IP SLA Enumeration & Monitoring v3 for Zenoss is here!. This new version includes tons of new features, bug fixes, and significantly improved performance over past versions. Version 3 implements a new dedicated daemon, zensla, to collect SLA information from hosts. The introduction of said daemon also improves compatibility with remote collector situations and code compatibility with Zenoss core, helping to avoid code breakage with the advent of new Zenoss patches.
Please report bugs in the forum or contact me :-)
New features include:
Zenoss 2.5.x notes:
Zenoss 3.x notes:
More official documentation will be posted soon along with general IP SLA related documentation.
Hi Shane, thanks again for this Zenpack.
As discussed in irc the other night, I've noticed a bug when attempting to add IP SLA monitoring to an existing device class (/Network/Router/Cisco). Due to other constraints, I need to have all of my Cisco routers in this device class, so cannot permanently move them to /Network/IPSLA.
Just to be clear, placing a new device myrouter.mydomain.net in /Devices/Network/IPSLA worked first time, with the various IPSLAs detected and graphed correctly.
To set up IPSLA monitoring on routers under /Network/Router/Cisco, I have set the zPythonClass of this device group to ZenPacks.ShaneScott.ipSLA.SLADevice and I've also added SLADevice to the device group's Modeler Plugins.
Next I deleted myrouter.mydomain.net from Zenoss and re-added/modelled it under /Network/Router/Cisco. The modelling appears to work correctly as I now see my SLAs listed under Components. However when I try to look at the graphs for these, nothing is rendering in the bottom pane where the graphs should be. I can see that it is attempting to load an iframe, but the iframe is empty:
Also I noticed that there is no IPSLA data being gathered /opt/zenoss/perf/Devices/myrouter.mydomain.net after the process above.
So, I'm not sure if having IPSLA monitoring in /Network/Router/Cisco is possible, but if there is some way to fix this it'd be great.
I hope you've been well!
The problem has been discovered and planned to be fixed for the next release of the IP SLA pack in a month or so. : )
I am testing it on zenoss 3.1.0 and only interesting in ip sla jitter area, it works well.
Question, I see a "View SLAs" there, is it any purpose for? if you click the one instance, it keeps cascade the screens. I think the "old" version shows the parameter values of the instance. Now this feature you put it is at "SLAS" display "detail". Would it be possible to format them as a table like it was in old version? Thanks!
Soon after a Zenoss restart or a zensla restart, it reports a "zensla heartbeat failure" event. Despite this error, it seem to do its job, and the graphs shows no sign of polling issue.
The zensla.log mention nothing special :
2012-01-11 01:43:36,960 INFO zen.zensla: ******** Cycle completed ********
2012-01-11 01:43:36,960 INFO zen.zensla: Sent 417 OID requests
2012-01-11 01:43:36,961 INFO zen.zensla: Queried 601 devices
2012-01-11 01:43:36,961 INFO zen.zensla: 0 in queue still unqueried
2012-01-11 01:43:36,961 INFO zen.zensla: Successes: 595 Failures: 0 Not reporting: 6
2012-01-11 01:43:36,962 INFO zen.zensla: Waited on 12 queries from previous cycles.
2012-01-11 01:43:36,962 INFO zen.zensla: Successes: 0 Failures: 0 Not reporting: 12
2012-01-11 01:43:36,962 INFO zen.zensla: Cycle lasted 300.00 seconds
2012-01-11 01:43:36,963 INFO zen.zensla: *********************************
This issue is not new, has been there since the beginning. We use ZenPacks.ShaneScott.ipSLA 3.0.
Any idea ?
Follow Us On Twitter »
||Latest from the Zenoss Blog »||Community||Products||Services||Customers||About Us|
Copyright © 2005-2011 Zenoss, Inc.