![](https://secure.gravatar.com/avatar/ede44170d3b4d84fc5e666bf21ad6b45.jpg?s=120&d=mm&r=g)
Some of them does, but will return way too many (empty) placeholder objects for codecs that theoretically could be there but in real life isn't. Yes, they their snmp implementation is a bit odd.
Others will crash or timeout trying to walk their inventory.
On Wed, Nov 12, 2014 at 11:29 PM, Adam Armstrong adama@memetic.org wrote:
The device's SNMP stack doesn't do snmpwalk?!
Adam.
Sent with AquaMail for Android http://www.aqua-mail.com
On 12 November 2014 13:18:49 Morten Guldager morten.guldager@gmail.com wrote:
Ahh, I see, I wasn't clear in what I wrote.
By non-auto-discovery I did not mean manually adding devices, but more, manually maintaining the list of measured points within the device.
An example: a device has 3 codecs, each codec has a counter telling how many video corrections it has made. You can not ask the device which codecs it has, but once you know, you can snmpget the correction counter for that particular codec.
I know which codecs each device has, it's in the "magic excel sheet". I can calculate the correct snmp OID. (or have python do it)
On Wed, Nov 12, 2014 at 8:50 AM, Nikolay Shopik shopik@inblock.ru wrote:
As long you up to job adding hosts manually - its working perfectly fine w/o auto discovery. I'm not even used it once
On 12 нояб. 2014 г., at 10:32, Morten Guldager <
morten.guldager@gmail.com> wrote:
can observium live in an non-auto-discovery world?
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- /Morten %-) _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium