- Observability: other versions:
- What is Elastic Observability?
- What’s new in 7.16
- 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)
- Log monitoring
- Metrics monitoring
- Synthetic monitoring
- User Experience
- Explore data
- Alerting
- Cases
- CI/CD Observability
- Fields reference
- Tutorials
IMPORTANT: No additional bug fixes or documentation updates
will be released for this version. For the latest information, see the
current release documentation.
Deploy Beats to send data
editDeploy Beats to send data
editBeats are lightweight data shippers that send operational data to Elasticsearch. Elastic provides separate Beats for different types of data, such as logs, metrics, and uptime. To send observability data, you must install mutliple shippers on a single host.
Prefer to use a single agent for your use case? Refer to Deploy Elastic Agent to send data.
To get started with Beats:
- Install and configure Filebeat on your servers to collect log events. For details, refer to Ingest logs.
- Install and configure Metricbeat on your servers to collect and preprocess system and service metrics, such as information about running processes, as well as CPU, memory, disk, and network utilization numbers. For details, refer to Ingest metrics.
- Install and configure Heartbeat on your servers to periodically check the status of your services. For details, refer to Ingest uptime data.
- If you have added an APM Server as part of an Elasticsearch Service deployment, configure your APM agents to send data to your Elasticsearch cluster. For details, refer to Instrument applications.
Was this helpful?
Thank you for your feedback.