News
#3657: clear automatically ipservice
Hello:
My problem is a bit complicated to explain. We conducted the installation of zenoss 2.2.3 without problems, then configure zenoss with all services and processes in each server.
But to reach another day at the office and the
Tip of the Month: Layer 3 Dependency Checker
This tip has been adapted from Wouter ‘netdata’ D’Haeseleer’s post on Zenoss-Users:
http://community.zenoss.com/forums/viewtopic.php?p=23030
Download this file and put it in
#3622: Clear alerts not working?
I have a threshold set on a zencommand datapoint. It is defined as follows:
min value = 0
max value = 5
escalate count = 5
severity = warning
against it an alert is defined with a 120 sec delay and send clear messages on. I get down alerts but don't get any clears.
Zenoss IRC session Thursday August 28 at 11am EST
Zenoss developers will be available for questions on Thursday, August 28 at 11am EST in the #zenoss IRC channel on irc.freenode.net (port 6667). Please drop in and bring your questions, answers, suggestions and feedback. Our JMX and Texas BBQ expert JP will be on hand to answer your questions. See you there!
We’ll log [...]
Announcing the Winners of the Zenoss Submit a ZenPack Contest
The results are in and it’s time to announce the winners of the Zenoss Submit a ZenPack Contest. There were a whole lot of exceptional entries over the past few weeks. We had a tremendous response and there were 25 entries, more than doubling the number of Zenoss Community ZenPacks available [...]
#3602: SMTP username and password field re-populated at reboot
It seems that everytime I reboot my zenoss server, those two fields get reinitialised with "admin/********". I don't use any smtp auth (except the source IP) so that every time I reboot, all my alerts are gone ...
If I'm the one rebooting
#3598: Only clear events get moved to the history table
When I look at the history table the only events there are clear's the matching down events don't exist. This also may be causing clear alerts to be missed?
The Submit a ZenPack Contest Entries
The Zenoss Submit a ZenPack Contest has concluded and first off, we would like to thank all the generous contributors to the contest! We had a tremendous response rate, more than doubling the number of Community ZenPacks that were available before the contest. There were a lot of really great entries, we’ll be [...]
#3588: Daemons don't restart cycles after zenhub connection failure
When the collector daemons timeout connecting to zenhub, then later reconnect they will not automatically start their collection cycles. This leaves them running, but doing nothing. Fortunately they aren't even sending heartbeats so the failure is
#3587: On restart, Zenoss attempts to discover networks that have zAutoDiscover==False
A limitation for my project is that Zenoss after a restart is always trying to discover the networks. My client has a class B (e.g 134.111.X.X) and many sites (Chile, Germany) and different usages (isolated network, etc...).
To reproduce : *
#3578: Add env variable SMIPATH as zProperty and update zenmib.py to use it
It has been noted on the list that some people have had to manually add SMIPATH to their environment variables before running zenmib.py to add a MIB to Zenoss. By creating a zProperty (eg zSMIPATH), this environment can be more easily tracked and
#3583: update to InterfaceMap.py for fixing Cisco CatOS port name & descriptions
http://community.zenoss.com/forums/viewtopic.php?p=23726
Several Cisco users report that the port names and descriptions are not correctly identified. The thread has an implementation to correct this for Cisco devices.
#3581: Alerting rule with repeat enabled doesn't stop when acknowledged
An event that triggers an alerting rule with repeat enabled will continue to repeat even if the event is acknowledged. The alerts will stop once the event is moved to history. The Admin Guide says the alerts will stop when the event is acknowledged.
#3580: Send an event on production state changes
It would be good to log when the production state changes. Make an event... the user can always just put it to the history.
#3579: Number of Mail/Pages limitation
It would be nice to have a "limit" field allowing to limit the number of SMS/eMails sent to a user.
#3584: device field of heartbeat events should be monitor name, not FQDN
The device field of heartbeat events would be better off as the options.monitor instead of socket.getfqdn(). This would allow fail-over in HA environments to work without sending in a duplicate set of heartbeats.
#3577: Can't add devices when autodiscovery is off
I did install 2.2.3 for monitoring around 200 Worstations, 20 ciscos and 50 severs.
I read in the forum that if auto-discovery is off you can't add devices. It is a serious limitation for users because they need to do two steps instead of