Version 2.0.0 (and newer) of opEvents provides a new mechanism for expiring old data from the database. The purging is totally optional and no old data will be removed unless you explicitely configure opEvents to do so.
opEvents can expire four different types of old data independently:
Your desired purging policy is defined by setting one or more of the following four configuration properties in conf/opCommon.nmis
. Here is the commented example from install/opCommon.nmis
:
'opevents' => { # lots of other directives... # how long should things be kept in the db? format NN[dhm]MM[hm]..., plain N means N minutes. 0 or undef means no purging. 'opevents_reports_purge_older_than' => undef, # covers summary reports 'opevents_events_purge_older_than' => undef, # covers events and actions 'opevents_rawlogs_purge_older_than' => undef, # covers raw logs 'opevents_archivelogs_purge_older_than' => undef, # covers archive logs |
The configuration is pretty straightforward:
undef
means no purging whatsoever.31d12h
means "purge data older than 31 days and 12 hours" (as does 12h31d
).