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

Not discover CPU

Details

    • Vendor Bug
    • Resolution: Not A Bug
    • Major
    • None
    • None
    • Default
    • None

    Description

      Observium not recognize CPU Type

      Attachments

        Activity

          [OBS-4875] Not discover CPU
          landy Mike Stupalov made changes -
          Issue Type Original: Bug [ 1 ] New: Vendor Bug [ 10000 ]
          Resolution New: Not A Bug [ 6 ]
          Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]
          landy Mike Stupalov added a comment -

          Look this page:
          https://docs.observium.org/device_windows/

          landy Mike Stupalov added a comment - Look this page: https://docs.observium.org/device_windows/
          adama Adam Armstrong made changes -
          Assignee Original: Mike Stupalov [ landy ] New: Adam Armstrong [ adama ]
          adama Adam Armstrong added a comment -

          This is not really related to Observium. We only display the string reported by the OS.

          In this case the snmp service on windows is not providing the processor description.

          An alternative SNMP daemon on windows might provide better information, but I don’t really know.

          adama Adam Armstrong added a comment - This is not really related to Observium. We only display the string reported by the OS. In this case the snmp service on windows is not providing the processor description. An alternative SNMP daemon on windows might provide better information, but I don’t really know.
          bot Observium Bot made changes -
          Component/s New: Default [ 10900 ]
          bot Observium Bot made changes -
          Assignee Original: Adam Armstrong [ adama ] New: Mike Stupalov [ landy ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          pbrzostowski Pawel Brzostowski created issue -
          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.

          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

            adama Adam Armstrong
            pbrzostowski Pawel Brzostowski
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: