-
Notifications
You must be signed in to change notification settings - Fork 83
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 all of fleet server configuration at startup #1626
Labels
Comments
@michalpristas @joshdover as discussed. |
These logs need to be sure to sanitize the configuration to avoid logging any sensitive fields like certificate private keys |
pierrehilbert
added
v8.4.0
Team:Elastic-Agent-Control-Plane
Label for the Agent Control Plane team
labels
Jul 5, 2022
@michel-laterman did we make any progress on this one? |
I have a PR that needs testing, i'll push it as a draft |
@michel-laterman thanks, would you mind linking it to this issue to keep track of it? |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
When debugging an issue in cloud it is useful to know with what options the fleet-server is operating at, because some options are derived from the current container size and other can be change with the fleet-server integration.
I would be good to log a single even that we can search through the log that would container the information defined in https://github.com/elastic/fleet-server/blob/3c8cd17c1370abb07f6935021d31c8204e4d16a3/internal/pkg/config/input.go
The text was updated successfully, but these errors were encountered: