You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In 8.10.0 onwards, we removed processor.event and processor.name from the model completely (elastic/apm-data#79). Now, these are set by Elasticsearch in ingest pipelines: #11028. This all works well for the majority of use cases.
Since those fields are no longer set within APM Server, users can't use those fields' values in Logstash to route events. However, they could use [data_stream][type] instead of [processor][event] to route traces, metrics and logs to a datastream if they wanted to.
The text was updated successfully, but these errors were encountered:
@bmorelli25 it seems we only merged the changes in APM Server on July 18th. The documentation PR was tested on July 14th. Which means that unless you've re-tested the configuration above with a released 8.10.x build, it's highly unlikely it'll work.
In
8.10.0
onwards, we removed processor.event and processor.name from the model completely (elastic/apm-data#79). Now, these are set by Elasticsearch in ingest pipelines: #11028. This all works well for the majority of use cases.However, it appears we overlooked or dismissed use-cases where we users use those fields in Logstash for routing purposes (https://www.elastic.co/guide/en/apm/guide/current/logstash-output.html#ls-config-pipeline)
Since those fields are no longer set within APM Server, users can't use those fields' values in Logstash to route events. However, they could use
[data_stream][type]
instead of[processor][event]
to routetraces
,metrics
andlogs
to a datastream if they wanted to.The text was updated successfully, but these errors were encountered: