Monitoring highly distributed computer systems

• US 10,362,135 B2
• Filed: 02/21/2017
• Issued: 07/23/2019
• Est. Priority Date: 02/21/2017
• Status: Active Grant

• Current Assignee: Experian Health, Inc. (Experian plc)
• Original Assignee: Experian Health, Inc. (Experian plc)
• Inventors: McNeese, Brian, Pilkington, Edmond Chase, Phoebus, David Stephen, Henson, Jeffery, Wallis, Jason Harrison, Ochs, Michael Peter
• Primary Examiner(s): Whipple, Brian
• Application Number:
  US15/438,308
• Publication Number:
  US 20180241835A1
• Time in Patent Office: 882 Days
• Field of Search: None
• CPC Class Codes: H04L 41/0273 using web services for network management, e.g. simple object access protocol [SOAP]
• CPC Class Codes: H04L 43/045 for graphical visualisation of monitoring data
• CPC Class Codes: H04L 43/0823 Errors, e.g. transmission errors
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
• CPC Class Codes: H04L 67/568 Storing data temporarily at an intermediate stage, e.g. caching

Abstract

Aspects described herein pertain to monitoring and/or remediating operational components distributed throughout a distributed computer architecture, but is not so limited. A disclosed system provides monitoring information associated with a plurality of monitored server computers, wherein the monitoring information includes processing data, storage data, control data, and/or error data to quantify an operational state of one or more of the monitored server computers. A disclosed method monitors information associated with a plurality of monitored server computers, wherein the monitoring information includes processing data, storage data, control data, and the error data to quantify an operational state of one or more of the monitored server computers.

Claims

1. A distributed computer system comprising:

a first server that includes a collector to collect processing queue data, storage queue data, control queue data, and error queue data associated with the first server;

a second server that includes a collector to collect processing queue data, storage queue data, control queue data, and error queue data associated with the second server;

a third server that includes a collector to collect processing queue data, storage queue data, control queue data, and error queue data associated with the third server;

a monitor server communicatively coupled to the first server, the second server, and the third server via one or more computer networks, wherein the monitor server receives the processing queue data, the storage queue data, the control queue data, and the error queue data from each of the first server, the second server, and the third server;

a storage database to store the processing queue data, the storage queue data, the control queue data, and the error queue data collected from each of the first server, the second server, and the third server; and

a caching tier to store most recent processing queue data, most recent storage queue data, most recent control queue data, and most recent error queue data collected from each of the first server, the second server, and the third server.

2. The system of claim 1, further comprising:

a web service to extract, from the caching tier, the most recent processing queue data, the most recent storage queue data, the most recent control queue data, and the most recent error queue data from each of the first server, the second server, and the third server; and

a dashboard user interface (UI) to display aspects of the processing queue data, the storage queue data, the control queue data, and the error queue data for each of the first server, the second server, and the third server.

3. The system of claim 2, wherein the dashboard UI operates, for each of the first server, the second server, and the third server, to display a first threshold and a second threshold associated with the processing queue data, a first threshold and a second threshold associated with the storage queue data, a first threshold and a second threshold associated with the control queue data, and a first threshold and a second threshold associated with the error queue data.

4. The system of claim 3, wherein the dashboard UI operates, for each of the first server, the second server, and the third server, further to display a processing queue value, a storage queue value, a control queue value, and an error queue value.

5. The system of claim 4, wherein the dashboard UI operates further to display:

a server name, a process type, and a time elapsed since displaying a first widget containing the processing queue value, the storage queue value, the control queue value, and the error queue value associated with the first server;

a server name, a process type, and a time elapsed since displaying a second widget containing the processing queue value, the storage queue value, the control queue value, and the error queue value associated with the second server; and

a server name, a process type, and a time elapsed since displaying a third widget containing the processing queue value, the storage queue value, the control queue value, and the error queue value associated with the third server.

6. The system of claim 2, wherein the dashboard UI operates to display:

a first widget for the first server that displays;

an identifier for the first server, a process type running on the first server, a first threshold and a second threshold associated with the processing queue data for the first server, a first threshold and a second threshold associated with the storage queue data for the first server, a first threshold and a second threshold associated with the control queue data for the first server, and a first threshold and a second threshold associated with the error queue data for the first server;

a second widget for the second server that displays;

an identifier for the second server, a process type running on the second server, a first threshold and a second threshold associated with the processing queue data for the second server, a first threshold and a second threshold associated with the storage queue data for the second server, a first threshold and a second threshold associated with the control queue data for the second server, and a first threshold and a second threshold associated with the error queue data for the second server; and

a third widget for the third server that displays;

