System and method for performance management in a multi-tier computing environment

• US 7,805,509 B2
• Filed: 03/23/2005
• Issued: 09/28/2010
• Est. Priority Date: 06/04/2004
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: OpTier
• Inventors: Alon, Amir, Tal, Mordechai, Lavi, Yoram Yori
• Primary Examiner(s): Nguyen; Thu Ha T
• Application Number:
  US11/088,277
• Publication Number:
  US 20060015512A1
• Time in Patent Office: 2,015 Days
• Field of Search: 709/222, 709/223, 709/224, 709/227, 709/202, 370/351, 370/252, 714/39
• US Class Current: 709/224
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/23 Bit dropping
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/125 involving control of end-device applications over a network

Abstract

Apparatus for monitoring a selected tier in a multi-tier computing environment, the apparatus including a context agent and a dynamic tier extension, the context agent associated with the selected tier and coupled with other context agents, each of which is associated with a respective tier, the dynamic tier extension coupled with the context agent and with specific predetermined points of the selected tier, the dynamic tier extension monitoring request traffic passing through the selected tier, the monitored request traffic including at least one entering request received at a request entry port from an adjacent tier, the dynamic tier extension identifying each request in the monitored request traffic and sending at least a request identifier to the context agent, the context agent also receiving information relating to the request context of the entering request from the context agent associated with the adjacent tier, the context agent associating the information relating to the request context of the entering request with the entering request, in accordance with the received request identifier.

Claims

1. A system for monitoring a selected tier in a multi-tier computing environment, said system comprising:

a central processing unit (CPU); and

storage coupled to the CPU for storing instructions that configure the CPU to;

implement a context agent associated with said selected tier of said computing environment, said context agent being coupled with other context agents, each of said other context agents associated with a respective tier of said computing environment; and

implement a dynamic tier extension, said dynamic tier extension coupled with said context agent and with at least a request entry port of said selected tier, at least for monitoring request traffic passing through said selected tier, said monitored request traffic including at least one entering request received at said request entry port from an adjacent tier of said computing environment, said dynamic tier extension providing request information to said context agent, said request information at least identifying each request included in said monitored request traffic,

said context agent for receiving context information directly from another context agent associated with said adjacent tier, said received context information relating to the request context of said at least one entering request, said context agent also for associating said context information with said request information for each said at least one entering request.

2. The system according to claim 1, wherein said dynamic tier extension is further coupled with at least a request exit port of said selected tier, and wherein said monitored request traffic further includes at least one exiting request received at said request exit port, said selected tier providing said at least one exiting request to another adjacent tier of said computing environment, wherein said context agent associates between said at least one exiting request and said at least one entering request;

and sends context information relating to the request context of said at least one exiting request to a further context agent associated with said another adjacent tier.

3. The system according to claim 2, wherein said context agent comprises:

an agent communication interface, relaying messages between said dynamic tier extension and said context agent;

an agent messaging module, notifying said further context agent that said at least one exiting request has been sent to said another adjacent tier, said agent messaging module further communicating with said dynamic tier extension using messages; and

a context table manager, maintaining a reference table associating at least one unit of work running on said selected tier with said request context of said at least one entering request to which said unit of work has been allocated, said reference table being a context table, said context table further storing information associated with said at least one entering request, said context table manager further identifying at least one entering request based on information stored in said context table.

4. The system according to claim 3, wherein said context agent further comprises:

a classification manager, performing classification of said at least one entering request based on said received context information, said classification manager further identifying said at least one entering request as part of a transaction.

5. The system according to claim 3, wherein said context agent further comprises:

an agent log event handler, performing event logging, internal tracing and messaging, and detection of operational irregularities within said context agent.

6. The system tem according to claim 3, wherein said context agent further comprises:

an agent administrator, archiving information, sending historical data to a context network management server (CNMS) and receiving active service class policies and additional data from said CNMS.

7. The system according to claim 4, wherein said context agent further comprises:

a policy manager, assigning a service class to said at least one entering request according to an active service class policy and said classification of said at least one entering request.

8. The system according to claim 1, wherein said dynamic tier extension is further coupled with a tier control port of said selected tier.

9. The system according to claim 8, wherein said context agent further alters the priority level of a processing enclave executing said at least one entering request.

10. The system according to claim 8, wherein said context agent further alters the type of execution of a processing enclave executing said at least one entering request.

11. The system according to claim 8, wherein said dynamic tier extension comprises:

a dynamic tier extension daemon, performing asynchronous processing associated with reported events where said at least one entering request is not detained;

