- Winlogbeat Reference: other versions:
- Winlogbeat Overview
- Quick start: installation and configuration
- Set up and run
- Upgrade
- Configure
- Winlogbeat
- General settings
- Project paths
- 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_observer_metadata
- add_process_metadata
- add_tags
- community_id
- convert
- copy_fields
- decode_base64_field
- decode_json_fields
- decompress_gzip_field
- detect_mime_type
- dissect
- dns
- drop_event
- drop_fields
- extract_array
- fingerprint
- include_fields
- rate_limit
- registered_domain
- rename
- script
- timestamp
- translate_sid
- truncate_fields
- urldecode
- decode_xml
- Internal queue
- Logging
- HTTP endpoint
- Instrumentation
- winlogbeat.reference.yml
- How to guides
- Modules
- Exported fields
- Monitor
- Secure
- Troubleshoot
- Get Help
- Debug
- Common problems
- Dashboard in Kibana is breaking up data fields incorrectly
- Bogus computer_name fields are reported in some events
- 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
- Not sure how to read from .evtx files
- Contribute to Beats
Rename fields from events
editRename fields from events
editThe rename
processor specifies a list of fields to rename. Under the fields
key, each entry contains a from: old-key
and a to: new-key
pair, where:
-
from
is the original field name -
to
is the target field name
The rename
processor cannot be used to overwrite fields. To overwrite fields
either first rename the target field, or use the drop_fields
processor to drop
the field and then rename the field.
You can rename fields to resolve field name conflicts. For example, if an
event has two fields, c
and c.b
(where b
is a subfield of c
), assigning
scalar values results in an Elasticsearch error at ingest time. The assignment {"c": 1,
"c.b": 2}
would result in an error because c
is an object and cannot be
assigned a scalar value. To prevent this conflict, rename c
to c.value
before assigning values.
processors: - rename: fields: - from: "a.g" to: "e.d" ignore_missing: false fail_on_error: true
The rename
processor has the following configuration settings:
-
ignore_missing
-
(Optional) If set to true, no error is logged in case a key
which should be renamed is missing. Default is
false
. -
fail_on_error
-
(Optional) If set to true, in case of an error the renaming of
fields is stopped and the original event is returned. If set to false, renaming
continues also if an error happened during renaming. Default is
true
.
See Conditions for a list of supported conditions.
You can specify multiple rename
processors under the processors
section.