A newer version is available. For the latest information, see the current release documentation.
« Publishing to Logstash fails with "connection reset by peer" message Not sure whether to use Logstash or Beats »
Elastic Docs ›Functionbeat Reference [7.10] ›Troubleshoot ›Common problems

@metadata is missing in Logstash

edit

@metadata is missing in Logstash

edit

Logstash outputs remove @metadata fields automatically. Therefore, if Logstash instances are chained directly or via some message queue (for example, Redis or Kafka), the @metadata field will not be available in the final Logstash instance.

To preserve @metadata fields, use the Logstash mutate filter with the rename setting to rename the fields to non-internal fields.

« Publishing to Logstash fails with "connection reset by peer" message Not sure whether to use Logstash or Beats »