Zenoss Self Monitoring

[ThinkItOverFirst]

ThinkItOverFirst [http://community.zenoss.org/people/ThinkItOverFirst] created the discussion

"Zenoss Self Monitoring"

To view the discussion, visit: http://community.zenoss.org/message/66309#66309

--------------------------------------------------------------
Recently, I've been toying with the idea of adding some self-monitoring to Zenoss.  Previously we've used Enterprise 3.2.1, but have since upgraded to 4.1.1.  In both version, we've come across a particular issue.  We have a large number of reports that we send to users via cron + reportmail.  From time to time, we get messages from users about data missing from reports.  Sure enough, we dig around and find that performance data hasn't been collected for a particular device  -- not to mention, nothing substantial in the event history to suggest a problem. 

In an effort to be proactive instead of reactive to these issues, my immediate thought is to run a cron that checks to see if/when the last time an rrd file was touched.  If it hasn't been touch in +X amount of time,+ then fire off a message to someone. I leaned on Zenoss support a bit to see if they had any suggestions, but they simply stated that there was talk of adding such functionality to future releases.  I'm curious if anyone else has implemented anything along these lines in their environment to keep Zenoss honest.
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/66309#66309]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Shane Scott]

Shane Scott [http://community.zenoss.org/people/hackman238] created the discussion

"Re: Zenoss Self Monitoring"

To view the discussion, visit: http://community.zenoss.org/message/66326#66326

--------------------------------------------------------------
ThinkItOver:

This feature is planned and on the roadmap.

What I do, in the mean time, is test the process table and use predictive thresholds on the collector graphs. The datapoints graph should never change abruptly so it's prefect for detecting collecting failures.

Best,
--Shane (Hackman238)
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/66326#66326]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[kb8u]

kb8u [http://community.zenoss.org/people/kb8u] created the discussion

"Re: Zenoss Self Monitoring"

To view the discussion, visit: http://community.zenoss.org/message/66341#66341

--------------------------------------------------------------
Along those lines, I've just added some basic daemon monitoring using monit.  It also has the capability to detect file timestamp changes but I'm not doing that right now.  http://mmonit.com/monit/documentation/monit.html#timestamp_testing http://mmonit.com/monit/documentation/monit.html#timestamp_testing
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/66341#66341]

Start a new discussion in zenoss-users by email
[discussions-community-forums-zenoss--***@community.zenoss.org] -or- at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]