- Auditbeat Reference: other versions:
- Auditbeat overview
- Quick start: installation and configuration
- Set up and run
- Upgrade Auditbeat
- Configure
- Modules
- General settings
- Project paths
- Config file reloading
- Output
- Kerberos
- SSL
- Index lifecycle management (ILM)
- Elasticsearch index template
- Kibana endpoint
- Kibana dashboards
- 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_network_direction
- add_nomad_metadata
- add_observer_metadata
- add_process_metadata
- add_tags
- append
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_duration
- decode_json_fields
- decode_xml
- decode_xml_wineventlog
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- move_fields
- rate_limit
- registered_domain
- rename
- replace
- syslog
- translate_sid
- truncate_fields
- urldecode
- Internal queue
- Logging
- HTTP endpoint
- Regular expression support
- Instrumentation
- Feature flags
- auditbeat.reference.yml
- How to guides
- Modules
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get Help
- Debug
- Understand logged metrics
- Common problems
- Auditbeat fails to watch folders because too many files are open
- Auditbeat uses too much bandwidth
- Error loading config file
- Found unexpected or unknown characters
- Logstash connection doesn’t work
- Publishing to Logstash fails with "connection reset by peer" message
- @metadata is missing in Logstash
- Not sure whether to use Logstash or Beats
- SSL client fails to connect to Logstash
- Monitoring UI shows fewer Beats than expected
- Dashboard could not locate the index-pattern
- High RSS memory usage due to MADV settings
- Contribute to Beats
Move fields
editMove fields
editThe move_fields
processor moves event fields from one object into another. It can also rearrange fields or add a prefix to fields.
The processor extracts fields from from
, then uses fields
and exclude
as filters to choose which fields to move into the to
field.
For example, given the following event:
{ "app": { "method": "a", "elapsed_time": 100, "user_id": 100, "message": "i'm a message" } }
To move method
and elapsed_time
into another object, use this configuration:
processors: - move_fields: from: "app" fields: ["method", "elapsed_time"], to: "rpc."
Your final event will be:
{ "app": { "user_id": 100, "message": "i'm a message", "rpc": { "method": "a", "elapsed_time": 100 } } }
To add a prefix to the whole event:
{ "app": { "method": "a"}, "cost": 100 }
Use this configuration:
processors: - move_fields: to: "my_prefix_"
Your final event will be:
{ "my_prefix_app": { "method": "a"}, "my_prefix_cost": 100 }
Table 2. Move-fields options
Name | Required | Default | Description | |
---|---|---|---|---|
|
no |
Which field you want extract. This field and any nested fields will be moved into |
||
|
no |
Which fields to extract from |
||
|
no |
false |
Ignore "not found" errors when extracting fields. |
|
|
no |
A list of fields to exclude and not move. |
||
|
yes |
These fields extract from |
processors: - move_fields: from: "app" fields: [ "method", "elapsed_time" ] to: "rpc."
ElasticON events are back!
Learn about the Elastic Search AI Platform from the experts at our live events.
Register now