Only one agent installation is required on each monitored server (unless the server is monitored via WMI or another agentless method). The agent provides all standard up.time monitoring functionality for the server.
Additional components can be monitored via custom scripts, which are not included within the default agent but are also not a requirement for standard up.time monitoring features. |
Monitored Application Platform Support | Rating | Views | |
---|---|---|---|
By: uptime Support | Date Created: 12-6-2011 | Last Modified: 8-7-2014 | Index: 571 |
4412 |
Ensuring an Application is Always Running | Rating | Views | |
---|---|---|---|
up.time's Process Count Check monitor can help you ensure an application is always running By: uptime Support | Date Created: 10-30-2007 | Last Modified: 6-27-2011 | Index: 223 |
12595 |
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 |
4175 |
Changing a monitored host's IP address | Rating | Views | |
---|---|---|---|
Versions of up.time after 4.3.x include the option of changing a monitored hosts IP address or hostname after the element has been added to up.time. To do this follow these steps: - Browse to the... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-31-2011 | Index: 292 |
2513 |
How do I create an Application? | Rating | Views | |
---|---|---|---|
Applications are used in up.time to group together dispersed service monitors into a single status of up/down. To create an application follow these steps 1) Create all of the service monitors you... By: uptime Support | Date Created: 12-31-1969 | Last Modified: 8-25-2011 | Index: 344 |
4378 |