...
Find the email section in opCommon.nmis and updated the values to match the email server that opEvents should utilise.
Configure a Contact
A 'contact' in variable that can represent one or many email addresses. opEvents can utilize the NMIS contacts file or the OMK contacts file. In order to determine which file your system is using look in opCommon.nmis; find the opevents section then look for the opevents_contacts attribute.
| Code Block | ||
|---|---|---|
| ||
'opevents' => {
'black_list_enabled' => 'true',
'log_archive_enabled' => 'true',
'nmis_non_stateful_events' => 'Node Configuration Change|Node Reset',
'opevents_action_max_runtime' => 30,
'opevents_action_policy' => '<omk_conf>/EventActions.nmis',
'opevents_application_heading' => undef,
'opevents_archivelogs_purge_older_than' => undef,
'opevents_auto_acknowledge' => 'true',
'opevents_auto_acknowledge_up' => 'true',
'opevents_auto_create_nodes' => 'true',
'opevents_contacts' => '<omk_conf>/Contacts.nmis', |
In the example above the OMK contacts file is being used.
Create an Escalation Policy
...