On Fri, 30 Sep 2016 13:06:54 +0200 tranimarc@hotmail.com wrote:
I'm working on a project to replace all polled data collections we have running on Cacti for our network devices ( Cisco, F5, Brocade, Sanbox, ..... ) to graphite. Actually your tools is the only one using graphite out of the box and I was wondering how much work it would be to add unsupported monitoring MIBs and if there would be some example other than https://nav.uninett.no/doc/4.2/hacking/adding-environment-probe-support.html ?
Hi there,
First of all, you should be looking at the latest version, which is: https://nav.uninett.no/doc/4.5/hacking/adding-environment-probe-support.html
Also, the inclusion of new MIBs for the sensors plugins has been somewhat simplified in trunk, which will hit NAV 4.6: https://nav.uninett.no/doc/dev/hacking/adding-environment-probe-support.html
If your collection needs will fit inside the sensors framework of NAV, then this is the way to go. If you need more examples, the best way is to study the code of the other MibRetriever classes (as used by nav/ipdevpoll/plugins/sensors.py) provided with NAV.
If you would rather have NAV model the data in a different way, we're open to suggestions (and maybe take the discussion to the nav-dev list).
Actually all exotic devices are showing values for their network interfaces but most are not retrieving CPU/Memory and other specific data.
That's because CPU and memory data are mostly stuck in proprietary MIBs when it comes to networking devices (unless you count the IETF-published HOST-RESOURCES-MIB, which is used mainly by server implementations, and which we are considering for inclusion into NAV).