I had a request fly into my inbox because...sometimes, SOMETIMES; things get into Production without getting monitored. And then sometimes those "things" have problems that then turn into Production problems and I get grumpy 1. Because there was user activity interruption that leads to all type of extrapolated metrics. 2. Because I get that great message in my chat client or mailbox asking me - "Hey, why aren't we getting alerted for those outages?"
Yup. It happens.
In this particular case - there is some application that some of the developers are already running some type of test/status checks that are being generated into a JSON file.
We've attempted (utilizing the SAM HTTP Component Monitor) to parse the JSON file with a POST and Query in the Request Body but none of the queries seem to return in the way we expect. Everything returns a 405 - Method Not Allowed.
Then theory is that the Request Body is sending a generic HTTP request and the static file won't accept it.
Can anyone confirm that using the HTTP Component Monitor is just sending the generic request and this is probably not going to work OR if you've got a better idea since apparently my dev team is going to be doing more things in this fashion this might be a problem that sticks with me.
My plan B was to utilize a PowerShell monitor to parse the JSON file but that's getting a little complicated due to how many loops (failure checkpoints) it needs to look at.
