...
This Solution Guide will provide a detailed, single reference for configuring opEvents for use in a production environment.
Related Pages
Additional related pages will be linked throughout this Solution Guide.
Scenario
The administrator Opmantek Administrator is deploying opEvents 4.x in a production environment and desires to enable as much functionality as possible, beyond the default settings provided by the installer.
...
This Solution Guide assumes the installation, setup and configuration of NMIS9.x and opEvents 4.x on a single-server. Additional Solution Guides are available for multitiered multi-tiered deployments using opHA.
Install/Update opEvents
Add opEvents License Key
Accept EULA
System Resources and Install
...
Consolidate your Browser Cookies
NMIS9 and opEvents by default opEvents4 use separate browser cookies to maintain your login information. This means that if you log into NMIS, you would need to login again to opEvents. You can, however configure both products to share the same browser cookie.
...
- Open /usr/local/omk/conf/opCommon.json
- Locate the "omkd_secrets" setting, change this to match the setting you copied from 'auth_web_key' earlier.
- Save and close the file.
- If you changed this setting make sure to restart the omkd daemon
...
NMIS9 shares a limited number of device fields with opEvents by default. These are defined in the 'node_summary_field_list' in the NMIS9 configuration file. You should review this setting in /usr/local/nmis9/conf/Config.nmis as you may want to append this list to include additional fields you may want to make available to opEvents for event handling or decision making.
...
Configure opEvents for Device Dependency Mapping
If you have opCharts installed with NMIS9 and opEvents4 you should configure opCharts for automated dependency mapping, AND configure opEvents to process events from a JSON stream. The following links detail how to configure each option.
...