From RIPv2_van_Winkle, 3 Months ago, written in HTML5.
This paste is a reply to Multiple BGP Peers, single alert rule from RIPv2_van_Winkle - view diff
Embed
  1. Hello. We are seemigly unable to evaluate multiple BGP peers in the same singular alert rule:
  2.  
  3. Here is the SQL format of the alert rule. I'm including screenshots as we
  4. Hello. We are seemigly unable to evaluate multiple BGP peers in the same singular alert rule:
  5.  
  6. Here is the SQL format of the alert rule. I'm including screenshots as well.
  7.  
  8. This works fine:
  9. ![image|690x358](upload://ok8GmLgtBw6YEm0KjfxrXWODE8D.png)
  10.  
  11. This also works fine:
  12. ![image|690x353](upload://daYz4xbYii1IXe87XZOTz1NKvdb.png)
  13.  
  14. But this does not work:
  15. ![image|497x466](upload://l1slXpagRva4R3GOVRmiR9bYLtN.png)
  16.  
  17. Perhaps this is by design, something that we are not understanding. But at this point we've exhausted every permutation of the rule, including creating Custom SQL queries that work properly when tested against the database itself, but fail when copied into the alert engine as SQL overrides.
  18. ll.