362CHAPTER 8: THE EVENT LOG

The process is controlled by two configurable parameters:

The maximum number of days to keep events for.

The maximum number of events to keep.

When the ageing process runs it uses these parameters to determine what events to permanently remove from the events database using the following rules:

Firstly, any events older than the configured maximum number of days are removed.

Secondly, if the number of events in the events database exceeds the configured maximum number of events then events marked for deletion are removed, oldest first. This process continues until either the number of events in the database equals the configured maximum number of events or all of the events marked for deletion have been removed, whichever comes first.

Third and finally, if the number of events in the events database still exceeds the configured maximum number of events then resolved events are removed, oldest first. Similarly, this process continues until either the number of events in the database equals the configured maximum number of events or all of the resolved events have been removed, whichever comes first.

The ageing process will never remove an unresolved event from the events database unless it has been marked for deletion. As a result you may find that after the ageing process has completed there are unresolved events in the database older than the configured maximum number of days.

Similarly, you may find that after the ageing process has completed the number of events in the database still exceeds the configured maximum number. This will occur if you have more unresolved events in the database that are not marked for deletion than the configured maximum number.

The ageing process normally runs once every 24 hours, at midnight.

As the process does not normally run during the day this means that you may see the configured limits being temporarily exceeded.

Page 366
Image 366
HP Network Direr Software Products manual Event LOG