We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Following the format the data is sent when using the elasticsearch output directly, as seen here:
https://github.com/elastic/apm-server/blob/6.5/apm-server.yml#L409-L431
The docs for the logstash output are not correct: https://www.elastic.co/guide/en/apm/server/current/logstash-output.html
There is no message saying that it should forward the data based on the process.event value.
process.event
Here is a logstash.conf that takes that into consideration, and works for other beats components:
logstash.conf
input { beats { port => 5044 } } filter { if [@metadata][beat] == "apm-server" { if [processor][event] == "sourcemap" { mutate { add_field => { "[@metadata][index]" => "apm-%{[@metadata][version]}-sourcemap" } } } else { mutate { add_field => { "[@metadata][index]" => "apm-%{[@metadata][version]}-%{[processor][event]}-%{+yyyy.MM.dd}" } } } } else { mutate { add_field => { "[@metadata][index]" => "%{[@metadata][beat]}-%{[@metadata][version]}-%{+YYYY.MM.dd}" } } } } output { elasticsearch { hosts => ["http://localhost:9200"] index => "%{[@metadata][index]}" } }
The text was updated successfully, but these errors were encountered:
Related to: #1792
Sorry, something went wrong.
bmorelli25
Successfully merging a pull request may close this issue.
Following the format the data is sent when using the elasticsearch output directly, as seen here:
https://github.com/elastic/apm-server/blob/6.5/apm-server.yml#L409-L431
The docs for the logstash output are not correct: https://www.elastic.co/guide/en/apm/server/current/logstash-output.html
There is no message saying that it should forward the data based on the
process.event
value.Here is a
logstash.conf
that takes that into consideration, and works for other beats components:The text was updated successfully, but these errors were encountered: