opEvents Configuration

The configuration options for opEvents are stored in a text file /usr/local/omk/conf/opCommon.nmis.

Configuration items that are not application specific are detailed on the opCommon Configuration page.

Common Settings to Consider Adjusting

The items below are commonly changed by customers.

SectionNameOriginal ValueDescription
opeventsopevents_event_status_values{'status' => 'Detected'},{'status' => 'Investigating'},{'status' => 'Resolved'}

Values which the operator can select. If enabled or the event has the status property, a select box will be rendered in the event context panel.

To configure to work for your team, decide on what fields you want to include in your status.

opeventsopevents_url_basehttp://yourserver.yourdomainFor creating links in emails
opeventsopevents_max_period_value90dIf N[dhm], any requests for longer periods are truncated
opeventsopeventsd_restart_on_config_changefalseShould the daemon restart if a config change is detected.
opeventsopevents_hostnamelocalhostFor the hostname in the syslog events

Specific Configuration

The opEvents section of opCommon.nmis is for opEvents specific configuration items only.

SectionNameOriginal Value
Possible ValuesDescription
opeventsblack_list_enabledtrue
true, false
opeventslog_archive_enabledtrue
true, false
opeventsnmis_non_stateful_eventsNode Configuration Change|Node Reset


opeventsopevents_action_max_runtime30
<integer>how long an asynchronous policy action process may run
opeventsopevents_action_policy<omk_conf>/EventActions.nmis
<relative filepath>
opeventsopevents_application_heading



opeventsopevents_archivelogs_purge_older_than365d

archive logs (format NN[dhm]..., plain N means N minutes. 0 or undef means no purging).
opeventsopevents_auto_acknowledgetrue
true, falseauto-acknowledge the down event on state down->up or not?
opeventsopevents_auto_acknowledge_uptrue
true, falseif opevents_auto_acknowledge is on, also acknowledge the up event?
opeventsopevents_auto_create_nodestrue
true, false
opeventsopevents_contacts<omk_conf>/Contacts.nmis


opeventsopevents_correlation_nodeglobal


opeventsopevents_daily_report_recipients



opeventsopevents_daily_report_titleDaily Summary Report


opeventsopevents_debug0
<integer>
opeventsopevents_emails<omk_conf>/EventEmails.nmis
<relative filepath>
opeventsopevents_event_rules<omk_conf>/EventRules.nmis
<relative filepath>
opeventsopevents_event_status_default_value



opeventsopevents_event_status_enabledfalse
true, false
opeventsopevents_event_status_values{'status' => 'Detected'},{'status' => 'Investigating'},{'status' => 'Resolved'}

An array
opeventsopevents_events_purge_older_than180d

events and actions (format NN[dhm]..., plain N means N minutes. 0 or undef means no purging).
opeventsopevents_flap_nameevent.stateful Flap

node.X, event.Y and macro.Z are substituted
opeventsopevents_gui_console_default_period2h


opeventsopevents_gui_console_pagination[10,10]

Separate for top and bottom panels
opeventsopevents_gui_current_events_priorities[3,10]
3, 4, 5, 6, 7, 8, 9, 10Only priorities 3..10 are included in current events view
opeventsopevents_gui_dashboard_default_period2h


opeventsopevents_gui_dashboard_pagination10
<integer>Default records per page for dashboard, event list and event console pages
opeventsopevents_gui_default_period2h

Default period for the gui screens: general and node/event context pages
opeventsopevents_gui_event_context_period2h

How much time before/after an event to consider for context
opeventsopevents_gui_event_context_summary_list



opeventsopevents_gui_event_node_summary_list["name","group","location","customer","businessService","host"]

Default list for opevents' mail template use, also gui for event-related node context
opeventsopevents_gui_events_coloringtrue
true, falseColor events by severity
opeventsopevents_gui_events_pagination25
<integer>
opeventsopevents_gui_node_summary_list["name","group","location","customer","businessService","host"]

Default property list for opevents' gui, for node context
opeventsopevents_gui_period_values['15m','30m','1h','90m','2h','4h','8h','12h','1d', '2d', '15d', '30d', '60d', '90d' ]


