- Journalbeat Reference for 6.5-7.15:
- Overview
- Getting started with Journalbeat
- Setting up and running Journalbeat
- Configuring Journalbeat
- Configure inputs
- 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 Docker metadata
- Add fields
- Add Host metadata
- Add Kubernetes metadata
- Add labels
- Add the local time zone
- Add Observer metadata
- Add process metadata
- Add tags
- Community ID Network Flow Hash
- Convert
- Decode Base64 fields
- Decode CSV fields
- Decode JSON fields
- Decompress gzip fields
- Dissect strings
- DNS Reverse Lookup
- Drop events
- Drop fields from events
- Extract array
- Keep fields from events
- Registered Domain
- Rename fields from events
- Script Processor
- Timestamp
- Parse data by using ingest node
- Enrich events with geoIP information
- Configure project paths
- Configure the Kibana endpoint
- Load the Elasticsearch index template
- Configure logging
- Use environment variables in the configuration
- YAML tips and gotchas
- Regular expression support
- HTTP Endpoint
- journalbeat.reference.yml
- Exported fields
- Monitoring Journalbeat
- Securing Journalbeat
- Troubleshooting
This functionality is experimental and may be changed or removed completely in a
future release. Elastic will take a best effort approach to fix any issues, but
experimental features are not subject to the support SLA of official GA
features.
Use legacy internal collection to send monitoring data
editUse legacy internal collection to send monitoring data
editDeprecated in 7.2.0.
In Journalbeat version 7.1 and earlier, you configured internal collectors that sent monitoring data to the production cluster, which would either index the data locally, or forward the data to a dedicated monitoring cluster via HTTP exporters.
Starting in Journalbeat version 7.2, the legacy settings for internal collection are deprecated and will be removed in version 8.0.0. Instead of sending monitoring data to your production cluster, it’s recommended that you use the configuration described under internal collection to route monitoring data directly to your monitoring cluster.
Or as an alternative to internal collection, use Metricbeat collection.
Was this helpful?
Thank you for your feedback.