- 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_cloudfoundry_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
- translate_sid
- 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.
Add fields
editAdd fields
editThe add_fields
processor adds additional fields to the event. Fields can be
scalar values, arrays, dictionaries, or any nested combination of these. By
default the fields that you specify will be grouped under the fields
sub-dictionary in the event. To group the fields under a different
sub-dictionary, use the target
setting. To store the fields as
top-level fields, set target: ''
.
-
target
-
(Optional) Sub-dictionary to put all fields into. Defaults to
fields
. -
fields
- Fields to be added.
For example, this configuration:
processors: - add_fields: target: project fields: name: myproject id: '574734885120952459'
Adds these fields to any event:
{ "project": { "name": "myproject", "id": "574734885120952459" } }
Was this helpful?
Thank you for your feedback.