-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log the config files used #40
Comments
@ryanuber @cbednarski I think it migiht be better if we exposed this information on an agent-debug endpoint rather than logging it, since this is something that will be logged during the startup and after a few hours/days it might be rotated out. |
That's true, but I think the same could be said for just about anything we log at start time. Logging it is just the easy way to solve the general use case since that's where other startup information lives currently. |
Also it's likely if there is a problem at startup (for instance if the node is misconfigured and fails to come online) that you may only have log data. |
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues. |
Suggested by @cbednarski in #33: It could be helpful to an operator if we had a debug-level log to show the names of the config files used when starting the agent, especially in cases where a config dir is used.
The text was updated successfully, but these errors were encountered: