- Fleet and Elastic Agent Guide: other versions:
- Fleet and Elastic Agent overview
- Beats and Elastic Agent capabilities
- Quick starts
- Migrate from Beats to Elastic Agent
- Deployment models
- Install Elastic Agents
- Install Fleet-managed Elastic Agents
- Install standalone Elastic Agents (advanced users)
- Install Elastic Agents in a containerized environment
- Run Elastic Agent in a container
- Run Elastic Agent on Kubernetes managed by Fleet
- Run Elastic Agent on GKE managed by Fleet
- Run Elastic Agent on Amazon EKS managed by Fleet
- Run Elastic Agent on Azure AKS managed by Fleet
- Run Elastic Agent Standalone on Kubernetes
- Scaling Elastic Agent on Kubernetes
- Using a custom ingest pipeline with the Kubernetes Integration
- Environment variables
- Installation layout
- Air-gapped environments
- Using a proxy server with Elastic Agent and Fleet
- Uninstall Elastic Agents from edge hosts
- Start and stop Elastic Agents on edge hosts
- Elastic Agent configuration encryption
- Secure connections
- Manage Elastic Agents in Fleet
- Configure standalone Elastic Agents
- Create a standalone Elastic Agent policy
- Structure of a config file
- Inputs
- Providers
- Outputs
- SSL/TLS
- Logging
- Feature flags
- Agent download
- Config file examples
- Grant standalone Elastic Agents access to Elasticsearch
- Example: Use standalone Elastic Agent to monitor nginx
- Debug standalone Elastic Agents
- Kubernetes autodiscovery with Elastic Agent
- Monitoring
- Reference YAML
- Manage integrations
- Define processors
- Processor syntax
- add_cloud_metadata
- add_cloudfoundry_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_cef
- decode_csv_fields
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- parse_aws_vpc_flow_log
- rate_limit
- registered_domain
- rename
- replace
- script
- syslog
- timestamp
- translate_sid
- truncate_fields
- urldecode
- Command reference
- Troubleshoot
- Release notes
Configure logging for standalone Elastic Agents
editConfigure logging for standalone Elastic Agents
editThe 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 agent.logging.files: path: /var/log/elastic-agent name: elastic-agent keepfiles: 7 permissions: 0600
Logging configuration settings
editYou can specify the following settings in the Logging section of the
elastic-agent.yml
config file.
Setting |
Description |
|
The minimum log level. Possible values:
Default: |
|
Specify the selector tags that are used by different Elastic Agent components for debugging.
To debug the output for all components, use Possible values: |
|
Set to Default: |
|
Set to Default: |
|
Set to Default: |
|
Set to Default: |
|
Specify the period after which to log the internal metrics. This setting is not passed to any Beats running under the Elastic Agent. Default: |
|
Set to Default: |
|
The directory that log files is written to. /Library/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log /opt/Elastic/Agent/data/elastic-agent-*/logs/elastic-agent-json.log C:\Program Files\Elastic\Agent\data\elastic-agent-*\logs\elastic-agent-json.log /var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log /var/lib/elastic-agent/data/elastic-agent-*/logs/elastic-agent-json.log 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: |
|
The maximum size limit of a log file. If the limit is reached, a new log file is generated. Default: |
|
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 Default: |
|
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: |
|
Enable log file rotation on time intervals in addition to the size-based rotation. Intervals must be at least Default: |
|
Set to Default: |
On this page