- Auditbeat Reference: other versions:
- Overview
- Contributing to Beats
- Getting started with Auditbeat
- Breaking changes in 6.2
- Setting up and running Auditbeat
- Configuring Auditbeat
- Specify which modules to run
- Specify general settings
- Reload the configuration dynamically
- Configure the internal queue
- Configure the output
- Specify SSL settings
- Filter and enhance the exported data
- Parse data by using ingest node
- Set up project paths
- Set up the Kibana endpoint
- Load the Kibana dashboards
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- auditbeat.reference.yml
- Modules
- Exported fields
- Monitoring Auditbeat
- Securing Auditbeat
- Troubleshooting
WARNING: Version 6.2 of Auditbeat has passed its EOL date.
This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Configure the output codec
editConfigure the output codec
editFor outputs that do not require a specific encoding, you can change the encoding
by using the codec configuration. You can specify either the json or format
codec. By default the json codec is used.
json.pretty: If pretty is set to true, events will be nicely formatted. The default is false.
Example configuration that uses the json codec with pretty printing enabled to write events to the console:
output.console: codec.json: pretty: true
format.string: Configurable format string used to create a custom formatted message.
Example configurable that uses the format codec to print the events timestamp and message field to console:
output.console: codec.format: string: '%{[@timestamp]} %{[message]}'