When adding a VM to be monitored via SNMP into observium if the VM is on the same cluster it will not be fully discovered.

Device have troubles with bulk requests. Not sure why on same VMs different behavior.
But you need disable or reduce SNMP max-repetition value for this device (on device
edit page -> SNMP). 0 - for disable, or 20/30/50 for reduce..

CMD[/usr/bin/snmpbulkwalk -Cr'100' -v2c -c *** -Pud -OQUs -m IF-MIB -M /opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp 'udp':'host':'161' ifDescr]

CMD EXITCODE[1]

CMD RUNTIME[6.0517s]

STDOUT[

]

STDERR[

Timeout: No Response from udp:host:161

]

SNMP STATUS[FALSE]

SNMP ERROR[#1004 - Bulk Request timeout]

I attached the discoveries, with the server that is not being discovered as expected, I also re-configured the snmpd.conf file to be the same as the observium recommended one and I did not see any changes in what is being graphed.

pls note, default snmpd.conf in debian/ubuntu have 2 default views: full for localhost requests and system for all others (with very limited output).
That why we promote own variant of snmpd config.

you missed discovery debug outputs, this is more actual for this case.

Ok, I installed 2 fresh Debian VM's, the only difference is they are located on different clusters, I also included screen shots of what is displayed by observium when they are being monitored.

I also included the snmpwalks for both.    They are using the exact same snmpd config, the underlying hardware and hypervisor versions are also the same.

pls make debug output as bot requested.
I think you have limitations for view in `/etc/snmp/snmpd.conf` on VM.

Look example here:
https://docs.observium.org/device_linux/#example-net-snmp-configuration

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.