- Observability: other versions:
- Get started
- What is Elastic Observability?
- What’s new in 8.17
- Quickstart: Monitor hosts with Elastic Agent
- Quickstart: Monitor your Kubernetes cluster with Elastic Agent
- Quickstart: Monitor hosts with OpenTelemetry
- Quickstart: Unified Kubernetes Observability with Elastic Distributions of OpenTelemetry (EDOT)
- Quickstart: Collect data with AWS Firehose
- Add data from Splunk
- Applications and services
- Application performance monitoring (APM)
- Get started
- Learn about data types
- Collect application data
- View and analyze data
- Act on data
- Use APM securely
- Manage storage
- Configure APM Server
- Monitor APM Server
- APM APIs
- Troubleshooting
- Upgrade
- Release notes
- Known issues
- Synthetic monitoring
- Get started
- Scripting browser monitors
- Configure lightweight monitors
- Manage monitors
- Work with params and secrets
- Analyze monitor data
- Monitor resources on private networks
- Use the CLI
- Configure projects
- Multi-factor Authentication
- Configure Synthetics settings
- Grant users access to secured resources
- Manage data retention
- Use Synthetics with traffic filters
- Migrate from the Elastic Synthetics integration
- Scale and architect a deployment
- Synthetics support matrix
- Synthetics Encryption and Security
- Troubleshooting
- Real user monitoring
- Uptime monitoring (deprecated)
- Tutorial: Monitor a Java application
- Application performance monitoring (APM)
- CI/CD
- Cloud
- Infrastructure and hosts
- Logs
- Troubleshooting
- Incident management
- Data set quality
- Observability AI Assistant
- Reference
Configure the Console output
editConfigure the Console output
editThe Console output writes events in JSON format to stdout.
The Console output should be used only for debugging issues as it can produce a large amount of logging data.
To use this output, edit the APM Server configuration file to disable the Elasticsearch
output by commenting it out, and enable the console output by adding output.console
.
Example configuration:
output.console: pretty: true
Configuration options
editYou can specify the following output.console
options in the apm-server.yml
config file:
enabled
editThe enabled config is a boolean setting to enable or disable the output. If set to false, the output is disabled.
The default value is true
.
pretty
editIf pretty
is set to true, events written to stdout will be nicely formatted. The default is false.
codec
editOutput codec configuration. If the codec
section is missing, events will be JSON encoded using the pretty
option.
See Change the output codec for more information.
bulk_max_size
editThe maximum number of events to buffer internally during publishing. The default is 2048.
Specifying a larger batch size may add some latency and buffering during publishing. However, for Console output, this setting does not affect how events are published.
Setting bulk_max_size
to values less than or equal to 0 disables the
splitting of batches. When splitting is disabled, the queue decides on the
number of events to be contained in a batch.
Change 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.
json.escape_html
: If escape_html
is set to true, HTML symbols will be escaped in strings. 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 escape_html: false
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]}'