Hello Thwack community, thank you for putting up a time to address this.
Here is how I set up my HTTPS monitor components:
component 1:
component name: Healthy
Go to "URL"
Search String: Healthy
Fail if found: No
component 2:
component name: Unhealthy
Go to "URL"
Search String: Unhealthy
Fail if found: Yes
component 3:
component name: Degraded
Go to "URL"
Search String: Degeraded
Fail if found: Yes
I have set this up using SAM for "MYURL/API/Health" which is off Azure and it will either show "Healthy", "Unhealthy" or "Degraded" based on what is the API health at the moment,
the URL is the same, the strings are different.
My problem is "Healthy" and "Unhealthy" they both contain 'healthy' in them and when I configure my alert conditions, even when the API is reporting "Unhealthy", the step that looks for "Healthy" comes back as up! because it was able to find the string it was looking for!
Here are how I set up my trigger conditions for an alert to detect "Unhealthy" as well as makes sure "Healthy" and "Degraded" checks also failed
All child conditions must be satisfied (AND)
Component Alerting Properties - Component Name - is equal to - Healthy
Component - Status - is equal to - Down (because it fails if the string is not found)
All child conditions must be satisfied (AND)
Component Alerting Properties - Component Name - is equal to - Degraded
Component - Status - is equal to - Up (because it fails if the string is found)
All child conditions must be satisfied (AND)
Component Alerting Properties - Component Name - is equal to - Unhealthy
Component - Status - is equal to - Down (because it fails if the string is found)
like I mentioned before the issues is the first step (Healthy) will not fail when the URL is returning "Unhealthy" though I think it should
Now is there any other way of specifying the string on the template to avoid this confusion? to make it search exactly for something and not anything that contains a part of it?
Thank you
