opConfig 4 is the NMIS 9 compatible version. In this guide, you will learn all you need to start using opEvents.
We recommend you:
Download the latest product version from opmantek.com.
opEvents is distributed in a self-extracting download format that simplifies the installation process quite a bit. More information on running the installer can be found HERE: The Opmantek Installer
Transfer the opEvents installer file onto the server in question, either by direct download from the Opmantek website, or from your desktop with scp
or sftp
or a similar file transfer tool.
Start the interactive installer and follow its instructions:
|
/usr/local/omk
, and the default configuration files are in /usr/local/omk/conf
, ready for your initial config adjustments./usr/local/omk/install.log
, and subsequent upgrades or installations of other Opmantek products will add to that logfile.If necessary the installer will offer to install MongoDB locally for you; if that is undesirable, or if you have a remote MongoDB installation that you want to use you'll need to adjust the MongoDB-related settings:
open conf/opCommon.nmis
in an editor, go to the database section and change the server, username and password to reflect your MongoDB installation.
The result should look similar to the following (but there might be extra settings related to other products):
|
Access the opEvents GUI and acquire, restore or enter your license.
The opEvents GUI is accessible at http://<yourservername or ip address>/omk/opEvents/
, and until you have entered a valid license neither the opEvents GUI nor the CLI tools will operate.
At this point opEvents should be ready for operation.
Your next step should be to consult the opEvents Basic Concepts:
priority
event property.Please feel free to leave comments and suggestions below!
opEvents can produce a lot of data and it is important to have a purging policy. For this, we can set up a cron job, as an example:
# purge the database once weekly 12 3 * * 5 root /usr/local/omk/bin/opevents-cli.pl act=purge |
opEvents will only cleanup the data types that have a purging policy. For this, you can update omk/conf/opCommon.nmis:
'opevents_events_purge_older_than' => 43200, # Minutes!! Will cleanup events older than 30 days. #'opevents_rawlogs_purge_older_than' => 43200, #'opevents_archivelogs_purge_older_than' => 43200, #'opevents_reports_purge_older_than' => 43200, |
As an output example:
omk$ ./bin/opevents-cli.pl act=purge debug=9 Purging disabled for rawlogs Purging disabled for archivelogs Db purge of events: 646 entries (of 1872749) in events are older than 30d Purged events: removed 646 records from events Db purge of events: 322 entries (of 1185634) in actionlog are older than 30d Purged events: removed 322 records from actionlog Purging disabled for reports |
Starting from version 3.2.0, we have made significant changes on our internal shared code for all our applications to work on Opmantek's latest and fastest platform, however, previously installed product are not compatible with this version.
To find out more about this upgrade please read: