...
Your desired purging policy is defined by setting one or more of the following four configuration properties in conf/opCommon.nmis (or opCommon.json in opEvents 3.0+4.x and newer). Here is the commented example from install/opCommon.nmis(json):
| Code Block |
|---|
'"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'" =>: "730d", # covers summary reports '"opevents_events_purge_older_than' => 180d": "180d", # covers events and actions '"opevents_rawlogs_purge_older_than'" =>: "90d", # covers raw logs '"opevents_archivelogs_purge_older_than'" =>: "365d", # covers archive logs |
The configuration is pretty straightforward:
...
The expiration of old data is performed by opeventsdopevents-cli.pl if and when it is started with the argument act=purge. You can also instruct it to only tell you how many entries a purge run would remove (without removing anything) by giving the arguments act=purge simulate=true.
...
| Code Block |
|---|
# this cron schedule controls opEvents db purging and reporting # # m h dom month dow user command # # purge the database once weekly 12 3 * * 51 root /usr/local/opmojoomk/bin/opevents-cli.plexe act=purge # create daily summary reports 021 93 * * * root /usr/local/opmojo/bin/opevents-cli.pl act=create-report daily=true 0 15 * * * root /usr/local/opmojoomk/bin/opevents-cli.plexe act=create-report daily=true # create weekly summary reports 32 3 * * 1 root /usr/local/opmojoomk/bin/opevents-cli.plexe act=create-report weekly=true # create monthly summary reports 43 4 1 * * root /usr/local/opmojoomk/bin/opevents-cli.plexe act=create-report monthly=true |
...