Details

    • Bug
    • Resolution: Not A Bug
    • Minor
    • None
    • Professional Edition
    • Alerting

    Description

      Observium 18.8.9361 (3rd August 2018)
      OS Linux 4.4.0-130-generic [amd64] (Ubuntu 16.04)
      Apache 2.4.18 (Ubuntu)
      PHP 7.0.30-0ubuntu0.16.04.1 (OPcache: ENABLED)
      Python 2.7.12
      MySQL 5.7.23-0ubuntu0.16.04.1 (extension: mysqli 5.0.12-dev)
      SNMP NET-SNMP 5.7.3
      RRDtool 1.5.5 (rrdcached 1.5.5: unix:/var/run/rrdcached.sock)
      Fping 3.13 (IPv4 and IPv6)

       

      Using sensor alert with the following conditions:
      sensor_value greater @sensor_limit
      sensor_value less @sensor_limit_low

      No predefined or custom values using hh3c-transceiver-info-mib
      Still getting alerts even though /device/device=id/tab=health/metric=dbm/ shows no errors

      Also ports that are shutdown will still alert if the values are out of bounds..

      Regards
      Christian

      Attachments

        1. dbm.PNG
          32 kB
          Christian Eriksson
        2. dbm1.PNG
          48 kB
          Christian Eriksson
        3. dbm2.PNG
          37 kB
          Christian Eriksson

        Issue Links

          Activity

            [OBS-2746] Optical power out of threshold

            The thresholds should regenerate after a discovery and be present in all of the places thresholds are present (on graphs as the dotted line, on tables as the threshold entry and on the settings page)

            The status of the table on that page is historical, and applies the thresholds during page generation rather than taking into account any alerter entries that may exist for that entity.

            adama Adam Armstrong added a comment - The thresholds should regenerate after a discovery and be present in all of the places thresholds are present (on graphs as the dotted line, on tables as the threshold entry and on the settings page) The status of the table on that page is historical, and applies the thresholds during page generation rather than taking into account any alerter entries that may exist for that entity.

            Where can I see the autogenerated value?

            And isn't the info under /device/device=id/tab=health/metric=dbm/ correlated with the alerting function, meaning if there are alarms in that view, there would be an alert trigger if configured and vice versa

            Regards
            Christian

            cheri001 Christian Eriksson added a comment - Where can I see the autogenerated value? And isn't the info under /device/device=id/tab=health/metric=dbm/ correlated with the alerting function, meaning if there are alarms in that view, there would be an alert trigger if configured and vice versa Regards Christian

            It's not actually possible for there not to be thresholds on a sensor, if they are removed, the system will autogenerate them based on the most recent value. It's likely that the autogenerated value isn't useful and the measured value is frequently bouncing out of the threshold range.

            You can prevent alerts being generated for a sensor using the "Alerts" slide on the same options page, and/or by setting the threshold so it can't be tripped.

            Whether the port underneath the sensor is up or down doesn't actually figure into the alerting at all, since the two are rarely connected in a way that makes this easy to handle.

            adama Adam Armstrong added a comment - It's not actually possible for there not to be thresholds on a sensor, if they are removed, the system will autogenerate them based on the most recent value. It's likely that the autogenerated value isn't useful and the measured value is frequently bouncing out of the threshold range. You can prevent alerts being generated for a sensor using the "Alerts" slide on the same options page, and/or by setting the threshold so it can't be tripped. Whether the port underneath the sensor is up or down doesn't actually figure into the alerting at all, since the two are rarely connected in a way that makes this easy to handle.

            People

              adama Adam Armstrong
              cheri001 Christian Eriksson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: