...
There are a few sections in EventActions.json, but the one we're concerned with for forwarding events first is the policy section. Entries in a given section are numbered for determining the order in which they are processed. Usually we make forwarding the last entry (the entry with the highest number).
First we want to check all events and filter them in sub-sections. This just makes things easier for a human to read and understand. So our IF section at the first level is a simple node.any and event.any. For any node and any event. The THEN section is again numbered for order, that will then be processed.
Check All
|
Tag any up events
Next we need to decide which events we would like to send to the second instance. We're going to send (for the purposes of this example) all events with a node that has a serviceStatus of 'Production'. These events will go into a second list, inside the top level. Also, we should send all 'Node Up' or 'Closed' events to the second instance, regardless of the node so it cancels out any escalation. It dows not matter that no 'down' event might not have been sent previously. So our JSON will now look like the below.
|
Tag any Production node events
Now you may have noticed we have two items to action - escalateToMaster and sendToMaster. escalateToMaster sends an escalation where-as sendToMaster doesn't do anything other than simply send the event. No escalation required.
...
That's all we'll bother with to keep things simple.
Check tags
Next we need to check the tags and if required, escalate or send it to the second instance.
...