Details

    • New Feature
    • Resolution: Unresolved
    • Minor
    • None
    • Professional Edition
    • Web Interface

    Description

      Is it possible to implement "Entity Filtering" in Alert Checker configuration?

      I try to explain the needs with an example, but scenarios may be also applied in other situations.

      We set up an alert which checks Interface Usage on a 48-port Cisco Switch. Since it's not possible to specify single ports (we need to check usage only for 4-5 ports, instead of 24 total), we inserted "*" in Entity Match section.

      What happens is that during night-time, backup process saturates one of the ports connected to backup device and a "fake" alert is generated.

      A couple of solutions could be:

      • possibility to specify more than an entity (for example only GigabitEthernet1/1 and GigabitEthernet1/2 ports)
      • possibility to exclude (one or more) specific port in checks.

      Otherwise we have to setup specific alert for specific port: it means lots of alert checkers, that may become hard to keep updated.

      Regards,
      Arrigo.

      Attachments

        Activity

          [OBS-2086] Alert Checker entity filtering

          So it's not possible filter in "entity" section?
          Your suggestions refer to "Device Match" section, correct?

          arryxyz Arrigo Savio added a comment - So it's not possible filter in "entity" section? Your suggestions refer to "Device Match" section, correct?

          This is easily done by using negative matching rules in the associations.

          os match linux
          hostname notmatch derp
          hostname match *.blah.com

          Would match the linux server foo.blah.com but not derp.blah.com

          Your scenario would be done by putting something like "ignore" or "backup" in the port description and ignoring these ports like "port_label notmatch backup"

          adama Adam Armstrong added a comment - This is easily done by using negative matching rules in the associations. os match linux hostname notmatch derp hostname match *.blah.com Would match the linux server foo.blah.com but not derp.blah.com Your scenario would be done by putting something like "ignore" or "backup" in the port description and ignoring these ports like "port_label notmatch backup "

          People

            adama Adam Armstrong
            arryxyz Arrigo Savio
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: