-
Notifications
You must be signed in to change notification settings - Fork 4.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
Proposal: Log system details to aid in support and debugging #5946
Comments
+1 on this. For the As the info is quite extensive, I wonder if we should only put a subset under |
I think it's best to put it all under INFO so that it is present by default so we don't need to ask people to do anything special to get this data other than ask for the logs. Regarding |
This adds logging of system information to provide more situational awareness when debugging. When a Beat starts it will log data about the host, process, build, and go runtime. One goal is to help resolve issues faster because there will be fewer back-and-forths. When logs are provided by the user there wouldn't be a need for questions like "how did you run it", "what OS", "what kernel", "what kind of hardware", "are you running in Docker", "what is the machine's local timezone", etc. Closes elastic#5946
This adds logging of system information to provide more situational awareness when debugging. When a Beat starts it will log data about the host, process, build, and go runtime. One goal is to help resolve issues faster because there will be fewer back-and-forths. When logs are provided by the user there wouldn't be a need for questions like "how did you run it", "what OS", "what kernel", "what kind of hardware", "are you running in Docker", "what is the machine's local timezone", etc. Closes #5946
At startup we should log details about the system to aid in providing support. This information could help us resolve issues faster because there would be fewer back-and-forths. When logs are provided by the user there wouldn't be a need for questions like "how did you run it", "what OS", "what kind of hardware", "what user were you running as", "are you running in Docker", "what is the machine's local timezone", etc.
For example, at startup we could add a single log line with the system info. We've had similar logging limited to Metricbeat-Windows and it has proven useful when debugging permissions issues.
This log message contains:
On Linux and Windows this will include some additional sections about privileges, capabilities, and seccomp.
The text was updated successfully, but these errors were encountered: