![]() |
![]() |
Subject: | Monitoring the Zenoss Collectors |
Author: | [Not Specified] |
Posted: | 2014-12-18 07:38 |
Recently we have been trying out Zenoss core collectors - version 4.2.5 using a patched version of Egon's distributed collector code (to roll in some fixes that aren't present in the original) : https://github.com/resilientplc/ZenPacks.community.DistributedCollectors
However although it generally works I am having weird issues where when I change a device's collector then the new collector starts polling it - although the old collector is still polling it as well. I have verified this through using tcpdump on both new and old collector.
sudo tcpdump -i eth0 -c 500 -tttt -q "((port 161 or icmp or portrange 49152-65535) and host ${device/manageIp})"
If I restart the hub or old collector then it stops polling it - but is there a way for it to hand over cleanly
Also since I have added a User Command of the above tcpdump then is there a TALES expression that includes the devices collector I would like to write a small shell script to use the already existing ssh passwordless connection to log onto the remote collector and run the tcpdump command.
What I really want to do is find out if a collector (or hub) thinks it is supposed to be collecting from a device so I can validate and check that the hub-collector setup is actually working.
Any ideas
Subject: | Tales expression for the |
Author: | [Not Specified] |
Posted: | 2014-12-18 07:46 |
Tales expression for the collector: ${device/getPerformanceServerName}
Subject: | Thank you so much, Dpirmann! |
Author: | [Not Specified] |
Posted: | 2014-12-19 04:31 |
Thank you so much, Dpirmann! Would never have thought that was it but the test runs perfectly!
I guess I will put together some User Commands to run tcpdump or zencommand on the ${device/getPerformanceServerName} server.
Anyone else know how to "nudge" a collector to stop collecting when it shouldn't
< |
Previous ERROR zen.PythonClient [SOLVED] |
Next OpenStack (Tenent) ZenPack SSL Issue |
> |