Point of view distributed agent methodology for network management

• US 20060074946A1
• Filed: 09/27/2005
• Published: 04/06/2006
• Est. Priority Date: 09/27/2004
• Status: Abandoned Application

• Current Assignee: PerformanceIT, Inc.
• Original Assignee: Performance It
• Inventors: Pham, Nguyen K.
• Application Number:
  US11/236,469
• Publication Number:
  US 20060074946A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/042 comprising distributed management centres cooperatively managing the network
• CPC Class Codes: H04L 41/046 comprising network management agents or mobile agents therefor

Abstract

The invention relates to a system and method for monitoring and diagnosis of issues experienced from a client system'"'"'s point of view. More particularly, the invention relates to a system and method for monitoring and diagnosis of issues experienced from a client system relating to synthetic or observed transactions involving the client system, or overall performance of the client system, taking into account that the system is member of a larger set of similar systems.

Claims

1. A system for the client-based perspective monitoring and diagnosis of issues relating to a client system, the system comprising:

a central server, wherein a point-of-view agent aggregator resides at the central server, the point-of-view agent aggregator maintains communication and aggregates data that is received from point-of-view agents;

at least one client system, wherein the client system is in communication with the central server;

a plurality of point-of-view agents, wherein at least one agent resides within at least one client system and is in communication with the central server, the point-of-view agent being configured to monitor the client system'"'"'s operations from the client system'"'"'s perspective and transmit the acquired monitored data to the central server and a point-of-view agent coordinator; and

a point-of-view agent coordinator, either residing locally at the central server or at a remote server that is in communication with the central server and the plurality of point-of-view agents, wherein the point-of-view agent coordinator transmits control commands to the plurality of point-of-view agents.

2. The system of claim 1, further comprising a repository residing at the central server, wherein the repository is in communication with the point-of-view aggregator and an analytical engine, data transmitted from the plurality of point-of-view agents to the point-of-view aggregator being stored within the repository.

3. The system of claim 2, further comprising an analytical engine residing at the central server, wherein the analytical engine is in communication with the point-of-view aggregator, wherein the analytical engine assigns respective client systems to groups based upon runtime, environmental, and use criteria.

4. The system of claim 3, wherein the analytical engine uses the data acquired from the point-of-view agents to determine client system baselines, identify deviant client systems, the determination of commonalities between deviant client systems, and the determination of the commonalities between deviant client systems and non-deviant client systems.

5. The system of claim 4, wherein the analytical engine reports its findings to a publisher, wherein the publisher packages and transmits the findings to a network management system.

6. The system of claim 5, wherein the point-of-view-agent coordinator transmits a command to a specific point-of-view agent to perform a predetermined client system monitoring function.

7. The system of claim 6, wherein upon the completion of the predetermined client system monitoring function, the point-of-view agent will transmit a performance-completed message to the point-of-view coordinator.

8. The system of claim 7, wherein if the point-of-view agent determines that the predetermined client system monitoring function has not been completed within a specified time, the point-of-view agent will reassign the predetermined client system monitoring function to another point-of-view agent to complete.

9. The system of claim 8, wherein upon the detection of a deviant client system an alarm function is initiated.

10. A method for the client-based perspective monitoring and diagnosis of issues relating to a client system, the method comprising the steps of:

distributing a plurality of point-of-view agents on at least one client system, wherein the point-of-view agents monitor predetermined operations of the client system;

coordinating the collection of the client system monitoring data acquired by the point-of-view agents;

confirming the validity of the acquired client system data;

assigning respective client systems to groups based upon runtime, environmental, and use criteria;

analyzing the acquired data in order to ascertain any commonalities that may exist between the data of differing client systems and differing groupings of client systems;

identifying a deviant client system in the event that the acquired data in regard to the client system determines that the client system behavior is deviant; and

initiating an alarm function that identifies the deviant client system.

11. The method of claim 10, wherein the step of coordinating the collection of client system monitoring data further comprises the step of distributing specific monitoring functions to individual point-of-view agents.

12. The method of claim 11, wherein the step of coordinating the collection of client system monitoring data further comprises the step of verifying the completion the individual point-of-view agents specific monitoring functions.

13. The method of claim 12, wherein if it is determined that a point-of-view agent has not completed a specific monitoring function, the monitoring function is assigned to a different point-of-view agent.

14. The method of claim 10, wherein the step of collecting the client system monitoring data further comprises the step of collecting the client system data from the point-of-view agents based upon the a point-of-view agent'"'"'s perspective of its operating and runtime environment in addition to synthetic or observed client transactions.

15. The method of claim 10, wherein the step of identifying a deviant client system further comprises the steps of:

determining whether the acquired data in regard to a specific client system originated at an operating environment of the point-of-view agent reporting the deviant behavior;

determining whether multiple point-of-view agents reported similar deviant behavior; and

correlating diagnostic information related to network availability and performance from multiple agents.

16. The method of claim 10, wherein the step of coordinating the collection of the client system monitoring data acquired by the point-of-view agents further comprises the steps of the point-of-view agents collecting data through the execution of assigned jobs.

17. The method of claim 16, wherein the execution of jobs by point-of-view agents further comprises the steps of accounting for current system load, and awareness of the client system'"'"'s operating environment.

18. The method of claim 17, wherein the accounting for current system load and awareness of the client system'"'"'s operating environment comprises implementing point-of-view agents that have negligible impact on actively used client systems.

19. The method of claim 18, wherein respective point-of-view agents periodically request updated job assignment information.

20. The method of claim 19, wherein point-of-view agents with negligible impact on actively used systems can hibernate until needed.

21. The method of claim 10, wherein deviant client systems can automatically be detected and the commonalities between deviant systems and non-deviant systems can be determined.

22. The method of claim 21, further comprising the step of determining baselines for the purpose of assisting in detecting deviation within a client system.

23. The method of claim 22, wherein baselines are composed of environmental, numerical runtime, and runtime components.

24. The method of claim 21, further comprising the step of comparing each client system to a group baseline.

25. The method of claim 21, further comprising the step of determining the commonalities, and differences in commonalities between deviant and non-deviant client systems.

26. The method of claim 25, further comprising the step of determining the difference set between any two groups of commonalities.

27. A computer program product that includes a computer readable medium that is usable by a processor, the medium having stored thereon a sequence of instructions that when executed by a processor causes the data unit processor to execute the steps of:

coordinating the collection of the client system monitoring data acquired by the point-of-view agents;

confirming the validity of the acquired client system data;

assigning respective client systems to groups based upon runtime, environmental, and use criteria;

analyzing the acquired data in order to ascertain any commonalities that may exist between the data of differing client systems and differing groupings of client systems;

identifying a deviant client system in the event that the acquired data in regard to the client system determines that the client system behavior is deviant; and

initiating an alarm function that identifies the deviant client system.