In addition to the alert, device and monitor specific variables, when overriding incoming alert text you are able to use values from the alert details. This is especially useful when dealing with incoming SNMP traps, as the software has no automatic way of knowing which object in the trap payload represents the error message.
Below is an example of an SNMP trap:
The trap payload is shown in the details section under 'PDU'. The payload contains a list of objects and a corresponding value. Any one of the PDU values can be used in the alert text, by using the object name as a substitution variable. So for this trap we could use the 'halEsAlertText' object, as below:
When the trap is received, the substitution variable engine scans the payload looking for an object with the same names as the variable, and inserts it into the alert text. Therefore, when the alert is viewed in the Enterprise Console, the specific error message for that particular trap is used instead of the default text as before:
MIB's (Management Information Base) can be loaded and if an incoming alert finds a matching MIB that maps SNMP OID’s to object names. If a MIB is not available for a trap you’re receiving you can still use substitution variables to override the incoming alert text by defining the OID as the variable as shown in the rule below:
Still have questions? We can help. Submit a case to Technical Support.