You took the words right out of my mouth! :-)
What the cf-monitord (new v3 cfenvd) was designed to do with its Nova
extensions was to
eliminate the need for SNMP by providing Unix-like sensors based on file
streams and
regular expressions (the two things that make Unix infinitely superior to
a
sufficient. It will take
> implementation, testing, and experience to determine this, I think.
>
> Justin
>
> -Original Message-
> From: help-cfengine-boun...@cfengine.org
> [mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Les Mikesell
> Sent: Tuesday,
On 2/9/10 2:16 PM, "Justin Lloyd" wrote:
> Syslog-ng is what we've historically used for centralized logging and
> I'll be revamping it with v3 later this year. Combined with a
> logwatching tool, it makes a powerful combination with an snmp-based
> monitoring tool. Intuitively, I like better the
ting, and experience to determine this, I think.
Justin
-Original Message-
From: help-cfengine-boun...@cfengine.org
[mailto:help-cfengine-boun...@cfengine.org] On Behalf Of Les Mikesell
Sent: Tuesday, February 09, 2010 2:39 PM
To: help-cfengine@cfengine.org
Subject: Re: Email notificatio
On 2/9/10 1:09 PM, "Justin Lloyd" wrote:
> Has anyone done any investigation into having a monitoring tool like
> Zenoss (which we use), Nagios, or OpenNMS watch for repairs? At the very
> least, centralizing at least some of Cfengine hosts' logs and using a
> log-watching tool like Swatch or Splu
t be nice to have some
configurable mechanism for detecting such things as quickly as
reasonably possible.
Justin
From: Michael Potter [mailto:mega...@gmail.com]
Sent: Tuesday, February 09, 2010 2:30 PM
To: Justin Lloyd
Cc: Neil Watson; help-cfengine@cfengine.org
Subject: Re: Email notification of
On 2/9/2010 3:09 PM, Justin Lloyd wrote:
> Has anyone done any investigation into having a monitoring tool like
> Zenoss (which we use), Nagios, or OpenNMS watch for repairs? At the very
> least, centralizing at least some of Cfengine hosts' logs and using a
> log-watching tool like Swatch or Splun
12:56 PM
> To: help-cfengine@cfengine.org
> Subject: Re: Email notification of repairs
>
> The trouble with this type of raw email notification is lack of
> correlation and reliability. If the MTA is out of action you'll get no
> notice. If the agent attempts repeated repai
help-cfengine@cfengine.org
Subject: Re: Email notification of repairs
The trouble with this type of raw email notification is lack of
correlation and reliability. If the MTA is out of action you'll get no
notice. If the agent attempts repeated repairs repeated emails are
sent. This c
The trouble with this type of raw email notification is lack of
correlation and reliability. If the MTA is out of action you'll get no
notice. If the agent attempts repeated repairs repeated emails are
sent. This can be very disheartening.
As has been mentioned a monitoring and alerting syste
ne.org
Subject: Re: Email notification of repairs
2010/2/9 Deb Heller-Evans
Justin,
I see where you're going here - that you want to alert on unkept
promises. But I am sure that like many here on this list, I receive
hundreds if not thousands of emails per day that are already filtered
an
2010/2/9 Deb Heller-Evans
> Justin,
>
> I see where you're going here - that you want to alert on unkept promises.
> But I am sure that like many here on this list, I receive hundreds if not
> thousands of emails per day that are already filtered and sorted with often
> times more information tha
Justin,
I see where you're going here - that you want to alert on unkept promises. But
I am sure that like many here on this list, I receive hundreds if not thousands
of emails per day that are already filtered and sorted with often times more
information than I can or want to process. Alterna
ct, neither promise needs to be repaired.
Justin
-Original Message-
From: nwat...@symcor.com [mailto:nwat...@symcor.com]
Sent: Friday, February 05, 2010 11:02 AM
To: Justin Lloyd
Cc: help-cfengine@cfengine.org; help-cfengine-boun...@cfengine.org
Subject: Re: Email notification of
I don't see how this could scale. Even a small policy can have dozens of
promises. A email for each one would just flood my mailbox.
> For example, if I have a promise to ensure that a Solaris system?s
> hostname is in /etc/nodename, I should write the promise so that it
> doesn?t do anything
Hi all,
I've opened a ticket on this but I wanted to share my thoughts with the
community to see if anyone has had the same thought and perhaps has
already implemented something to this effect.
I'd like for Cfengine on each host to be able to send an email every
time it tries to repair a pr
16 matches
Mail list logo
