In triaging the train we noticed that memory allocation errors were being shown despite filters for that message.
This is due to a change in how monolog reports messages to logstash. Previously, there was an exception object with:
Now there is no exception object, but there is only a message field. We're missing the stack trace and the exception.message.