On Wed, 12 Nov 2014 22:19:35 +0100 (CET) jch@raytheon.com wrote:
I am really new to NAV, but I've liked it so far in my lab testing. I do have some routers whose CPU utilization is not showing up, and I would like to poll some non-standard OIDs (like IP SLA metrics) even if NAV won't display them. I could use graphite to do that for me separately, but utilize the engine that NAV provides. Could someone point me to where I might need to go to do that?
Is there an OID somewhere that could be added or updated to support newer router CPU metrics, so that my Cisco ISR-G2 routers will have that displayed?
How can I customize the polling of some devices (mostly Cisco routers) to get additional metrics? I have not found where I can modify or add scripts to do this and need some general pointers on where to look on the internet as well as on the system. Since this is just a lab environment, I have all the NAV components on one server.
Hi Joel,
Great to hear you want to tinker with NAV code. Unfortunately, documentation on extending NAV code is sorely lacking. We are, however, prepared to answer any questions you might have in that regard (we're also on IRC, but our timezones may possibly differ too much for meaningful conversation there).
Just last week, I wrote a guide to adding support for new types of environment probes to NAV. It may not help explicitly with your scenario, but should still be informative enough to move you along:
https://nav.uninett.no/doc/dev/hacking/adding-environment-probe-support.html
This guide describes the `sensors` and `statsensors` plugins in ipdevpoll. There's a similar plugin called `statsystem`, which collects "system" stats from devices and push those to Graphite. With the proper MIB implementation (which is partly described in the guide above), this plugin could also collect system stats from new MIBs.
See https://bitbucket.org/mbrekkevold/nav-mirror/src/9a6c02de139a73109982a0cae1c... - the code is built up more or less the same way as the `sensors` plugin, mapping known MIB implementations to enterprise/vendor IDs.
IP SLA metrics may not fall nicely into the "system" statistics category, but given the examples above, a new plugin shouldn't be too difficult to write.
Also, I think this discussion belongs on the nav-dev list. I've Cc-ed that list, and would suggest that further replies are sent only there.