a dynamic tier extension messaging module, communicating with said context agent using messages; and

a dynamic tier extension communication interface, relaying messages between said dynamic tier extension and said context agent.

12. The system according to claim 11, wherein said dynamic tier extension further comprises:

a dynamic tier extension administrator, enabling said dynamic tier extension to receive messages relating to how said at least one entering request should be processed.

13. The system according to claim 11, wherein said dynamic tier extension further comprises:

a dynamic tier extension log event handler, logging tracing information concerning operation of said dynamic tier extension and logging alerts raised by said dynamic tier extension.

14. The system according to claim 8, wherein said dynamic tier extension collects performance, availability, and error metrics from said selected tier.

15. The system according to either of claim 1 or 8, wherein said context agent further adjusts the order of said at least one entering request on a queue at said request entry port.

16. The system according to either of claim 1 or 8, wherein said context agent further instructs said selected tier to allocate computational resources to process said at least one entering request.

17. The system according to either of claim 1 or 8, wherein said context agent further instructs said selected tier to deny computational resources to process said at least one entering request.

18. The system according to claim 1, wherein said context information includes at least a request identifier, a transaction identifier, a request class, and context related data.

19. The system according to claim 18, wherein said context related data includes the entire said request context of said at least one entering request.

20. The system according to claim 18, wherein said context related data includes a portion of said request context of said at least one entering request.

21. The system according to claim 18, wherein said context related data includes an indication to said request context of said at least one entering request.

22. The system according to claim 1, wherein said context agent resides on the same host machine as said selected tier.

23. The system according to claim 2, wherein said dynamic tier extension associates said at least one entering request with a processing enclave, said processing enclave being allocated for executing said at least one entering request on said selected tier.

24. The system according to claim 23, wherein said processing enclave producing said at least one exiting request in consequence with said at least one entering request, and wherein said dynamic tier extension associates said at least one exiting request with said processing enclave.

25. The system according to claim 24, wherein said dynamic tier extension associates between said at least one exiting request and said at least one entering request according to the association of said at least one entering request and said at least one exiting request with said processing enclave.

26. The system according to claim 1, wherein said context agent associates said context information with said request information, prior to the processing of said entering request within said selected tier.

27. A system for monitoring a selected tier in a multi-tier computing environment, said system comprising:

a central processing unit (CPU); and

storage coupled to the CPU for storing software code that configures the CPU to;

implement a context agent associated with said selected tier, said context agent being coupled with at least one other context agent, each of said at least one other context agent being associated with a respective tier of said computing environment; and

implement a dynamic tier extension, said dynamic tier extension coupled with said context agent and with at least a request entry port and a request exit port of said selected tier, said dynamic tier extension at least monitoring request traffic passing through said selected tier, said monitored request traffic including at least one entering request received at said request entry port and at least one respective exiting request at said request exit port, said selected tier providing said at least one respective exiting request to an adjacent tier, said dynamic tier extension capturing a request context of said at least one entering request, said dynamic tier extension providing request information and context information to said context agent, said request information at least identifying each request included in said monitored request traffic, said context information relating to said captured request context of said at least one entering request,

said context agent for associating said at least one entering request with said at least one exiting request, and said context agent also for providing context information relating to the request context of said at least one respective exiting request directly to another context agent associated with said adjacent tier.

28. The system according to claim 27, wherein said at least one entering request is a user request received from a user application.

29. The system according to claim 27, wherein said context information includes at least a request identifier, a transaction identifier, a request class, and context related data.

30. The system according to claim 27, wherein said context agent classifies said at least one entering request into a request class in accordance with said context information.

31. The system according to claim 30, wherein said context agent contains a set of tier-specific service class policies, each of said tier-specific service class policies mapping a service class to a request class for said selected tier, wherein an active service class policy contains the request class to service class mapping that is currently in effect;

and wherein said context agent assigns a service class to said at least one entering request based on said request class and the appropriate active service class policy in said set of tier-specific service class policies.

32. The system according to claim 30, wherein said context agent contains a set of tier-specific service class policies, each of said tier-specific service class policies mapping a service class to a request class for said selected tier,

wherein an active service class policy contains the request class to service class mapping that is currently in effect;

and

wherein said context agent assigns a service class to said at least one entering request different than the service class designated by said request class and the appropriate active service class policy in said set of tier-specific service class policies.

33. The system according to either of claim 31 or 32, wherein said service class includes the priority to be assigned to said at least one entering request.

34. The system according to either of claim 31 or 32, wherein said service class includes the central processing unit percentage to be allocated to said at least one entering request.

35. The system according to either of claim 31 or 32, wherein said service class includes the memory to be allocated to said at least one entering request.

36. The system according to either of claim 31 or 32, wherein said service class includes the priority in allocating and accessing input and output devices to said at least one entering request.

37. The system according to either of claim 31 or 32, wherein said service class policies are periodically updated.

38. The system according to either of claim 31 or 32, wherein said service class policies are defined by a user of said multitier computing environment.

39. The system according to either of claim 31 or 32, wherein said context agent adds said assigned service class to said request context.

40. The system according to claim 27, wherein said dynamic tier extension is further coupled with a tier control port of said selected tier.

41. The system according to claim 40, wherein said context agent further alters the priority level of a processing enclave executing said at least one entering request.

42. The system according to claim 40, wherein said context agent further alters the type of execution of a processing enclave executing said at least one entering request.

43. The system according to claim 40, wherein said dynamic tier extension comprises:

a dynamic tier extension daemon, performing asynchronous processing associated with reported events where said at least one entering request is not detained;

a dynamic tier extension messaging module, communicating with said context agent using messages; and

a dynamic tier extension communication interface, relaying messages between said dynamic tier extension and said context agent.

44. The system according to claim 43, wherein said dynamic tier extension further comprises:

a dynamic tier extension administrator, enabling said dynamic tier extension to receive messages relating to how said at least one entering request should be processed.

45. The system according to claim 43, wherein said dynamic tier extension further comprises:

a dynamic tier extension log event handler, logging tracing information concerning operation of said dynamic tier extension and logging alerts raised by said dynamic tier extension.

46. The system according to claim 40, wherein said dynamic tier extension collects performance, availability, and error metrics from said selected tier.

47. The system according to either of claim 27 or 40, wherein said context agent further adjusts the order of said at least one entering request on a queue at said request entry port.

48. The system according to either of claim 27 or 40, wherein said context agent further instructs said selected tier to allocate computational resources to process said at least one entering request.

49. The system according to either of claim 27 or 40, wherein said context agent further instructs said selected tier to deny computational resources to process said at least one entering request.

50. The system according to claim 27, wherein said dynamic tier extension assigns a transaction identifier to each request included in said monitored request traffic.

51. The system according to claim 27, wherein said dynamic tier extension obtains a request identifier of each request included in said monitored request traffic.

52. The system according to claim 27, wherein said context agent comprises:

an agent communication interface, relaying messages between said dynamic tier extension and said context agent;

an agent messaging module, notifying said another context agent that said at least one exiting request has been sent to said another adjacent tier, said agent messaging module further communicating with said dynamic tier extension using messages;

a context table manager, maintaining a reference table associating at least one unit of work running on said selected tier with said request context of said at least one entering request to which said unit of work has been allocated, said reference table being a context table, said context table further storing information associated with said at least one entering request, said context table manager further identifying at least one entering request based on information stored in said context table;

a classification manager, performing classification of said at least one entering request based on said received context information, said classification manager further identifying said at least one entering request as part of a transaction; and

a policy manager, assigning a service class policy to said at least one entering request according to an active service class policy and said classification of said at least one entering request.

53. The system according to claim 52, wherein said context agent further comprises:

an agent log event handler, performing event logging, internal tracing and messaging, and detection of operational irregularities within said context agent.

54. The system according to claim 52, wherein said context agent further comprises:

an agent administrator, archiving information, sending historical data to a context network management server (CNMS) and receiving active service class policies and additional data from said CNMS.

55. The system according to claim 27, wherein said context agent resides on the same host machine as said selected tier.

56. The system according to claim 27, wherein said dynamic tier extension associates said at least one entering request with a processing enclave, said processing enclave being allocated for executing said at least one entering request on said tier, said processing enclave producing said at least one exiting request in consequence with said at least one entering request, said dynamic tier extension associates said at least one exiting request with said processing enclave, and wherein said dynamic tier extension associates between said at least one exiting request and said at least one entering request according to the association of said at least one entering request and said at least one exiting request with said processing enclave.

57. In a multi-tier computing environment including a plurality of tiers, a system for application performance management associated with at least two monitored tiers of said plurality of tiers, the system comprising, for each of said at least two monitored tiers:

a central processing unit (CPU); and

implement a respective dynamic tier extension coupled with at least a request entry port and a request exit port of said monitored tier, said dynamic tier extension at least monitoring request traffic passing through said respective monitored tier, said monitored request traffic including at least one entering request received at said request entry port and at least one respective exiting request at said request exit port, said selected tier providing said at least one respective exiting request to an adjacent respective monitored tier, said dynamic tier extension capturing a request context of said at least one entering request; and

