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
Logstash pipeline is adding an event field to the payload containing the original payload from RabbitMQ. This is causing Elasticsearch to throw an error as it goes against the strict mapping set for the indices.
This was temporarily fixed in commit- 8ef8f5a by manually removing the event field in the pipeline filter. Need to debug what's causing this and make a permanent fix.
The text was updated successfully, but these errors were encountered:
- postgres max connections increased as more no. of components use it
- Logstash fix pipeline, by removing event field in docker
see issue datakaveri#193
Logstash pipeline is adding an
event
field to the payload containing the original payload from RabbitMQ. This is causing Elasticsearch to throw an error as it goes against the strict mapping set for the indices.Tested using the RMQ test script here
Error from Logstash:
Current solution:
This was temporarily fixed in commit- 8ef8f5a by manually removing the
event
field in the pipeline filter. Need to debug what's causing this and make a permanent fix.The text was updated successfully, but these errors were encountered: