Details

    • Help
    • Resolution: Fixed
    • Major
    • None
    • None
    • Default
    • None

    Description

      Hi, 
      I added an alert to check if there was a change in fdb count on any device
      I saw that there is an option called @previous, so i added the alert conditions below to match any of them, so if the fdb count increase or decrease i should get an alert
      I did some tests and it seem that its not working, i am not getting alerts.

      fdb_count gt @previous
      fdb_count lt @previous

      Attachments

        Activity

          [OBS-4781] FDB count alert
          Shama Tarek added a comment -

          Thanks Adam

          You can close the ticket for now.

          Shama Tarek added a comment - Thanks Adam You can close the ticket for now.

          Yeah, this is documented in the entity type reference in our documentation:

          https://docs.observium.org/entities/#metrics

          Note that the "device" entity only covers a handful of metrics that are directly available on the device record.

          Our alerting system is fairly unusual, and doesn't have access to most of the "device" level data that is collected because of how it works.

          adam.

          adama Adam Armstrong added a comment - Yeah, this is documented in the entity type reference in our documentation: https://docs.observium.org/entities/#metrics Note that the "device" entity only covers a handful of metrics that are directly available on the device record. Our alerting system is fairly unusual, and doesn't have access to most of the "device" level data that is collected because of how it works. adam.
          Shama Tarek added a comment -

          I see.

          Thanks for the clarification.

          Is there a page at your website for all the possible alerts? I didnt find such one when i was looking for details about the fdb_count alert.

          Shama Tarek added a comment - I see. Thanks for the clarification. Is there a page at your website for all the possible alerts? I didnt find such one when i was looking for details about the fdb_count alert.

          fdb_count isn't a metric, so you can't make an alert based on it

          an alert like this would likely be really noisy and sort of useless, since fdb counts change quite a lot on most devices

          also "metric != @previous" would be the same as the two checks here

          For this sort of thing you really need to find a nagios plugin that can do this as a probe.

          adama Adam Armstrong added a comment - fdb_count isn't a metric, so you can't make an alert based on it an alert like this would likely be really noisy and sort of useless, since fdb counts change quite a lot on most devices also "metric != @previous" would be the same as the two checks here For this sort of thing you really need to find a nagios plugin that can do this as a probe.
          Shama Tarek added a comment - - edited

          Thats how the alert looks like

          Is it correct or i am doing it wrong?

          I am using version 

          24.3.13376 (4th March 2024)
          Shama Tarek added a comment - - edited Thats how the alert looks like Is it correct or i am doing it wrong? I am using version  24.3.13376 (4th March 2024)

          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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -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

            landy Mike Stupalov
            Shama Tarek
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: