We use lots of web checks and would like a separate trigger on each of the possible failure modes - timeout/no connect, return code mismatch, and text mismatch. For the first one we wait a while, but the 2nd and 3rd require immediate engineer alerts.
The only useful web check items that seem available are download time, response code, and the fail() function so I can't seem to get a way to do this, especially because when the step fails, all items are zero, so I can't even check if the failure was due to bad code since the code item is 0 then (even if the real code was 504, etc.)
Even better (or helpful) would be to get the error text the Monitor-Web shows then we can parse it, etc. but seems only in DB and not an item for a trigger.
The only useful web check items that seem available are download time, response code, and the fail() function so I can't seem to get a way to do this, especially because when the step fails, all items are zero, so I can't even check if the failure was due to bad code since the code item is 0 then (even if the real code was 504, etc.)
Even better (or helpful) would be to get the error text the Monitor-Web shows then we can parse it, etc. but seems only in DB and not an item for a trigger.