Systems and methods for managing event messages

• US 9,349,114 B2
• Filed: 10/31/2006
• Issued: 05/24/2016
• Est. Priority Date: 10/31/2006
• Status: Active Grant

• Current Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Original Assignee: Hewlett Packard Enterprise Development LP (Hewlett-Packard Enterprise Company)
• Inventors: Cowham, Adrian
• Primary Examiner(s): Hussain, Imad
• Application Number:
  US11/591,411
• Publication Number:
  US 20080104229A1
• Time in Patent Office: 3,493 Days
• Field of Search: 370/230, 370/412, 370/449, 370/241, 370/252, 706/16, 709/203, 709/223, 709/224, 709/226, 709/231, 455/566, 718/105, 705/1, 705/35, 707/102
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 10/10 Office automation; Time management
• CPC Class Codes: H04L 41/0604 using filtering, e.g. reduction of information by using priority, element types, position or time

Abstract

In one embodiment a method for managing event messages includes predicting an event message arrival rate, determining a current capacity of an event message repository in which received event messages are stored, and calculating a time at which to perform event message deletion relative to the predicted event message arrival rate and the determined current capacity of the event message repository.

Claims

1. A method for managing event messages, the method comprising:

predicting, by a processing device of a computer, an event message arrival rate;

determining, by the processing device, a maximum number of event messages permissible to be stored in a repository and a current number of event messages presently stored in the repository; and

calculating, by the processing device, a time at which to delete event messages from the repository based upon a difference between the maximum number of event messages and the current number of event messages relative to the predicted event message arrival rate.

2. The method of claim 1, wherein predicting an event message arrival rate comprises determining a previous message arrival rate from historical data pertaining to previous arrivals of event messages.

3. The method of claim 2, wherein predicting an event message arrival rate further comprises determining a number of event messages that arrived over a given period of time.

4. The method of claim 2, wherein predicting an event message arrival rate further comprises determining an amount of data that was stored in the event message repository over a given period of time.

5. The method of claim 1, wherein predicting an event message arrival rate comprises computing multiple event message arrival rates for discrete periods of time.

6. The method of claim 5, wherein computing multiple event message arrival rates comprises computing separate event message arrival rates for different days of the week.

7. The method of claim 5, wherein computing multiple event message arrival rates comprises computing separate event message arrival rates for different times of day.

8. The method of claim 1, wherein determining the current number of event messages comprises determining an amount of data currently stored in the repository.

9. The method of claim 1, further comprising deleting event messages from the repository at the calculated time.

10. The method of claim 9, further comprising determining a new capacity of the repository after event messages were deleted and recalculating the time at which to delete event messages based upon the predicted event message arrival rate and the new capacity.

11. A non-transitory computer-readable medium that stores instructions that when executed by a processor cause the processor to:

predict a future event message arrival rate;

determine a maximum number of event messages that a repository has stored and a current number of event messages presently stored in the repository; and

calculate a time at which to delete event messages from the repository based upon a difference between the maximum number of event messages and the current number of event messages relative to the predicted event message arrival rate.

12. The non-transitory computer-readable medium of claim 11, wherein to predict an event message arrival rate, the instructions are to cause the processor to determine a previous message arrival rate from historical data pertaining to previous arrival of event messages.

13. The non-transitory computer-readable medium of claim 12, wherein to predict an event message arrival rate, the instructions are to cause the processor to determine a number of event messages that arrived over a given period of time.

14. The non-transitory computer-readable medium of claim 12, wherein to predict an event message arrival rate, the instructions are to cause the processor to determine an amount of data that was stored in the event message repository over a given period of time.

15. The non-transitory computer-readable medium of claim 11, wherein to predict an event message arrival rate, the instructions are to cause the processor to calculate multiple event message arrival rates for discrete periods of time.

16. The non-transitory computer-readable medium of claim 11, wherein the instructions are further to cause the processor to determine an amount of data currently stored in the event message repository.

17. The non-transitory computer-readable medium of claim 11, wherein the instructions are further to cause the processor to delete event messages from the repository at the calculated time.

18. A computer comprising:

a processing device; and

memory including a program to cause the processing device to

predict an event message arrival rate based upon historical data concerning past arrival of event messages,

determine a maximum number of event messages permissible to be stored in a repository and a current number of event messages presently stored in the repository,

calculate a time at which to perform event message deletion based upon a difference between the maximum number of event messages and the current number of event messages relative to the predicted event message arrival rate,

delete event messages from the repository at the calculated time.

19. The computer of claim 18, wherein, to predict the event message arrival rate, the program is to cause the processing device to determine a number of event messages that arrived over a given period of time.

20. The computer of claim 18, wherein, to predict the event message arrival rate, the program is to cause the processing device to determine an amount of data that was stored in the event message repository over a given period of time.

21. The computer of claim 18, wherein the program is to cause the processing device to calculate multiple event message arrival rates for discrete periods of time.