We're setting up a new SAM install, migrating across from ipMonitor. We have a bunch of internal URLs that we need to monitor. Currently I have them set up as http/https application monitors that I've applied to a fake parent node. So far so good, but I have two things I'm stuck on currently that I've looked for documentation or prior discussions on but haven't yet found a clear answer.
1. I'm trying to understand the differences between the Up/Warning/Critical/Down states of http/https monitors. I have Warning and Critical thresholds set, so I gather that the only difference between Up/Warning/Critical is the time taken for the page to return? In other words, all three mean that the page did come back and our Search String condition was satisfied, but that they differ only in the timing of the response? Further, the Down state means that we either got a response that didn't contain our Search String, or that the parent application monitor Polling Timeout was exceeded before a response was obtained? Or maybe for that latter case, there is another state we'd go into ("Unknown" perhaps)? All of this is leading to how Availability is calculated for these monitors, as we're seeing a lot of Warning and Critical activity, but monitors are still reporting 100% Availability. We'd like to see how we can properly report these "non-Up" states in our reporting.
2. Is there a way to insert the URL we are monitoring into the alert text that is sent? I couldn't see any obvious candidates in the fields available in the Alert Manager configuration. I could put the URL in the Description field and use ${UserDescription}, but I was hoping for another way before I go back and edit 100+ URL monitors.
