Open b2ronn opened 2 years ago
A fix for this is included in the in-flight release of 8.3.0 -> https://github.com/elastic/logstash/pull/14044
The source of your problem appears to be in the Test Petclinic App
definition, which configures APM to set a field with key [ project
. Prior to Logstash 8.3.0, this field cannot be created and results in the crash you experienced. After Logstash 8.3.0, the field is created but cannot be referenced by the pipeline unless you opt into one of the field reference escape styles provided by #14044.
name: ELASTIC_APM_GLOBAL_LABELS value: '[ project=testtesttest'
Note that the source ip of the host submitting the faulty data to Logstash can be seen in the INFO
message (172.23.56.22
in this case) that precedes the WARN
message:
[2022-06-21T22:06:27,329][INFO ][org.logstash.beats.BeatsHandler][main][apm] [local: 172.21.65.17:5044, remote: 172.23.56.22:43272] Handling exception: org.logstash.FieldReference$IllegalSyntaxException: Invalid FieldReference: `[ project` (caused by: org.logstash.FieldReference$IllegalSyntaxException: Invalid FieldReference: `[ project`)
If the log level is set to warn
or higher, such as by setting log.level: "warn"
in logstash.yml
, this message won't be logged.
one of the applications sends to APM labels of a non-standard format that contains
I can't remove this label on the logstash side, because crashes on the input plugin. and it kills logstash with this error
Logstash information:
Please include the following information:
bin/logstash --version
)Plugins installed: (
bin/logstash-plugin list --verbose
)JVM (e.g.
java -version
):installed APM server via Elasticsearch (ECK) Operator 2.1.0 provided by Elastic
Steps to reproduce: Elasticsearch
APM-server
Logstash
Test Petclinic App