Minor Description
Is it possible to receive syslog messages from devices that do not have snmp? We have several devices we just want to consolidate logs to with a syslog server, but cannot figure out how to do it on observium.
Attachments
Activity
| Comment |
[ _*General questions and device support can be discussed in [our Discord channel, click here to join|https://discord.gg/GjpNXKWm8W].*_ ---- Please make and attach additional information about the device: * full snmp dump from device: {noformat} 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 {noformat} _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: {noformat} ./discovery.php -d -h <device> ./poller.php -d -h <device> {noformat} * additionally attach device and/or vendor specific MIB files ---- {color:#505F79}_This comment is added automatically._{color} ] |
| Component/s | New: Default [ 10900 ] |
| Assignee | Original: Adam Armstrong [ adama ] | New: Mike Stupalov [ landy ] |
| Status | Original: Open [ 1 ] | New: Pending Response [ 10000 ] |
Observium's syslog support relies on knowing the OS of the end device, because we parse the syslog differently for different OSes, since vendors can't decide what syslog should look like.
The entire US and database structure also relies on knowing about devices, so it's difficult to handle data coming from devices we don't know.
Handling unknown device syslog would just be via a separate table with a separate UI, it could never be mixed with the existing syslog support.