Performance Monitoring Infrastructure for Distributed Transaction Service

• US 20080306712A1
• Filed: 10/01/2007
• Published: 12/11/2008
• Est. Priority Date: 06/08/2007
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Chen, Wei
• Granted Patent: US 8,898,277 B2
• Time in Patent Office: Days
• US Class Current: 702/186
• CPC Class Codes: G06F 11/3495 for systems
• CPC Class Codes: G06F 2201/865 Monitoring of software

Abstract

A computer-implemented system to support performance monitoring of distributed transaction service can comprise a monitoring management tier that provides services to a monitoring logic and policy control module; one or more monitoring processes that are controlled by the monitoring logic and policy control module; and a plug-in framework that includes one or more plug-ins that is capable of receiving monitoring data from the one or more monitoring processes.

Claims

1. A computer-implemented system to support performance monitoring of distributed transaction service, comprising:

a monitoring management tier that provides services to a monitoring logic and policy control module;

one or more monitoring processes that are controlled by the monitoring logic and policy control module; and

a plug-in framework that includes one or more plug-ins that is capable of receiving monitoring data from the one or more monitoring processes.

2. The system according to claim 1, wherein:

the monitoring management tier performs at least one of;

monitoring specification parsing;

environment variable recognition;

specification for a particular node, group and server; and

Bulletin Board and process level cooperation;

3. The system according to claim 1, wherein:

the monitoring process is one of;

an application monitoring process;

a service monitoring process;

a transaction monitoring process;

or

a system monitoring process.

4. The system according to claim 3, wherein:

the application monitoring process contains a monitoring initiator that initiates a call path tree.

5. The system according to claim 1, wherein:

the monitoring data are performance metrics that are consistent with application correlation.

6. The system according to claim 1, wherein:

the monitoring logic and policy control module is capable of performing;

selecting monitoring points based on monitoring category;

defining logic at monitoring points; and

handling performance metrics collection.

7. The system according to claim 1, wherein:

the plug-in framework uses a fan-out plug-in model.

8. The system according to claim 1, further comprising:

an API to provide application request monitoring metrics.

9. The system according to claim 1, further comprising:

a presentation layer that is connected with the plug-in Framework through at least one of;

a monitoring services component;

a network channel;

or

a database.

10. A computer-implemented method to support performance monitoring of distributed transaction service, comprising:

selecting monitoring points based on monitoring category;

defining monitoring logic at monitoring points;

handling monitoring data collection; and

passing monitoring data to a plug-in.

11. The method according to claim 10, further comprising:

performing monitoring management services which includes at least one of;

monitoring specification parsing;

environment variable recognition;

specification for a particular node, group and server; and

Bulletin Board and process level cooperation;

12. The method according to claim 10, wherein:

there are at least four monitoring categories;

application monitoring;

service monitoring;

transaction monitoring; and

system monitoring.

13. The method according to claim 10, further comprising:

inititating a call path tree;

14. The method according to claim 10, wherein:

the monitoring data are performance metrics that are consistent with application correlation.

15. The method according to claim 10, wherein:

the plug-in is part of a plug-in framework which uses a fan-out plug model.

16. The method according to claim 10, further comprising:

providing an API to output application request monitoring metrics.

17. The method according to claim 10, further comprising:

outputting monitoring data to a presentation layer that is connected with the plug-in Framework through at least one of;

a monitoring services component;

a network channel;

or

a database.

18. A machine readable medium having instructions stored thereon that when executed cause a system to:

select monitoring points based on monitoring category;

define monitoring logic at monitoring points;

handle monitoring data collection; and

pass monitoring data to a plug-in.

19. The machine readable medium of claim 18, further comprising instructions that when executed cause the system to:

perform monitoring management services which includes at least one of;

monitoring specification parsing;

environment variable recognition;

specification for a particular node, group and server; and

Bulletin Board and process level cooperation;

20. The machine readable medium of claim 18, wherein:

there are at least four monitoring categories;

application monitoring;

service monitoring;

transaction monitoring; and

system monitoring.

21. The machine readable medium of claim 18, further comprising instructions that when executed cause the system to:

inititate a call path tree;

22. The machine readable medium of claim 18, wherein:

the monitoring data are performance metrics that are consistent with application correlation.

23. The machine readable medium of claim 18, wherein:

the plug-in is part of a plug-in framework which uses a fan-out plug model.

24. The machine readable medium of claim 18, further comprising instructions that when executed cause the system to:

provide an API to output application request monitoring metrics.

25. The machine readable medium of claim 18, further comprising instructions that when executed cause the system to:

output monitoring data to a presentation layer that is connected with the plug-in Framework through at least one of;

a monitoring services component;

a network channel;

or

a database.