Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4150

Meta-conditions for alert checkers

Details

    • New Feature
    • Resolution: Unresolved
    • Major
    • None
    • Professional Edition
    • Alerting

    Description

      Hi Team,

      We'd like to be able to create a kind of "meta" alert checker that combines the results of the "alert condition" checks across all associated entities within the alert checker before triggering an alert to fire. 

      The use case for this is for multi-chassis bundles and pseudowire head-end, where a single "service" that we care about could have a variety of different paths or termination points in the network, but we only want to alert if some combination of entities is down. 

      For example, given the following alert checker with these two entities (ports) associated:

      We'd like to not have each individual entity alert separately, but only alert if the combination of both entities is down at the same time.

      Let me know if you want further details and whether you think this is viable for implementation or not.

      Best regards,

      Matt Clancy

      Attachments

        Activity

          [OBS-4150] Meta-conditions for alert checkers
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            adama Adam Armstrong
            mcslc Matthew Clancy
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: