Proactive Performance Management for Multi-User Enterprise Software Systems

• US 20130007267A1
• Filed: 06/28/2012
• Published: 01/03/2013
• Est. Priority Date: 03/02/2007
• Status: Active Grant

• Current Assignee: Pegasystems Incorporated
• Original Assignee: Pegasystems Incorporated
• Inventors: Khatutsky, Victor E.
• Granted Patent: US 9,189,361 B2
• Time in Patent Office: Days
• US Class Current: 709/224
• CPC Class Codes: G06F 11/3409 for performance assessment
• CPC Class Codes: G06F 11/3438 monitoring of user actions tracking the activity of the user H04L67/535
• CPC Class Codes: G06F 11/3442 for planning or managing the needed capacity
• CPC Class Codes: G06F 11/3447 Performance evaluation by modeling
• CPC Class Codes: G06F 2201/81 Threshold
• CPC Class Codes: G06F 2201/86 Event-based monitoring

Abstract

The invention provides, in some aspects, systems for proactive management of development and performance of a software application based on monitoring it (and/or one or more of its components) during the course of development or execution. Those systems signal alerts upon determining that actual or expected usage of the application (or its components) by users of like classes (or roles) is anticipated to, or does, exceed quotas, when the application is placed in production mode.

Claims

1-25. -25. (canceled)

26. A system for proactive management of performance of an application, comprising:

A. a digital data processor executing a performance monitor in communications coupling with one or more resources, the performance monitor monitoring any of (i) usage of the application and/or one or more components thereof by a user, and (ii) consumption of the one or more resources during usage of the application and/or one or more components thereof by the user, and

B. the performance monitor signaling an alert upon determining that such usage by the user and/or consumption of resources during such usage violates a model, wherein the model defines one or more quotas for the user with respect to usage of a component of the application by the user.

27. The system of claim 26, wherein the performance monitor limits usage and/or consumption of resources.

28. The system of claim 26, wherein the performance monitor limits usage and/or consumption of resources by preventing additional users from executing the application.

29. The system of claim 26, wherein the performance monitor limits usage and/or consumption of resources by terminating a process of the user.

30. The system of claim 26, wherein the model further defines the one or more quotas in accord with a class to which the user belongs.

31. The system of claim 30, wherein the quotas include any of (i) maximum permitted usage of the application by users in each of one or more classes, and (ii) expected usage of the application by users in each of one or more classes.

32. The system of claim 30, wherein the model defines such quotas on the basis of individual and multiple users in such classes.

33. The system of claim 26, wherein the performance monitor signals the alert to a centralized monitoring environment.

34. The system of claim 26, in which the model is defined based on a performance history of the application.

35. The system of claim 26, wherein the resources include any of processing capacity, memory capacity and/or network bandwidth.

36. A method for proactive management of performance of an application, comprising:

A. monitoring, by a digital data processor, any of (i) usage of the application and/or one or more components thereof by a user, and (ii) consumption of the one or more resources during usage of the application and/or one or more components thereof by the user, and

B. signaling an alert upon determining that such usage by the user and/or consumption of resources during such usage violates a model, wherein the model defines one or more quotas for the user with respect to usage of a component of the application by the user.

37. The method of claim 36, further comprising limiting usage and/or consumption of resources.

38. The method of claim 36, further comprising limiting usage and/or consumption of resources by preventing additional users from executing the application.

39. The method of claim 36, further comprising limiting usage and/or consumption of resources by terminating a process of the user.

40. The method of claim 36, wherein the model further defines the one or more quotas in accord with a class to which the user belongs.

41. The method of claim 40, wherein the quotas include any of (i) maximum permitted usage of the application by users in each of one or more classes, and (ii) expected usage of the application by users in each of one or more classes.

42. The method of claim 40, wherein the model defines such quotas on the basis of individual and multiple users in such classes.

43. The method of claim 36, the alert is signaled to a centralized monitoring environment.

44. The method of claim 36, in which the model is defined based on a performance history of the application.

45. The method of claim 36, wherein the resources include any of processing capacity, memory capacity and/or network bandwidth.