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

Ignored/ edited Power Usage sensors keep coming back as alert

Details

    • Vendor Bug
    • Resolution: Fixed
    • Minor
    • None
    • Enterprise Edition
    • Discovery
    • Dell N1548P, several firmware versions.

    Description

      This issue concerns Dell Networking N1548P devices.

      Several of our Dell N1548P switches are alerting because there is a power usage of 0W. This is not the correct value, but is not my main issue.

      When i disable alerting for these sensors, they will disappear for a while, but after next inventory, they will pop back up as alert. My manual disabling has reset. This results in many 'false positive' alerts continuously popping up. 

      I also tried to set a manual value of 0W, but unfortunately has the same results. The error will disappear for a while and return after an inventory.

      Could you please help me solve this issue?
      I am looking forward to your findings.

      Kind regards,
      Erik Bos

      Attachments

        1. Screenshot 2024-09-03 152738.png
          Screenshot 2024-09-03 152738.png
          150 kB
        2. discoverylogfile.log
          1.70 MB
        3. pollerlogfile.log
          2.75 MB

        Activity

          [OBS-4891] Ignored/ edited Power Usage sensors keep coming back as alert
          ebosallinqnl Erik Bos added a comment -

          Hi Mike,

           

          Thanks for your update! I will patch our Observium environment this evening and will supply a follow-up of the results.
          In response to your previous question, these aren't customized alert rules. The sensors indeed have no low limit by default, but will automatically generate Power Usage alerts in the Status Warnings and Notifications tables, triggering on 0W usage.

          When i manually set the low limit to 0W, the alerts will disappear for a while, only to return after the next inventory cycle. After next inventory, all my manual settings on the affected sensors are back to defaults. Same goes for the Ignore setting. It will ignore only until the next inventory cycle, after which it resets to default.

          ebosallinqnl Erik Bos added a comment - Hi Mike,   Thanks for your update! I will patch our Observium environment this evening and will supply a follow-up of the results. In response to your previous question, these aren't customized alert rules. The sensors indeed have no low limit by default, but will automatically generate Power Usage alerts in the Status Warnings and Notifications tables, triggering on 0W usage. When i manually set the low limit to 0W, the alerts will disappear for a while, only to return after the next inventory cycle. After next inventory, all my manual settings on the affected sensors are back to defaults. Same goes for the Ignore setting. It will ignore only until the next inventory cycle, after which it resets to default.
          landy Mike Stupalov made changes -
          Issue Type Original: Bug [ 1 ] New: Vendor Bug [ 10000 ]
          Resolution New: Fixed [ 1 ]
          Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]

          This is not real sensors, but history table.
          On any random polling interval index will changed and return incorrect (zero) value.

          I removed discovery this Oids in r13655.

          landy Mike Stupalov added a comment - This is not real sensors, but history table. On any random polling interval index will changed and return incorrect (zero) value. I removed discovery this Oids in r13655.
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]

          Please clarify, these are your customized ones alert rules?
          Than show me your alert checker rules.

          As I see, sensors not have low limit (∞) and not should alert this values by default.

          landy Mike Stupalov added a comment - Please clarify, these are your customized ones alert rules? Than show me your alert checker rules. As I see, sensors not have low limit (∞) and not should alert this values by default.
          landy Mike Stupalov made changes -
          Attachment Original: myagent1.snmpwalk [ 21425 ]
          landy Mike Stupalov made changes -
          Attachment Original: myagent2.snmpwalk [ 21426 ]
          ebosallinqnl Erik Bos added a comment - - edited

          Good morning,

           

          I've added 4 files:

          • myagent1.snmpwalk -> This is the SNMP dump from the first snmpwalk rule.
          • myagent2.snmpwalk -> This is the SNMP dump from the second snmpwalk rule.
          • discoverylogfile.log -> Output of the discovery.php -d -h
          • pollerlogfile.log -> Output of the poller.php -d -h

           

          Both snmpwalk files are quite large. I've cancelled both snmpwalks after roughly 15 minutes. From what it seems to me, the snmpwalk gets into some kind of loop and keeps re-walking the SNMP. I am not sure yet what causes this looping.

          ebosallinqnl Erik Bos added a comment - - edited Good morning,   I've added 4 files: myagent1.snmpwalk -> This is the SNMP dump from the first snmpwalk rule. myagent2.snmpwalk -> This is the SNMP dump from the second snmpwalk rule. discoverylogfile.log -> Output of the discovery.php -d -h pollerlogfile.log -> Output of the poller.php -d -h   Both snmpwalk files are quite large. I've cancelled both snmpwalks after roughly 15 minutes. From what it seems to me, the snmpwalk gets into some kind of loop and keeps re-walking the SNMP. I am not sure yet what causes this looping.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          ebosallinqnl Erik Bos made changes -
          Attachment New: discoverylogfile.log [ 21424 ]
          Attachment New: myagent1.snmpwalk [ 21425 ]
          Attachment New: myagent2.snmpwalk [ 21426 ]
          Attachment New: pollerlogfile.log [ 21427 ]

          People

            landy Mike Stupalov
            ebosallinqnl Erik Bos
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: