Issue #4339 has been updated by Brice Figureau.

Brice Figureau wrote:
> R.I. Pienaar wrote:
> > I tested this, this is awesome can't wait for it to be released :)
> 
> I feel the same :)
> I want to be able to export all that data through SNMP.
> 
> > would be good if in the 2nd data where no changes were made all the data 
> > from the 3rd would still be in the file just with 0s
> 
> Yeah, I followed what the textual summary was doing (ie removing all 0s, but 
> not float 0s).
> I think it make sense to keep all the information in the hash format. I'll 
> modify the code.

It turns out that it's not as simple as it sounded first :(
Most of the information like total changes, resources statuses or events states 
are never generated nor known if nothing happened.
The only reasonably simple thing I was able to add is a total: 0 for every 
empty section.
which gives this when no changes:
<pre>
--- 
  time: 
    last_run: 1289574285
    schedule: 0.000824
    config_retrieval: 0.161079883575439
    filebucket: 0.000136
    file: 0.00084
  resources: 
    total: 8
  events: 
    total: 0
  changes: 
    total: 0
</pre>

Would that work?

It would be possible to fully populate the "resources" section with the various 
resource state (because those are known even when there are no changes), but 
that will also change the report that is sent to the master (which also omits 0 
stuff).
If that's acceptable, I can add it.

----------------------------------------
Feature #4339: Record last run status on the node
https://projects.puppetlabs.com/issues/4339

Author: R.I. Pienaar
Status: Accepted
Priority: Normal
Assignee: 
Category: reports
Target version: Statler
Affected Puppet version: 2.6.0
Keywords: 
Branch: https://github.com/masterzen/puppet/tree/feature/master/4339


It would be helpful for monitoring if the status of the last run from either a 
daemonized puppetd or one from --test etc could be recorded in $vardir 
somewhere.

The whole report would be too big to parse regularly from nagios so maybe a 
smaller structured yaml file with the information that --summarize would show.  
This way we could easily monitor the detailed status of our node runs in a way 
that isnt very resource intensive or requiring extra tools like dashboards - 
just generally tighter integration with our existing toolset.

Additionally it would be helpful if the reports could be written on the nodes 
as well as to the network.


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://projects.puppetlabs.com/my/account

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en.

Reply via email to