sweb.Validate System Health Status
Multiple sites going offline around the same time can be an indication of a service issue.
When this value is 10 or higher, a critical alert will be issued.
When this value is 3-9, a warning alert will be issued.
The total number os sites that are offline can be an indication of a service issue. However, the threshold is much higher compared to the number of sites that go offline within last 10 minutes.
When this value is 25 or higher, a critical alert will be issued.
When this value is 15-24, a warning alert will be issued.
Old 3.8 Sites had an issue where a rare type of Parking.Logic message could result in an engine issue that would ultimately stop the site's Application Pool online.
While this issue has not been observed for a long while (and very few customers are still on v3.8), this monitoring is still in place. When this value is 1 or higher, a warning alert will be issued.
This metric shows how much time was needed to send and process the most recent health message by sweb.Validate
Typically, this value should be very low. This value will not trigger an alert by itself. Rather, it is used in conjunction with the five-minute average metric to determine system health.
For the preceding five minutes, this metric shows how long it took on average for a Parking.Logic message sent by a Parking system to reach the cloud and be processed by sweb.Validate
Typically, messages are transmitted and processed almost immediately. A sustained high value can indicate there is a system issue. When this value is 25,000 (25 seconds) or higher AND the Current Processing Time is 20,000 (20 seconds) or higher, a critical alert will be issued.
When this value is 12,000 (12 seconds) or higher AND the Current Processing Time is 6,000 (6 seconds) or higher, a warning alert will be issued.
This metric shows how much time has elapsed since the most recent system health message was received and processed.
Typically, this value should not exceed 10,000 ms (10 seconds). Though during times of high volume, it can increase without affecting system health. When this value is 75,000 (75 seconds), a critical alert will be issued.
When this value is 30,000 (30 seconds), a warning alert will be issued.
This metric shows how many times a health message has failed to send in the last five minutes.
Since this health process uses the publicly-available URL, failed messages can be an indication of server unavailability or DNS issues. When this value is 6 or greater, a critical alert will be issued.
When this value is 1-5, a warning alert will be issued.
This metric records the last time a Park Mobile transaction was closed out and completed successfully.
If it has been more than 24 hours since any site has done so, it may be indicative of a service issue that needs to be investigated.