'Aloha!
I promised you more questions for use in my evaluation process, here comes the next one:
Odd devices: besides the 4000 routers and switches in my previous post, our business does a great deal of video transmissions. This is handled with crazy video codec boxes which sometimes have very limited SNMP capabilities.
I face two problems: - it cant be autodiscovered; the MIB simply doesn't that. I have a database describing exactly what we have and how it's configured. - it's covered by NDAs, so I cant event tell you much about it.
I would like to graph various parameters in these devices using observium, but I guess I will have to implement these myself. (or hire somebody to sign the NDA and hack something together for me). Also, sometimes the concept needing graphing isn't really bound to a single device, but more a collation of multiple states from multiple devices.
I understand that observium isn't really meant to be extensible by the end customer (me) by simply tweaking configuration. I read "It's not as simple as "adding the MIB", actual code needs to be written to support the device and its features. You could learn PHP and familiarise yourself with the Observium codebase and write support for it yourself." as a warning, as i'm nowhere a competent PHP hacker.
Think the questions are: - is observium at all the right tool for the job? (a goal is to limit the number of tools the NOC has to learn) - can observium live in an non-auto-discovery world? - can observium handle abstract measurements not bound to a specific device?
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?
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
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
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
participantes (3)
-
Adam Armstrong -
Morten Guldager -
Nikolay Shopik