Configure logging for standalone Elastic Agentsedit

The Logging section of the elastic-agent.yml config file contains settings for configuring the logging output. The logging system can write logs to the syslog, file, stderr, eventlog, or rotate log files. If you do not explicitly configure logging, the stderr output is used.

This example configures Elastic Agent logging:

agent.logging.level: info
agent.logging.to_files: true
  path: /var/log/elastic-agent
  name: elastic-agent
  keepfiles: 7
  permissions: 0600

Logging configuration settingsedit

You can specify the following settings in the Logging section of the elastic-agent.yml config file.




The minimum log level.

Possible values:

  • error: Logs errors and critical errors.
  • warning: Logs warnings, errors, and critical errors.
  • info: Logs informational messages, including the number of events that are published. Also logs any warnings, errors, or critical errors.
  • debug: Logs debug messages, including a detailed printout of all events flushed. Also logs informational messages, warnings, errors, and critical errors. When the log level is debug, you can specify a list of selectors to display debug messages for specific components. If no selectors are specified, the * selector is used to display debug messages for all components.

Default: info


Specify the selector tags that are used by different Elastic Agent components for debugging. To debug the output for all components, use *. To display debug messages related to event publishing, set to publish. Multiple selectors can be chained.

Possible values: [beat], [publish], [service]


Set to true to write all logging output to the stderr output—this is equivalent to using the -e command line option.

Default: true


Set to true to write all logging output to the syslog output.

Default: false


Set to true to write all logging output to the Windows eventlog output.

Default: false


Set to true for Elastic Agent to periodically log its internal metrics that have changed in the last period. For each metric that changed, the delta from the value at the beginning of the period is logged. Also, the total values for all non-zero internal metrics get logged on shutdown. If set to false, no metrics for the agent or any of the Beats running under it are logged.

Default: true


Specify the period after which to log the internal metrics. This setting is not passed to any Beats running under the Elastic Agent.

Default: 30s


Set to true to log to rotating files. Set to false to disable logging to files.

Default: true


The directory that log files is written to.


Logs file names end with a date and optional number: log-date.ndjson, log-date-1.ndjson, and so on as new files are created during rotation.

The name of the file that logs are written to.

Default: elastic-agent


The maximum size limit of a log file. If the limit is reached, a new log file is generated.

Default: 10485760 (10MB)


The most recent number of rotated log files to keep on disk. Older files are deleted during log rotation. The value must be in the range of 2 to 1024 files.

Default: 7


The permissions mask to apply when rotating log files. The permissions option must be a valid Unix-style file permissions mask expressed in octal notation. In Go, numbers in octal notation must start with 0.

Default: 0600


Enable log file rotation on time intervals in addition to the size-based rotation. Intervals must be at least 1s. Values of 1m, 1h, 24h, 7*24h, 30*24h, and 365*24h are boundary-aligned with minutes, hours, days, weeks, months, and years as reported by the local system clock. All other intervals get calculated from the Unix epoch.

Default: 0 (disabled)


Set to true to rotate existing logs on startup rather than to append to the existing file.

Default: true