Monitoring network entities via a central monitoring system

• US 9,438,493 B2
• Filed: 01/31/2013
• Issued: 09/06/2016
• Est. Priority Date: 01/31/2013
• Status: Active Grant

• Current Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Original Assignee: Go Daddy Operating Company LLC (GoDaddy, Inc.)
• Inventors: Reynolds, Daymion, Mink, Jeff, Condit, Craig, Boltz, Chris
• Primary Examiner(s): Tiv, Backhean
• Application Number:
  US13/756,316
• Publication Number:
  US 20140215055A1
• Time in Patent Office: 1,314 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 41/22 comprising specially adapted graphical user interfaces [GUI]
• CPC Class Codes: H04L 43/022 by sampling
• CPC Class Codes: H04L 43/08 Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
• CPC Class Codes: H04L 43/14 using software, i.e. software packages network security related monitoring H04L63/1408

Abstract

Systems and method of the present invention provide for one or more server computers configured to receive a plurality of data published by a network entity and identify, within the data: the network entity that published the data, a sample of one or more metrics for the network entity and a sample type of each of the one or more samples. The one or more server computers may further be configured to calculate a network resource usage score, using the one or more metrics according to one or more rules for each of the sample types identified, for the sample.

Claims

1. A method, comprising the steps of:

subscribing, by a single instance of a network monitoring software running on a server computer coupled to a network, to at least one topic defining a common purpose for a server cluster comprising a plurality of servers configured according to a diversity of configuration settings;

decoding, by the server computer, an extensible markup language (XML) file published via data stream by at least one server in the plurality of servers, the XML file comprising;

a server identification for the at least one server that published the XML file;

a numeric value representing sample of performance metric, which has not been analyzed, or on which no algorithms have been performed, by the at least one server; and

a sample type of the at least one sample, the sample type comprising a definition of the common purpose for the server cluster;

normalizing, by the server computer, the numeric value according to the diversity of configuration settings among the cluster;

calculating, by the server computer, according to at least one scoring rule for the sample type, as defined in an XML configuration file, score comprising the numeric value as normalized;

rendering, by the server computer, a user interface comprising the score;

responsive to a determination that the score is outside a minimum or maximum boundary for a specified period of time, as defined for the sample type in at least one alert rule in the XML configuration file, rendering, by the server computer, on the user interface, an alert comprising;

the server identification for the server that scored outside the minimum or maximum boundary;

the score, including a score interpretation; and

a recommended action to resolve a cause of the alert, as defined for the sample type within at least one recommendation rule in the XML configuration file; and

transmit the user interface to a client computer coupled to the network.

2. The method of claim 1, wherein the XML file further comprises:

an identity of the at least one server; and

a data feed of the sample, wherein the at least one server has run no calculations on the sample or the metric.

3. The method of claim 1, wherein the at least one server comprises:

a network node comprising a computer or an other server computer;

a server cluster comprising a plurality of network nodes;

a plurality of unrelated network nodes across one or more server clusters acting with the common purpose;

a plurality of unrelated network nodes across one or more server clusters generating a plurality of data that can be grouped together;

a plurality of unrelated network nodes across one or more server clusters with a common operating system;

or

at least one metric reflecting usage of the at least one server by a user.

4. The method of claim 1, wherein the XML file is published via a message broker software utilizing a publish/subscribe model, wherein:

the at least one server publishes the sample of the metric as a message topic;

the server computer is configured to subscribe to the message topic and receive;

an identity of the at least one server that published the data;

the sample of the metric; and

the sample type for the sample.

5. The method of claim 1, wherein the XML configuration file controls:

extraction of a plurality of identifying information from the XML file, to determine;

the server computer the sample applies to;

the sample; and

the sample type;

calculation of at least one network resource usage score;

generation of the alert based on the at least one network resource usage score;

or

extraction of the sample from the XML file.

6. The method of claim 1, wherein the XML configuration file:

is written using a general-purpose language;

is applicable to any entity which is represented in a sample; and

has access to at least one previous sample for the at least one server.

7. The method of claim 1, wherein the sample comprises a collection of data containing at least one measurement of data for the at least one server over the specific period of time.

8. The method of claim 1, wherein the sample type:

