Minor Description
I have add my ESXi hosts into OBS, using SNMP which works.
I have then tried to add OBS as the remote syslog server with udp://osserver:514 as the link in the Syslog.global.logHost option in Advanced System Settings for each of my ESXi hosts... The host names and IP are defined in OBS. (and I have other syslog hosts reporting, so I know it works for other hosts)... but I get nothing from the ESXi servers... I have tried to trigger different things, but I get nothing...
Also I have tried to add the OBS server in the syslog option on the vCenter Appliance Server... I can do a test which vCenter tells me is send OK, yet I get nothing on OBS.. This might be because the vCenter Appliance is virtual and is not added to OBS as a host (not sure if you even can, because it does not support SNMP...) ? But it would be great to It was possible to add it...
I know this is two problems, yet it is related and maybe someone has tried to set this up?
Attachments
Activity
The main purpose of Observium is monitoring via snmp.
Any other features is extending of this functionality. Like receiving Syslog also required that host/device should be registered in Observium.
As I know, vSphere support SNMP server, you can configure it:
https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.monitoring.doc/GUID-8EF36D7D-59B6-4C74-B1AA-4A9D18AB6250.html
Hello again. it looks like it took awhile for the ESXi servers to post anything in the syslog.
I now have logs from all my servers. So that part is solved.
The configured syslog on the vSphere appliance does not however log anything, and I think that it is because the server is not registered in OBS, which is due to the fact that it does not have any SNMP server. It only have syslog...
Does OBS require that the server is setup within OBS in order to receive syslogs? And is there a way around that?
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.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf 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.
Hi Mike
Thank you for taking your time for answering this.
I understand the issue, but I hoped that there was a way to get around this, because the vCenter server does not support SNMP, the link your supplied only lists the ESXi servers which does have SNMP support.
It is of cause because we would like to have as few monitoring systems as possible... and if we would like to monitor our vCenter server we would have to do it via GrayLog or some other syslog server... it would be nice to have most of this inside Observium. But where do you stop?
I can see that you have enabled nagios-plugins which is also a stray away from SNMP 
My suggestion to "fix" this would of cause be to enable a way to add a host which is just pinged (without SNMP), this would then allow syslog etc. to be enabled against that host... I also understand that maybe it's only me requesting this, and I understand if this is not implemented
Thanks!