WARNING: Version 5.3 of Metricbeat has passed its EOL date.

This documentation is no longer being maintained and may be removed. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.

« include_fields Configuring Metricbeat to Use Ingest Node »
Elastic Docs ›Metricbeat Reference [5.3] ›Configuring Metricbeat

Filtering and Enhancing the Exported Data

edit

Filtering and Enhancing the Exported Data

edit

You can define processors in your configuration to process events before they are sent to the configured output.The libbeat library provides processors for:

  • reducing the number of exported fields
  • enhancing events with additional metadata
  • performing additional processing and decoding

Each processor receives an event, applies a defined action to the event, and returns the event. If you define a list of processors, they are executed in the order they are defined in the Metricbeat configuration file.

event -> processor 1 -> event1 -> processor 2 -> event2 ...

For example, the following configuration reduces the exported fields by dropping the beat.name and beat.hostname fields under beat from all documents.

processors:
 - drop_fields:
    fields: ['beat']

See Processors for more information.

« include_fields Configuring Metricbeat to Use Ingest Node »