Open nkakouros opened 4 years ago
Pinging @elastic/integrations-services (Team:Services)
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Still a valid request.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
definitely valid!!!!
Hi! We just realized that we haven't looked into this issue in a while. We're sorry!
We're labeling this issue as Stale
to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1
.
Thank you for your contribution!
still valid
Describe the enhancement: The
@metadata
field is documented as containing:But, in Filebeat, if an input has a pipeline specified, it can also contain a
pipeline
key (source). This is mentioned to show that there is already limited support for what I am describing below.In every Beat, you can configure a pipeline in the Elasticsearch output. But, there is no way to do so if you are using the Logstash output. For instance, if you want to apply some processing on all packetbeat logs using an ingest node (e.g. to change the timestamp), you can't use sth like:
since
@metadata
will not contain thepipeline
key. One has to fallback to using more complex and fragile conditionals.