implement respective context agent coupled with said respective dynamic tier extension, said context agent being coupled with other said context agents associated with tiers that are directly coupled with said respective tier, said respective context agent receiving request information from said respective dynamic tier extension, said request information at least identifying each request included in said monitored request traffic, said respective context agent further receives context information relating to the request context of said at least one entering request from said respective dynamic tier extension, for each said at least one entering request, said respective context agent associates said at least one entering request with said at least one exiting request, and said respective context agent provides context information relating to the request context of said at least one respective exiting request directly to another context agent associated with said adjacent tier.

58. The system according to claim 57, wherein each of said dynamic tier extensions is further coupled with at least a request exit port of said respective tier, and wherein said monitored request traffic further includes at least one exiting request received at said request exit port, said selected tier providing said at least one exiting request to another adjacent tier of said computing environment,

wherein said respective context agent associates said at least one exiting request with said at least one entering request;

and sends context information relating to the request context of said at least one exiting request to a further context agent associated with said another adjacent tier.

59. The system according to claim 58, wherein said dynamic tier extension associates said at least one entering request with a processing enclave, said processing enclave being allocated for executing said at least one entering request on said tier, said processing enclave producing said at least one exiting request in consequence with said at least one entering request, said dynamic tier extension associates said at least one exiting request with said processing enclave, and wherein said dynamic tier extension associates between said at least one exiting request and said at least one entering request according to the association of said at least one entering request and said at least one exiting request with said processing enclave.

61. The system according to either of claims 57 or 60, further comprising:

a context network management server (CNMS) coupled with said context agents, said CNMS at least collecting and analyzing performance data received from said context agents.

62. The system according to claim 61, further including a policy database coupled with said CNMS, said policy database storing at least service class policies.

63. The system according to claim 61, wherein said CNMS further performs activity profiling, creating an activity profile including integrated transaction, tier, and system level performance metrics and statistical analysis.

64. The system according to claim 62, further including a supervisor workstation coupled with said CNMS and with said policy database.

60. In a multi-tier computing environment including a plurality of tiers, a system for application performance management, associated with at least selected monitored tiers of said plurality of tiers, the system including one or more computer-readable media with one or more computer programs, the system comprising:

for each of at least two of said monitored tiers, a respective dynamic tier extension being coupled with at least a request entry port and a request exit port of said monitored tier, said dynamic tier extension at least monitoring request traffic passing through said respective monitored tier, said monitored request traffic including at least one entering request received at said request entry port and at least one respective exiting request at said request exit port, said selected tier providing said at least one respective exiting request to an adjacent respective monitored tier, said dynamic tier extension capturing a request context of said at least one entering request; and

for each of said at least two of said monitored tiers, a respective context agent, coupled with said respective dynamic tier extension, said context agent being coupled with other said context agents associated with tiers that are directly coupled with said respective tier, said respective context agent receiving request information from said respective dynamic tier extension, said request information at least identifying each request included in said monitored request traffic, said respective context agent further receives context information relating to the request context of said at least one entering request from said respective dynamic tier extension, for each said at least one entering request, said respective context agent associates said at least one entering request with said at least one exiting request, and said respective context agent provides context information relating to the request context of said at least one respective exiting request to another context agent associated with said adjacent tier.

65. The system according to claim 60, wherein said at least one entering request is a user request received from a user application.

66. The system according to claim 60, wherein said dynamic tier extension associates said at least one entering request with a processing enclave, said processing enclave being allocated for executing said at least one entering request on said tier, said processing enclave producing said at least one exiting request in consequence with said at least one entering request, said dynamic tier extension associates said at least one exiting request with said processing enclave, and wherein said dynamic tier extension associates between said at least one exiting request and said at least one entering request according to the association of said at least one entering request and said at least one exiting request with said processing enclave.

67. An application performance management method for operation in a multi-tier computing environment that includes a plurality of tiers, the method for monitoring a selected monitored tier of said plurality of tiers and comprising the steps of:

monitoring request traffic passing through said monitored tier, said monitored request traffic including at least one entering request and at least one respective exiting request, said selected tier providing said at least one respective exiting request to an adjacent tier;

determining context information relating to the request context of said at least one entering request;

identifying each request included in said monitored request traffic;

associating said at least one entering request with said at least one exiting request; and

sending context information relating to the request context of said at least one exiting request directly from a context agent associated with said monitored tier to another context agent associated with said adjacent tier.