Open for Voting
over 2 years ago

Extract of Log / Trap Messages (VarBinds) to Trigger Orion Alerts

We need to be able to extract VarBinds from traps and alert on them (or regex patterns in syslogs).

For Example, BGP Peer down OID 1.1.1.1.1.1.1

Peer address is in varbind 1.1.1.1.1.2.1

Local address is in varbind 1.1.1.1.1.2.2

The problem is that you cannot have 2 instances/alerts of the same Log Anayser rule hit. So if "RouterA" has Peer1 go down, it triggers this. 

5 hours later if "RouterA" has "Peer2" go down, it triggers this again (with a different VarBind). Same LA rule, Same Orion Alert, so nothing re-triggers as Orion thinks its already active. 

Similarly, Orion can only display the ENTIRE trap message using the $(loganalyster.Macro). Thats no good, as we get 5 lines of garbage when all I want to view is the single varbind thats important to me - the peer address. 

Until Varbinds can be individually alerted on, and extracted into the orion message, the Alerting functionality of LA is useless for us. 

Parents Comment Children
  • half of your request is now possible with 2020.2.5+. You can extract the varbinds so that you can construct an alert message from the varbinds. unfortunately the other half - where you want unique instances of alerts hit by the same condition but with different varbinds - ie nodename, or interface is not possible - so its still useless as from an incident management perspective 

  • I'm able to construct and alert off of specific varbinds but I can't get the information in the varbind into the actual text of the alert.  Are you able to do that?