| Table of Contents |
|---|
opEvents Configuration
The configuration options for opEvents are stored in a json formatted text file: /usr/local/omk/conf/opCommon.json.
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.
| Section | Name | Original Value | Description |
|---|---|---|---|
| opevents | opevents_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. |
| opevents | opevents_url_base | http://yourserver.yourdomain | For creating links in emails |
| opevents | opevents_max_period_value | 90d | If N[dhm], any requests for longer periods are truncated |
| opevents | opeventsd_restart_on_config_change | false | Should the daemon restart if a config change is detected. |
| opevents | opevents_hostname | localhost | For the hostname in the syslog events |
Specific Configuration
The opEvents section of opCommon.nmis is for opEvents specific configuration items only.
...