Events Maintenance - On Premise
In Privilege Manager versions prior to 10.6, all events are stored unless manually purged. Event storage uses database space and can impact performance of dashboard queries so it is sometimes desirable to purge the stored events.
Privilege Manager version 10.6 and up, includes an option to specify the maximum number of events to be stored (rather than let the system continue to add events to be stored until manually purged).
In the Cloud version of Privilege Manager, the Maximum Event Count cannot be changed by the user; it is fixed at its default value. Refer to Event Limits - Cloud.
Manually Purge Events
-
Navigate to Admin | Configuration and select the General tab
-
In the Maintenance Settings section of this page, click on Purge Maintenance - Application Control Events.
The Description text explains what this feature does: "Purges the selected Application Control Event types from the database based upon the time range specified".
-
Under Parameters, set the switches and edit values based on how you want the maintenance to be performed for your instance.
-
Click Save Changes.
Maximum Event Count: Basics
- Navigate to Admin | Configuration and select the Advanced tab.
The "Privilege Manager Server" section of the page shows the option "Maximum Application Event Count" and its default value, which is 1,000,000.
You can change the value, but storing a large number of events could cause database issues and slow down dashboard queries. Save your changes, if you edit the number.
Maximum Event Count: Additional Information
The points below provide additional information about the Maximum Event Count:
- The count value is a total for all policies; it is not a per policy setting.
- The count is treated as a rolling window; if a new event would cause the count to exceed the maximum limit, the oldest event is removed.
- The manual purge, as described in a previous section, is still available.
- In the Cloud version of Privilege Manager, the Maximum Event Count cannot be changed by the user; it is fixed at its default value. Refer to Event Limits - Cloud.