an identifier for the third server, a process type running on the third server, a first threshold and a second threshold associated with the processing queue data for the third server, a first threshold and a second threshold associated with the storage queue data for the third server, a first threshold and a second threshold associated with the control queue data for the third server, and a first threshold and a second threshold associated with the error queue data for the third server.

7. The system of claim 6, wherein the dashboard UI operates to display a low priority section, a medium priority section, and a high priority section to contain one or more of the first widget, the second widget, and the third widget.

8. The system of claim 7, wherein the dashboard UI operates to relocate one or more of the first widget, the second widget, and the third widget from a current priority section to a new priority section.

9. The system of claim 8, wherein the dashboard UI displays the low priority section below or to the left of the medium priority section and displays the medium priority section below or to the left of the high priority section.

10. The system of claim 1, wherein the dashboard UI includes a control interface that operates to display trending data associated with one or more of the processing queue data, the storage queue data, the control queue data, and the error queue data for each one of the first server, the second server, and the third server.

11. The system of claim 1, further comprising:

a processing queue to maintain a number of transactions to process for each of the first server, the second server, and the third server;

a storage queue to maintain a current processing capacity for each of the first server, the second server, and the third server;

a control queue to maintain notifications of an ability to process one or more transactions for each of the first server, the second server, and the third server; and

an error queue to maintain a number of error messages for each of the first server, the second server, and the third server.

12. A method performed in a distributed computer architecture that includes a number of monitored servers, the method comprising:

installing a collector on each monitored server associated with the distributed computer architecture;

using the collector to collect processing queue data, storage queue data, control queue data, and error queue data from each monitored server associated with the distributed computer architecture;

storing, in a database, the processing queue data, storage queue data, control queue data, and error queue data for each monitored server associated with the distributed computer architecture;

caching most recent processing queue data, most recent storage queue data, most recent control queue data, and most recent error queue data for each monitored server associated with the distributed computer architecture; and

displaying aspects of the processing queue data, the storage queue data, the control queue data, and the error queue data for each monitored server associated with the distributed computer architecture, wherein the displaying includes displaying threat assessment thresholds and current values associated with the processing queue data, the storage queue data, the control queue data, and the error queue data for each monitored server associated with the distributed computer architecture.

13. The method of claim 12, further comprising displaying a widget for each monitored server associated with the distributed computer architecture including:

displaying a first threshold, a second threshold, and a current value associated with the processing queue data for each widget;

displaying a first threshold, a second threshold, and a current value associated with the storage queue data for each widget;

displaying a first threshold, a second threshold, and a current value associated with the control queue data for each widget; and

displaying a first threshold, a second threshold, and a current value associated with the error queue data for each widget.

14. The method of claim 13, further comprising displaying each widget in one or more of a low priority section, a medium priority section, and a high priority section.

15. The method of claim 14, further comprising relocating a widget from one of the low priority section, the medium priority section, and the high priority section to a different section.

16. The method of claim 14, further comprising using different colors to distinguish the low priority section, the medium priority section, and the high priority section.

17. The method of claim 12, further comprising providing at least one control interface with each widget that operates to display trending data associated with one or more of the processing queue data, the storage queue data, the control queue data, and the error queue data.

18. A non-transitory computer readable medium that includes instructions which, when executed as part of a distributed computer architecture:

receive processing queue data, storage queue data, control queue data, and error queue data from each monitored server associated with the distributed computer architecture;

store, in a database, the processing queue data, storage queue data, control queue data, and error queue data for each monitored server associated with the distributed computer architecture;

cache most recent processing queue data, most recent storage queue data, most recent control queue data, and most recent error queue data for each monitored server associated with the distributed computer architecture; and

display aspects of the processing queue data, the storage queue data, the control queue data, and the error queue data for each monitored server associated with the distributed computer architecture, wherein to display includes a display of threat assessment thresholds and current values associated with the processing queue data, the storage queue data, the control queue data, and the error queue data for each monitored server associated with the distributed computer architecture.

19. The non-transitory computer readable medium of claim 18, further configured to display a widget for each monitored server associated with the distributed computer architecture including:

displaying a first threshold, a second threshold, and a current value associated with the processing queue data for each widget;

displaying a first threshold, a second threshold, and a current value associated with the storage queue data for each widget;

displaying a first threshold, a second threshold, and a current value associated with the control queue data for each widget; and

displaying a first threshold, a second threshold, and a current value associated with the error queue data for each widget.

20. The non-transitory computer readable medium of claim 19, further configured to provide at least one control interface with each widget that operates to display trending data associated with one or more of the processing queue data, the storage queue data, the control queue data, and the error queue data.