opeventsopevents_hostnamelocalhost
<hostname>For the hostname in the syslog events
opeventsopevents_import_node_interfacestrue
true, false
opeventsopevents_import_nodes_activatedtrue
true, false
opeventsopevents_kb_link_titleKB Lookup


opeventsopevents_kb_link_urlhttps://community.opmantek.com/x/%s
<url>
opeventsopevents_list_rules<omk_conf>/EventListRules.nmis
<relative filepath>
opeventsopevents_logs


See Documentation
opeventsopevents_max_action_queue_age3600
<integer>Abort action processing if action queued longer than N seconds (set tp zero to disable).
opeventsopevents_max_event_age7200
<integer>Ignore input events older than N seconds (set tp zero to disable).
opeventsopevents_max_period_value90d

If N[dhm], any requests for longer periods are truncated
opeventsopevents_max_time_delta0
<integer>
opeventsopevents_monthly_report_recipients



opeventsopevents_monthly_report_titleMonthly Summary Report


opeventsopevents_move_json_logs<nmis_logs>/json/historic

If set, move consumed json log files into this directory, if unset, remove consumed json log files
opeventsopevents_nmis_rules<omk_conf>/EventNmisRules.nmis
<relative filepath>
opeventsopevents_no_action_on_flaptrue
true, falseskip actions on flap detected?
opeventsopevents_parser_rules<omk_conf>/EventParserRules.nmis
<relative filepath>Generic parsers can be defined in this file
opeventsopevents_plugin_max_runtime5
<integer>Parser plugins may run that long
opeventsopevents_rawlogs_purge_older_than90d

raw logs (format NN[dhm]..., plain N means N minutes. 0 or undef means no purging).
opeventsopevents_refresh_time120


opeventsopevents_report_mininterval900

granularity for interval reporting
opeventsopevents_reports_purge_older_than730d

summary reports (format NN[dhm]..., plain N means N minutes. 0 or undef means no purging).
opeventsopevents_reschedule_action_age180
<integer>Reschedule action after X seconds if worker died
opeventsopevents_search_link_title



opeventsopevents_search_link_urlhttps://duckduckgo.com/html/?q=%s
<url>
opeventsopevents_standard_path/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
<filepath>If you want opeventsd to use a specific path for itself and the programs that it runs in event actions, set it here
opeventsopevents_syslog_rules<omk_conf>/EventSyslogRules.nmis
<relative filepath>
opeventsopevents_tivoli_rules<omk_conf>/EventTivoliRules.nmis
<relative filepath>
opeventsopevents_trap_rules<omk_conf>/EventTrapRules.nmis
<relative filepath>
opeventsopevents_url_basehttp://yourserver.yourdomain
<url>For creating links in emails
opeventsopevents_warn_overdue_actions100
<integer>Warn if there are more than N overdue queued actions (set tp zero to disable).
opeventsopevents_warn_overdue_events100
<integer>Warn if there are more than N queued events that are overdue for processing (set tp zero to disable).
opeventsopevents_weekly_report_recipients



opeventsopevents_weekly_report_titleWeekly Summary Report


opeventsopeventsd<omk_base>/bin/opeventsd.pl
<relative filepath>
opeventsopeventsd_cache<omk_var>/opeventsd.nmis
<relative filepath>
opeventsopeventsd_file_cycle4
<integer>wake up every N seconds, check for files
opeventsopeventsd_max_cycles

<integer>if set, then the opeventsd worker restarts after that many update cycles
opeventsopeventsd_max_processes10
<integer>how many workers to run at most, at any time
opeventsopeventsd_pid/var/run/opeventsd.pid
<filepath>
opeventsopeventsd_queue_cycle3
<integer>wake up every N seconds, check for queued events
opeventsopeventsd_restart_on_config_changefalse
true, false
opeventsraw_log_black_listtrue
true, false
opeventsraw_log_enabledtrue
true, false
opeventsstate_flap_window90
<integer>
opeventsstate_reorder_window0
<integer>If set to positive N, external events may be delayed for up to N seconds for reordering
opeventswhite_list_enabledfalse
true, false