- Journalbeat Reference for 6.5-7.15:
- Overview
- Get started
- Set up and run
- Configure
- Inputs
- General settings
- Project paths
- Output
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Processors
- Define processors
- add_cloud_metadata
- add_docker_metadata
- add_fields
- add_host_metadata
- add_id
- add_kubernetes_metadata
- add_labels
- add_locale
- add_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_csv_fields
- decode_json_fields
- decompress_gzip_field
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- registered_domain
- rename
- script
- timestamp
- truncate_fields
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- journalbeat.reference.yml
- How to guides
- Exported fields
- Monitor
- Secure
- Troubleshoot
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 Use Metricbeat collection.
Was this helpful?
Thank you for your feedback.