Run the following query to get the configuration ID of the monitor you want to check:
Next, run the following query to see the status of the monitor (ordered by date) and its status message:
|
Application Availability Does Not Match Average Status of Service... | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 7-9-2007 | Last Modified: 6-28-2011 | Index: 192 |
4174 |
Understanding the Status of Services | Rating | Views | |
---|---|---|---|
This article explains the status of the services that are displayed in the GlobalScan panel By: uptime Support | Date Created: 9-6-2007 | Last Modified: 6-28-2011 | Index: 213 |
3641 |
MySQL Monitor error: Insufficient status data returned | Rating | Views | |
---|---|---|---|
Monitor: MySQL (Advanced Metrics) Status Message: ------------------------------------------------ Status: CRIT Message: Insufficient status data returned Response time: 437... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 287 |
2763 |
Configuring up.time to send alerts based on monitor status | Rating | Views | |
---|---|---|---|
Alert profiles are attached to one or more service monitors and they are used to tell up.time what groups of users will receive the alert. You can create an alert profile by following the steps... By: uptime Support | Date Created: 2-3-2009 | Last Modified: 8-25-2011 | Index: 366 |
4642 |
How does up.time determine routing? | Rating | Views | |
---|---|---|---|
When a monitoring station has multiple NICs that are connected to different VLANs or subnets, up.time will use the operating system's routing table to determine where specific requests should be sent. By: uptime Support | Date Created: 6-22-2011 | Last Modified: 8-10-2011 | Index: 526 |
1446 |