Message Logging Callout

[reshmaj]

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 · Accepted solution]

@Kiran Reddy

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

[reshmaj]

Thankyou @Ravindra Singh I am new to the message logging policy that i mentioned above scenario.Could you please explain in depth?

[dknezic]

If you're not familiar with the trace tool, Dino provides a nice overview here

[reshmaj]

Thankyou @dane knezic for your reply.Could you provide insight for the question i have posted?

[itravindrasingh]

Trace tool capture request and response on each step. Similar to the screenshot shows to you.