Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Available in opEvents-3.2.2 and opEvents-2.6.1


Image RemovedImage Added


opEvents programmable buttons allow scripts to be run against events to give operators  greater flexibility in the use of opEvents in troubleshooting and triaging of events.

...

Configuration

Create a file in omk/conf/table_schemas/opEvents_action-buttons.json

This must be valid JSON schema or the buttons will fail to render. You should see an error in opEvents.log if this is the case.

Code Block
languagejsbash
[
  {
    "description": "Example Events Button Action",
    "label": "Ping Node",
    "fa_icon": "fas fa-table-tennis",
    "script": "ping_node",
    "tags": ["ping"]
  }
]


Add a policy in omk/conf/EventActions.json|.nmis that triggers show_button.tag()

Code Block
languagebash
titleEventActions.json
"policy": {
	"5": {
		"IF": "event.any",
		"THEN": "show_button.ping()",
		"BREAK": "true"
		},
	}


Code Block
languagebash
titleEventActions.nmis
%hash = (
		'policy' => {
				'5' => {
						IF => 'event.any',
						THEN => 'show_button.ping()',
						BREAK => 'true'
					},
				}
		);


These are the supported keys and how the change operation and look of the button.

...

In opEvents-3.2.2 we are shipping the library 5.12.1

In opEvents-2.6.1 we are sipping shipping the library 5.8.2