-
Notifications
You must be signed in to change notification settings - Fork 31
Malformed messages result in message buffer queues to fill up #25
Comments
Looks like i might be able to emulate this failure mode using a simple test json object based on this stackoverflow query |
I Got what is issue. |
Dropping with warnings might be the safest approach as forcing encoding might change the meaning of the messages being sent. If the messages are dropped at least they can be reviewed and fixed by an end-user - just need to make sure they're dropped with a clear indication of why they were dropped. |
Where about's should I be looking to apply changes? I'm thinking it might be around here; https://github.com/giraffi/fluent-plugin-amqp/blob/master/lib/fluent/plugin/out_amqp.rb#L84-L90 Is it as simple as wrapping the JSON.dump in a begin/rescue and throwing a log warning for encoding errors? |
I seemed it's might better. |
I'm not sure I understand what you mean...? |
Ah, sorry. |
Going to manually hack this into some of our servers;
|
It looks good enough to avoid crash. Could you create new PR? |
…rate with rescues to deal with Generate Errors
I'm not 100% on the sequence of events that result in this scenario, but heres what I think happens...
Configuration
Message showing error
The text was updated successfully, but these errors were encountered: