- Observability: other versions:
- What is Elastic Observability?
- What’s new in 8.6
- Send data to Elasticsearch
- Spin up the Elastic Stack
- Deploy Elastic Agent to send data
- Deploy Beats to send data
- Elastic Serverless Forwarder for AWS
- Deploy serverless forwarder
- Configuration options
- Troubleshooting
- Observability overview page
- Application performance monitoring (APM)
- Application logs
- Log monitoring
- Infrastructure monitoring
- Uptime and synthetic monitoring
- User Experience
- Alerting
- Cases
- CI/CD observability
- Troubleshooting
- Fields reference
- Tutorials
- Monitor Amazon Web Services (AWS) with Elastic Agent
- Monitor Amazon Web Services (AWS) with Beats
- Monitor Google Cloud Platform
- Monitor a Java application
- Monitor Kubernetes
- Monitor Microsoft Azure with Elastic Agent
- Monitor Microsoft Azure with the native Azure integration
- Monitor Microsoft Azure with Beats
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
ECS logging with Filebeat
editECS logging with Filebeat
editElastic Common Schema (ECS) loggers format your logs into ECS-compatible JSON, removing the need to manually parse logs.
Requirements
- (Optional) Elastic APM agent for your programming language (for log correlation)
- The Elastic ECS logger for your language or framework
- Filebeat configured to monitor and capture application logs
Pros
- Popular logging frameworks supported
- Simplicity: no manual parsing with Filebeat, and a configuration can be reused across applications
- Decently human-readable JSON structure
- APM log correlation
- Resilient in case of outages
Cons
- Not all frameworks are supported
- Requires modification of the application and its log configuration
Get started
editSee the guide for your favorite logging framework:
On this page
Was this helpful?
Thank you for your feedback.