When configuring alerts in a Distributed Monitoring configuration. I'm having some problems when alerting from a location the trigger did not originate from.
When I alert from an ACTION on the child node where the trigger is generated all the macros get expanded correctly.
However when I alert from an ACTION on an upstream node all of the macros come back as *UNKNOWN*.
Perhaps this functionality was never intended to work, but I would like to generate alert actions off of the triggers from a child node on an upstream node. Currently I'm getting bad results.
Email from child node (expected results):
Email from upstream node (macros not expanded):
Both of these emails are generated by the same trigger, just the actions are configured on different nodes. The child node expands the macros and provides the expected information. The parent node returns the *UNKNOWN* values.
Any insight into the problem would be very helpful.
When I alert from an ACTION on the child node where the trigger is generated all the macros get expanded correctly.
However when I alert from an ACTION on an upstream node all of the macros come back as *UNKNOWN*.
Perhaps this functionality was never intended to work, but I would like to generate alert actions off of the triggers from a child node on an upstream node. Currently I'm getting bad results.
Email from child node (expected results):
HTML Code:
Trigger: Free disk space is less than 20% on volume C: on test1.host Trigger status: PROBLEM Trigger severity: Warning Trigger URL: Item values: 1. Free disk space on C: (percentage) (test1.host:vfs.fs.size[C:,pfree]): 10.63 % 2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* Original event ID: 200000000003358
HTML Code:
Trigger: Free disk space is less than 20% on volume C: on *UNKNOWN* Trigger status: PROBLEM Trigger severity: Warning Trigger URL: Item values: 1. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* 3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN* Original event ID: 200000000003358
Any insight into the problem would be very helpful.
Comment