Logging configuration options
editLogging configuration options
editlog_level
editSets the logging level for the agent.
This option is case-insensitive.
Valid options: ERROR, WARN, INFO, DEBUG, TRACE
| Default | Type | Dynamic |
|---|---|---|
|
Level |
true |
| Java System Properties | Property file | Environment |
|---|---|---|
|
|
|
log_file
editSets the path of the agent logs.
The special value _AGENT_HOME_ is a placeholder for the folder the elastic-apm-agent.jar is in.
Example: _AGENT_HOME_/logs/elastic-apm.log
When set to the special value System.out, the logs are sent to standard out.
When logging to a file, it’s content is deleted when the application starts.
| Default | Type | Dynamic |
|---|---|---|
|
String |
false |
| Java System Properties | Property file | Environment |
|---|---|---|
|
|
|
enable_log_correlation
editA boolean specifying if the agent should integrate into SLF4J’s MDC to enable trace-log correlation.
If set to true, the agent will set the spanId and traceId for the currently active spans and transactions to the MDC.
You can then use the pattern format of your logging implementation to write the MDC values to your log file.
With the help of Filebeat and Logstash or an Elasticsearch ingest pipeline,
you can index your log files and correlate them with APM traces.
With this integration you can get all logs belonging to a particular trace and vice-versa:
for a specific log, see in which context it has been logged and which parameters the user provided.
While it’s allowed to enable this setting at runtime, you can’t disable it without a restart.
This is an incubating feature and the MDC key names might change.
| Default | Type | Dynamic |
|---|---|---|
|
Boolean |
true |
| Java System Properties | Property file | Environment |
|---|---|---|
|
|
|