Solved: Message Logging Callout - Page 2

reshmaj · 08-19-2019 04:58 AM

We use a message logging policy to log messages via Syslog.We've discovered as of 8:00 am on 27th July 2019 (AEST), we no longer are able to successfully parse "error" messages (anything other than a "StatusCode = 200"). Was there a release that changed the message format? We urgently need this fixed as it has broken our alerting.Could you please help me out from these error?

itravindrasingh

@Kiran Reddy

You can use a trace tool to see what data/format is getting missed.

View solution in original post