github-mirrors/logstash
1
0
Fork 0
mirror of https://github.com/elastic/logstash.git synced 2025-04-24 14:47:19 -04:00
Code Issues Projects Releases Packages Wiki Activity

Fix heading levels in logging topic

Browse source 
Fixes #5910
This commit is contained in:
DeDe Morton 2016-09-13 18:54:04 -07:00
parent 7c771ada6e
commit 0bca1a9a63
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/static/logging.asciidoc vendored
View file

@ -1,5 +1,5 @@
[[logging]]
== Logging
=== Logging
Logstash emits internal logs during its operation, which are placed in `LS_HOME/logs`. The default logging level is `INFO`.
Logstash's logging framework is based on http://logging.apache.org/log4j/2.x/[Log4j2 framework], and many of its functionality
@ -11,17 +11,17 @@ Starting with 5.0, you can configure logging for a particular subsystem in Logst
debugging issues with Elasticsearch Output, you can increase log levels just for that component. This way
you can reduce noise due to excessive logging and focus on the problem area effectively.
=== Log file location
==== Log file location
You can specify the log file location using `--path.logs` setting.
=== Log4j2 Configuration
==== Log4j2 Configuration
Logstash ships with a `log4j2.properties` file with out of the box settings. Users can modify this file directly to change the
rotation policy, type and other https://logging.apache.org/log4j/2.x/manual/configuration.html#Loggers[log4j2 configuration].
Any change made to this file is only effective after a process restart.
=== Logging APIs
==== Logging APIs
You could modify the `log4j2.properties` file and restart your Logstash, but that is both tedious and leads to unnecessary
downtime. Instead, you can dynamically update logging levels through the settings API. These settings are effective