-
Notifications
You must be signed in to change notification settings - Fork 3.5k
New issue
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
"[" key in an event crashes logstash #12123
Comments
Can you provide a backtrace? I believe we have resolved a few of these since 7.4 shipped, but I'd be glad to help chase this instance down. Many plugins/codecs will catch this kind of exception and produce a tagged event that contains a serialized form of the payload. |
|
I also have this situation, looking forward to solving it. |
Any updates on this? This seems to still be an issue with 7.12.1 |
I resolved it by stringifying the incoming json document in the respective plug-in (couchdb_changes.rb). Works fine. |
any updates on this? this bug is causing our pipelines to crash and we have no way to fix this |
any updates on this? |
This was resolved in 8.3.0 with #14044. Even with the above fix in place, the Elasticsearch input plugin should certainly be more resilient to failure in general, so I have filed logstash-plugins/logstash-input-elasticsearch#182 |
For all general issues, please provide the following details for fast resolution:
It fails with the following error,
Error: Invalid FieldReference:
[Exception: Java::OrgLogstash::FieldReference::IllegalSyntaxException Stack: org.logstash.FieldReference$StrictTokenizer.tokenize(FieldReference.java:283)
As we don't have control on the incoming data, should logstash fail when it fails to parse the incoming data? Although it may look fair from the logstash perspective, this crash resets the elastic input plugin which then starts reading from the start again. One bad record results in an infinite loop! The fix I believe should come from logstash instead of elastic input plugin as this potentially can affect multiple other plugins as well. At least there should be a way to ignore such data errors while creating events at the logstash level.
The text was updated successfully, but these errors were encountered: