...
When an event is acknowledged, opEvents stops the propagation. That means, that all the rules are not going to run anymore. There are different approaches to achieve this, but is a common schema to set up opevents_auto_acknowledge_up to false in the poller, so the event is not acknowledge and can be sent to the primary.
More information: https://docs.community.opmantekfirstwave.com/wiki/pages/viewpage.action?pageId=27264053#EventActionsandEscalation3164406701#EventActionsandEscalation(opEvents3)-ActionPolicyApplicationandTiming
Reorder protection
Forwarded events may arrive out of order to the primary server, because of network congestion or slow action processing.
...
More information: Deduplication and storm control in opEvents#StatefulDeduplication,ForwardedEventsandReorderProtectionreorder_protection
Poller sending duplicate events to the primary
If your poller is sending duplicate events to the primary make sure that your EventActions.json script does not have any 'or' gates in your 'IF' statements - 'AND' and 'and' are fully supported, but 'or' (also 'OR') is not supported and can lead to unexpected behavior.
It's also best practice to use "BREAK" : "true" whenever possible, for example:
If we confirm that event.event = 'Node Down' there's no need to also check to see if event.event = 'Interface Down' etc.
Fast create remote event
We have recently rewritten create remote event in Go and have provided the option to use token auth skipping out one of the auth requests from the old Perl version.
...
| Code Block |
|---|
-d int
Log Level (default 4)
-p string
Password for the remote user
-path string
Path for generate auth token script (default "/usr/local/omk/bin/generate_auth_token.pl")
-q DontQuiet level, (1|true|0|false). Don't output anything (default true), -q=0 to see event id of remote system.
-retry int
Maximum number of retries
-s string
http://servername:portnumber/omk, API endpoint details are automatic. (default "http://localhost:8042/omk")
-t string
Token for auth
-u string
Username for remote server (default "nmis")
-v Verify the servers TLs connection (default true)
-version
Print out the version |
...
If your Opmantek Applications in a non standard location you can use -path to point to the full path of generate_auth_token.pl which is shiped in /usr/local/omk/bin/generate_auth_token.pl in future versions we aim to remove this.
Debug Values
to see debug set value to one i.e. -d 1, debug comes in as stdout (standard output)
Boolean Values
for the TLS verify command we support the following flags
...