comprises a format for the sample, the format defining a plurality of data that the sample contains; and

determines the at least one scoring rule applied to the sample.

9. The method of claim 1, wherein the sample type:

comprises information about a purpose of the at least one server; and

determines, based on the purpose of the at least one server, the at least one scoring rule applied when calculating at least one network resource usage score.

10. The method of claim 1, wherein at least one network resource usage score:

measures a metric performance or a usage of the at least one server; and

comprises;

the numeric value;

a category defining how the numeric value should be interpreted; and

the at least one server associated with the category and the at least one network resource usage score.

11. The method of claim 1, wherein the XML configuration file controls:

generation of a plurality of scores;

generation of the plurality of scores using a plurality of samples comprising a plurality of different sample types;

or

generation of one or more different categories of scores based on information included in the plurality of samples.

12. The method of claim 1, wherein at least one network resource usage score:

is calculated for a plurality of network nodes;

is calculated for at least one cluster of network nodes;

or

is calculated for at least one user of the plurality of network nodes.

13. The method of claim 1, wherein at least one network resource usage score:

is calculated using at least one scoring script running on the server computer; and

is calculated using;

the XML file published by the at least one server; and

an additional data published by an additional network entity.

14. The method of claim 1, further comprising the steps of:

monitoring, by the server computer, at least one network resource usage score;

determining, by the server computer, whether the at least one network resource usage score is outside the minimum or maximum boundary for a specified period of time;

responsive to a determination that the at least one network resource usage score is outside the minimum or maximum boundary for the specified period of time, generating and triggering, by the server computer, the alert indicating a detected issue with the at least one server; and

transmitting, by the server computer, the alert to the client computer communicatively coupled to the network.

15. The method of claim 1, wherein the score triggers the alert indicating a detected issue with the at least one server, the alert being triggered based on:

an entity type the alert applies to; and

a score category the alert applies to.

16. A system, comprising a single instance of a network monitoring software running on a server computer communicatively coupled to a network and configured to:

subscribe to at least one topic defining a common purpose for a server cluster comprising a plurality of servers configured according to a diversity of configuration settings;

decoding, by the server computer, an extensible markup language (XML) file published via data stream by at least one server in the plurality of servers, the XML file comprising;

a server identification for the at least one server that published the XML file;

a numeric value representing sample of performance metric, which has not been analyzed, or on which no algorithms have been performed, by the at least one server; and

a sample type of the at least one sample, the sample type comprising a definition of the common purpose for the server cluster; and

normalize the numeric value according to the diversity of configuration settings among the cluster;

calculate, according to at least one scoring rule for the sample type, as defined in an XML configuration file, a score comprising the numeric value as normalized;

render a user interface comprising the score;

responsive to a determination that the score is outside a minimum or maximum boundary for a specified period of time, as defined for the sample type in at least one alert rule in the XML configuration file, render, on the user interface, an alert comprising;

the server identification for the server that scored outside the minimum or maximum boundary;

the score, including a score interpretation; and

a recommended action to resolve a cause of the alert, as defined for the sample type within at least one recommendation rule in the XML configuration file; and

transmit the user interface to a client computer coupled to the network.

17. The system of claim 16, wherein the single instance of the network monitoring software is configured to:

normalize and compare a data between a plurality of nodes in the network;

determine if at least one network resource usage score is outside a minimum or maximum boundary for a specified period of time;

responsive to a determination that the at least one network resource usage score is outside the minimum or maximum boundary for the specified period of time, generate and trigger the alert indicating a detected issue.

18. The system of claim 17, wherein the single instance of the network monitoring software comprises:

an application programming interface running on the server computer;

at least one web service;

or

the XML configuration file defining the behavior of the server computer or the single instance of the network monitoring software, the XML configuration file comprising configurations to;

subscribe to at least one message topic;

receive the sample of the metric;

calculate the score;

determine if at least one network resource usage score is outside the minimum or maximum boundary for the specified period of time; and

responsive to a determination that the at least one network resource usage score is outside the minimum or maximum boundary for the specified period of time, generate and trigger the alert indicating a detected issue.

19. The system of claim 17, further comprising a response engine configured to:

receive the alert indicating the detected issue; and

generate at least one available action to be taken to correct the alert.