Method for event triggered monitoring of managed server health
First Claim
1. A method for monitoring a server comprising:
- providing a monitoring instance to monitor at least one server;
providing a triggering event that causes the monitoring instance to monitor the at least one server;
determining the health status of the at least one server by invoking a servlet located on the server, the servlet configured to return a health status of the server to the monitoring instance;
detecting degenerate health status of the at least one server and determining whether to restart the at least one server upon the detection of the degenerate health;
determining for a server having a health status of degenerated whether any conditions exist that may limit the at least one server from being restarted; and
performing treatment on the server, the treatment corresponding with the health status of the server, by determining a value of an auto-kill parameter, the value specified in the auto-kill parameter corresponding to whether the monitoring instance will automatically kill a server if the server is deemed failed.
2 Assignments
0 Petitions
Accused Products
Abstract
A Node Manager monitors the status of multiple servers. The Node Manager detects server failures, periodically monitors server health status, and performs server maintenance. When the Node Manager detects a server failure, it determines whether or not the server should be restarted. While periodically monitoring servers, the Node Manager may determine how often to trigger a health check, how long to wait for a response, and how to proceed if the server is deemed failed. The Node Manager may be controlled by an Administrative Server directly or by an external administrative agent. An administrative agent may control the Node Manager by interfacing with the Administrative Server. The Node Manager and AS may authenticate each other and encode their communications to each other for increased security.
-
Citations
21 Claims
-
1. A method for monitoring a server comprising:
-
providing a monitoring instance to monitor at least one server; providing a triggering event that causes the monitoring instance to monitor the at least one server; determining the health status of the at least one server by invoking a servlet located on the server, the servlet configured to return a health status of the server to the monitoring instance; detecting degenerate health status of the at least one server and determining whether to restart the at least one server upon the detection of the degenerate health; determining for a server having a health status of degenerated whether any conditions exist that may limit the at least one server from being restarted; and performing treatment on the server, the treatment corresponding with the health status of the server, by determining a value of an auto-kill parameter, the value specified in the auto-kill parameter corresponding to whether the monitoring instance will automatically kill a server if the server is deemed failed. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21)
-
Specification