For the WebMonitor rule "WebMonitor Transaction Availability Check" the rule conditions are:
Fatal:
#serviceAvailability# <= 0
Warning:
#serviceAvailability# > 0 && (#pageAvailability# <= 0 || #httpStatus# < 200 || #httpStatus# > 400)
Warning alarms are fired for some sites even when they are up, what do the following metrics mean and where are they getting their value from?
Reviewing Script Console for the httpStatus property shows it is not set for the Web transactions; hence the rule is not able to evaluate this condition.
There could be a delay while the data is being aggregated by the WebMonitor rule; it is necessary to confirm if httpStatus always shows as unset in Script Console or it's just sporadically.
The data from Configuration | Data | Services | All System Services | WebMonitor Pivot Service | Definition | Choose URL | Measurements | HttpStatus | Select Property Viewer from the right panel | see the list of last httpStatus metrics is the data of per location while the query from Script Console EUWebMonitorTransactionMetrics | List instances and select one URL | filter by HTTP | see last http status displayed is the data per transaction; there're not the same exactly.
To check data of EUWebMonitorTransactionMetrics for a specific URL, then navigate to Configuration -> Data -> Management Server -> All Data -> WebMonitorRoot -> WebMonitorRoot -> Webmonitor Transactions -> click on your transaction -> measurements -> click on the node which is type of "EUWebMonitorTransactionMetrics", that's the node without "@" in its name -> then check httpStatus.
About the rule condition, httpStatus may be ignored sometimes, for example, if serviceAvailability is 100 and pageAvailability is 0, then it's not necessary to evaluate the value of httpStatus. Generally if the given URL is accessible, there should get a value for httpStatus.
For metrics serverAvailability, serviceAvailability and pageAvailability the only possible values are 0 and 100 to indicate if the server, service or page are unavailable (0) or available (100).
For example, if the agent cannot visit the server, it wont be able to reach the service or page; then the value for serverAvailability, serviceAvailabity and pageAvailabity will be 0.
The same, if the agent can visit the page, then indicates both the server and the service are also available for the agent, then the value is 100 for those flags. See table below for more details.
Note: Service availability refers to the availability of the HTTP service.
For Page Availability, Expected Content and Unexpected content validations will be taken into account if the expected content is not found or the unexpected content is found and be included in the alarm message for a Warning severity if:
Some important definitions:
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center