- Functionbeat Reference:
- Overview
- Getting Started With Functionbeat
- Setting up and running Functionbeat
- Configuring Functionbeat
- Configure functions
- Specify general settings
- Configure the internal queue
- Configure the output
- Configure index lifecycle management
- Specify SSL settings
- Filter and enhance the exported data
- Define processors
- Add cloud metadata
- Add fields
- Add labels
- Add the local time zone
- Add tags
- Decode JSON fields
- Community ID Network Flow Hash
- Convert
- Drop events
- Drop fields from events
- Keep fields from events
- Rename fields from events
- Add Kubernetes metadata
- Add Docker metadata
- Add Host metadata
- Add Observer metadata
- Dissect strings
- DNS Reverse Lookup
- Add process metadata
- Extract array
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure the Kibana endpoint
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- functionbeat.reference.yml
- Exported fields
- Monitoring Functionbeat
- Securing Functionbeat
- Troubleshooting
A newer version is available. For the latest information, see the
current release documentation.
Monitoring Functionbeat
editMonitoring Functionbeat
editYou can use the Elastic Stack monitoring features to gain insight into the health of Functionbeat agents running in your environment.
To monitor Functionbeat, make sure monitoring is enabled on your Elasticsearch cluster, then configure the method used to collect Functionbeat metrics. You can use one of following methods:
- Internal collection - Internal collectors send monitoring data directly to your monitoring cluster.
- Legacy internal collection (deprecated) - Legacy internal collectors send monitoring data to your production cluster.
To learn about monitoring in general, see Monitoring the Elastic Stack.
Was this helpful?
Thank you for your feedback.