I'm psyched... I think I have my boss almost ready to implement Zenoss and
still only see small benefits to using Dashboard.
Craig
On Jun 24, 2011, at 10:53 AM, Don wrote:
> Ok, here's the report processor to send events to Zenoss, based off
> James' Zendesk module.
>
> https://github.com/donj
Ok, here's the report processor to send events to Zenoss, based off
James' Zendesk module.
https://github.com/donjohnson/puppet-zenoss
-Don
Release Engineer / Toolsmith, VerticalResponse
On Wed, Jun 8, 2011 at 6:09 PM, Don wrote:
> Thanks for the help off-list, James.
>
> here's the stub I'm us
Thanks for the help off-list, James.
here's the stub I'm using to check if the log is error-ful, inside of
process():
def process
failure = false
#iterate through each log object and look for failures
self.logs.each do |log|
if log.level.to_s == 'err' || 'alert' || 'emerg' |
Don wrote:
>
> I'm running 2.6.4 on the master & client. pluginsync is true on both,
> and reports = zenoss only on the master for this test.
>
> Why is self.status not working in this case?
>
The issue is that status is only available in the V2 report format in
Puppet 2.6.5 and onwards. Before
Don wrote:
> (possible double-post)
>
> James,
>
> This is all wonderfully helpful and I just spent a little while
> writing up a Zenoss processor to send an event on failure using
> XMLRPC::Client, modeled directly after your puppet-zendesk module,
> replacing the HTTParty guts with XMLRPC guts.
James,
This is all wonderfully helpful and I just spent a little time writing
up a Zenoss processor to send an event on failure using
XMLRPC::Client, modeled directly after your puppet-zendesk module,
replacing the HTTParty guts with XMLRPC guts. I've encountered a
problem though (and we can refer
(possible double-post)
James,
This is all wonderfully helpful and I just spent a little while
writing up a Zenoss processor to send an event on failure using
XMLRPC::Client, modeled directly after your puppet-zendesk module,
replacing the HTTParty guts with XMLRPC guts. I've encountered a
problem
Scratch my last question, had to restart puppetmaster.
Thanks again for your help and these plugins
- Trey
On Jun 8, 5:01 pm, treydock wrote:
> That did it! I'm now getting messages over Jabber upon failure!!
>
> Is the debug output you refered to earlier, "Sending status for
> name.of.host to
That did it! I'm now getting messages over Jabber upon failure!!
Is the debug output you refered to earlier, "Sending status for
name.of.host to XMMP user jabber.user" something I would see from
Puppet or the Jabber server? I have yet to see similar output, but
the IM is now working.
Also now t
treydock wrote:
> I don't have any lines like that no.
>
> Could the daemon line for puppetmaster be effecting this? Is the "--
> reports" option necessary since my puppet.conf has that specified?
>
> PUPPETMASTER_EXTRA_OPTS="--reports puppet_dashboard --debug"
>
> Other than that and my puppet
On 2011 6 8 20:16, "Craig" wrote:
>
> Hi,
>
> These sample reports have been very useful, thanks!
>
> Is there is a way to only send a report once every 24 hours (say)?
> For example, I want to know about failed runs, but not every time
> someone is hacking around, changing something, re-running e
I don't have any lines like that no.
Could the daemon line for puppetmaster be effecting this? Is the "--
reports" option necessary since my puppet.conf has that specified?
PUPPETMASTER_EXTRA_OPTS="--reports puppet_dashboard --debug"
Other than that and my puppet.conf I haven't found any furthe
Craig wrote:
> Hi,
>
> These sample reports have been very useful, thanks!
>
> Is there is a way to only send a report once every 24 hours (say)?
> For example, I want to know about failed runs, but not every time
> someone is hacking around, changing something, re-running etc.
>
> I can think o
Hi,
These sample reports have been very useful, thanks!
Is there is a way to only send a report once every 24 hours (say)?
For example, I want to know about failed runs, but not every time
someone is hacking around, changing something, re-running etc.
I can think of all sorts of workarounds, jus
treydock wrote:
> My [master] has :
>
> report = true
> reports = http, store, xmpp
> pluginsync = true
>
> The [agent] includes:
>report = true
>listen = true
>pluginsync = true
>
>
> The second agent I tested with also has the same configuration as the
> above [agent]
My [master] has :
report = true
reports = http, store, xmpp
pluginsync = true
The [agent] includes:
report = true
listen = true
pluginsync = true
The second agent I tested with also has the same configuration as the
above [agent]
Correct, the xmpp.yaml has all that informa
treydock wrote:
> Ok I restarted puppetmaster daemon and then broke a module to create a
> failed puppet run on the same host as the master...and here's /var/log/
> messages from that
Can I confirm you have:
[master]
report = true
reports = xmpp
[agent]
report = true
In your puppet.conf on the
Ok I restarted puppetmaster daemon and then broke a module to create a
failed puppet run on the same host as the master...and here's /var/log/
messages from that
Jun 7 18:37:19 puppetmaster puppet-master[27426]: Reopening log files
Jun 7 18:37:19 puppetmaster puppet-master[27426]: Starting Puppe
treydock wrote:
> Excuse the dumb question, but what file is the default location or
> what configuration variable defines that location?
>
> I've noticed the bulk of puppetmaster logs go either in /var/log/
> puppet/masterhttp.log (previous message) or /var/log/message (syslog
> I'm assuming). O
Excuse the dumb question, but what file is the default location or
what configuration variable defines that location?
I've noticed the bulk of puppetmaster logs go either in /var/log/
puppet/masterhttp.log (previous message) or /var/log/message (syslog
I'm assuming). Or is there a different place
treydock wrote:
> This is the output from master.log during the failed puppet run.
Sorry I meant the output from the master daemon puppetmasterd or puppet
master.
Thanks
James
--
James Turnbull
Puppet Labs
1-503-734-8571
--
You received this message because you are subscribed to the Google G
This is the output from master.log during the failed puppet run.
[2011-06-07 02:24:16] DEBUG accept: 10.1.0.1:39742
[2011-06-07 02:24:16] DEBUG Puppet::Network::HTTP::WEBrickREST is
invoked.
[2011-06-07 02:24:16] puppetmaster.domain - - [07/Jun/2011:02:24:16
CDT] "GET /production/file_metadatas/pl
treydock wrote:
The report processor was synced to /var/lib/puppet/lib/reports/ . I
enabled puppetmaster to run in debug mode but haven't seen anything
mentioning reports when I run test runs. I purposly misspelled a
module for the puppetmaster and run puppetd --test, but no reports
except thos
The report processor was synced to /var/lib/puppet/lib/reports/ . I
enabled puppetmaster to run in debug mode but haven't seen anything
mentioning reports when I run test runs. I purposly misspelled a
module for the puppetmaster and run puppetd --test, but no reports
except those in puppet-dashbo
treydock wrote:
> These will be most useful!! Thank you.
>
> How can I test that these are functioning? I have setup the XMPP as
> well as modified that to send emails. However when I purposely cause
> a puppet run to fail I do not receive either email or jabber message.
Is the report processo
These will be most useful!! Thank you.
How can I test that these are functioning? I have setup the XMPP as
well as modified that to send emails. However when I purposely cause
a puppet run to fail I do not receive either email or jabber message.
Thanks
- Trey
On May 31, 10:09 am, James Turnbu
26 matches
Mail list logo