As Support Engineers, it can happen often that we need to review Debug/Trace level logs when troubleshooting technical issues with Logstash. Sometimes, we would like to have a look at the root level Debug logs before going further to either set only specific loggers or actually finding the root cause of the issue being investigated.
This page does not mention the log.levelsetting of logstash.yml method which is sometimes the quickest/clearest way for customers to set global logging to Debug level. Unless there are reasons not to use it, it would make sense to have it listed as part of the ways we can increase logging level. The Logging page only mentions the API and log4j2.properties methods
You can configure logging using the log4j2.properties file or the Logstash API.
AFAICT, even for the API and log4j2.properties methods, the page also does not include a clear example on how to set root level logging.
Tell us about the issue
Description:
As Support Engineers, it can happen often that we need to review
Debug
/Trace
level logs when troubleshooting technical issues with Logstash. Sometimes, we would like to have a look at the root levelDebug
logs before going further to either set only specific loggers or actually finding the root cause of the issue being investigated.My feedback here is about the Logging page:
log.level
setting oflogstash.yml
method which is sometimes the quickest/clearest way for customers to set global logging toDebug
level. Unless there are reasons not to use it, it would make sense to have it listed as part of the ways we can increase logging level. The Logging page only mentions the API andlog4j2.properties
methodslog4j2.properties
methods, the page also does not include a clear example on how to set root level logging.URL:
https://www.elastic.co/guide/en/logstash/current/logging.html
Anything else?