Page Comparison

...

Setup and Configure opEvents (Initial)

Consolidate your Browser Cookies

NMIS9 and opEvents by default 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.

Configure NMIS9:

1. Open /usr/local/nmis9/conf/Config.nmis
2. Locate the 'auth_cookie_flavor' setting under 'authentication' and ensure it is set to 'omk'
3. Locate the 'auth_web_key' setting under 'authentication', this should be set to a long, random string. Make sure you COPY this as you will need it later.
4. Save and close the file.
5. If you needed to change either of these settings make sure you restart the nmis9d daemon

Configure opEvents4:

1. Open /usr/local/omk/conf/opCommon.json
2. Locate the "omkd_secrets" setting, change this to match the setting you copied from 'auth_web_key' earlier.
3. Save and close the file.
4. If you changed this setting make sure to restart the omkd daemon

Adjust Node Summary Field List

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.

Adjust NMIS to use JSON events

Add/Edit EscalationsIf 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.

• opCharts Node Dependency Management (Root Cause Analysis)
• Leveraging NMIS Dependency in opEvents

Add/Edit Correlation Rules

Add/Edit Event Actions

Monitor opEvents for Proper Event Handling

...