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

Month end date in Previous billing period is wrong

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • None
    • Billing
    • None

    Description

      Month end date in Previous billing period is wrong, ie 28th of Jan

      Attachments

        1. 0 percent.png
          81 kB
          Dennis Jasch
        2. PRevious billing period.png
          194 kB
          Dennis Jasch

        Activity

          [OBS-4011] Month end date in Previous billing period is wrong

          Also fixed in r11870.

          landy Mike Stupalov added a comment - Also fixed in r11870.

          derp

          landy Mike Stupalov added a comment - derp

           

          It seems now all the percent gauges are zeroed ... ?

          yanky83 Dennis Jasch added a comment -   It seems now all the percent gauges are zeroed ... ?

          Should be fixed in r11869.

          landy Mike Stupalov added a comment - Should be fixed in r11869.

          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

            landy Mike Stupalov
            yanky83 Dennis Jasch
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: