The Event Expiration Times table defines how long persistent events will be stored in event history. Default duration is 10 days, after which events are permanently deleted from the history records. You can customize the duration of storage ("time-to-live") for different events.
The record format for the Event Expiration Times table:
Context Mask |
Every record in the table defines the storage time for an event in every context matching this mask. For example, if we specify custom expiration time of 1 month for the "login" event (in the Event column) and set the context mask to "users.admin" (matches the User context of the admin user), information about the logins of the system administrator will be stored for a period of one month. If Context Mask is set to "users.*", successful logins of all users will be stored for the same custom time period. |
Event |
Name of the event whose expiration time is re-defined. |
Expiration Period (hours) |
Duration of persistent storage. Note that in practice events may be available in event history a little bit longer than specified by this setting, because the cleanup process (removing expired events) runs every five minutes. |
When an event is stored in the history, LinkServer processes the Event Expiration Times table from the the first to the last record. If the context in which an event has occurred matches the mask defined by a record, the server uses the expiration time defined in this record to store the event and stops going over the list. I.e, the first match applies, even if masks in later lines also match the context. If this context doesn't match any mask defined in the table, default expiration time defined in the event definition will be used to store the event.
|
Example: Assuming we have the following table of custom expiration times:
According to this table, LinkServer will store logins of "admin" user for 1000 hours, logins of all other users will be stored for 200 hours. |
