I have the same issue. We are running a bunch of DSLAM (Zhone and Keymile) and we want to monitor the numebr of calls, the temperature and so on (no more than 10 SNMP OID checks). How can I ask to add this kind of support? Can I write my own check files for this hardware and (if it's working fine) pull up on the main release? Where to start writing a custom check? Regards
There is no doubt a very wide range of equipment that isn't supported by Observium. Nothing against Adam or the other developers, but there is more equipment types that Observium users or would-be users) would want to watch than they could reasonably code support for. That's the beauty of SNMP, a fairly low impact to support additional types of data assuming the manufacturer has provided the documentation (MIB) for it.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
----- Original Message -----
From: lom@digitelitalia.com To: observium@observium.org Sent: Wednesday, December 31, 2014 5:06:31 AM Subject: Re: [Observium] Custom SNMP OID
I have the same issue. We are running a bunch of DSLAM (Zhone and Keymile) and we want to monitor the numebr of calls, the temperature and so on (no more than 10 SNMP OID checks). How can I ask to add this kind of support? Can I write my own check files for this hardware and (if it's working fine) pull up on the main release? Where to start writing a custom check? Regards
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
The below request was a perfect example of why we are more interested in adding proper support for things than giving people the tools to build ugly hacks.
The requester even asked about feeding it back to the code base, thus automatically giving that capability to everyone.
It's not at all difficult to write support for sensors and graph simple things. Graphing has been simplified down to an array now, and sensors are usually done with an SNMP query, and a foreach() loop calling discover_sensor for each entry. We would like to simplify this to a definition array too, if possible.
I doubt I will ever permit these definition arrays to be added in a cacti-esque fashion. They will always need to be patched into the code base itself, thus forcing people to feed them upstream so they are automatically available to (and improvable/updatable by) everyone.
I consider these things to be features, not limitations. Observium doesn't seek to do everything regardless of the usability, but rather to support as much as we can in a fully automated fashion.
adam.
------ Original Message ------ From: "Mike Hammett" observium-list@ics-il.net To: "Observium Network Observation System" observium@observium.org Sent: 12/31/2014 8:01:42 AM Subject: Re: [Observium] Custom SNMP OID
There is no doubt a very wide range of equipment that isn't supported by Observium. Nothing against Adam or the other developers, but there is more equipment types that Observium users or would-be users) would want to watch than they could reasonably code support for. That's the beauty of SNMP, a fairly low impact to support additional types of data assuming the manufacturer has provided the documentation (MIB) for it.
Mike Hammett Intelligent Computing Solutions http://www.ics-il.com
From: lom@digitelitalia.com To: observium@observium.org Sent: Wednesday, December 31, 2014 5:06:31 AM Subject: Re: [Observium] Custom SNMP OID
I have the same issue. We are running a bunch of DSLAM (Zhone and Keymile) and we want to monitor the numebr of calls, the temperature and so on (no more than 10 SNMP OID checks). How can I ask to add this kind of support? Can I write my own check files for this hardware and (if it's working fine) pull up on the main release? Where to start writing a custom check? Regards
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi,
To add support for new devices or new entities, it's necessary to write code (or sometimes simply arrays describing the data to be collected).
In the case of sensors, you write a discovery module to walk the relevent tables on the device and pass data to a function which will register them in the database.
There are some examples in : includes/discovery/sensors/
The entity-sensor-mib code uses virtually all features of the functions, bluecoat code is a bit simpler and the trapeze one is even simpler. You can even just hardcode things on devices with fixed sensors.
You generally need to walk the tables and then run a loop over the data feeding each sensor to discover_sensor().
To graph non-entity (a non-entity is something we don't have specific infrastructure for (like cpu, memory, sensor, port, etc). Basically everything in the graphs tab.
There is a new way to graph these things, you can write code explaining to observium how to collect a table (or set of oids) of data and put it into an rrd file (includes/polling/graphs/) and then a set of definitions to build graphs in includes/definitions/graphs.inc.php (in the middle of the file are some new-style definitions). Graphs which can't be built using these definitions can be built with code like in html/includes/graphs/device/
It's actually a lot simpler than it sounds, and you can usually figure most of it out by reading the code, since we intentionally keep code simple so that it's easy to work with.
adam.
------ Original Message ------ From: lom@digitelitalia.com To: observium@observium.org Sent: 12/31/2014 5:06:31 AM Subject: Re: [Observium] Custom SNMP OID
I have the same issue. We are running a bunch of DSLAM (Zhone and Keymile) and we want to monitor the numebr of calls, the temperature and so on (no more than 10 SNMP OID checks). How can I ask to add this kind of support? Can I write my own check files for this hardware and (if it's working fine) pull up on the main release? Where to start writing a custom check? Regards
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong -
lom＠digitelitalia.com -
Mike Hammett