-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Mapping error ingesting logstash loggin #20709
Comments
Pinging @elastic/integrations (Team:Integrations) |
Here's another log sample (in pretty format) that causes the bug:
It cannot use |
I implemented what I discussed in the previous post with #23944. |
To prevent index failures resulting from indexing a mix of strings and nested objects as logstash.log.log_event.action, this converts any objects to a stringified version of the object using painless toString(). Fixes elastic#20709
To prevent index failures resulting from indexing a mix of strings and nested objects as logstash.log.log_event.action, this converts any objects to a stringified version of the object using painless toString(). Fixes #20709
…ic#23944) To prevent index failures resulting from indexing a mix of strings and nested objects as logstash.log.log_event.action, this converts any objects to a stringified version of the object using painless toString(). Fixes elastic#20709 (cherry picked from commit 0d4109d)
ES returns a mapping error when trying to ingest Logstash logs (in json format) via logstash module
FB mapping:
Event in Filebeat:
And it is rejected in ES due the mapping not being aligned:
The text was updated successfully, but these errors were encountered: