Issue #5194 has been updated by Nigel Kersten.

Status changed from Needs design decision to Accepted
Assignee deleted (Nigel Kersten)


----------------------------------------
Feature #5194: Puppet event and report data should be normalized for end users
https://projects.puppetlabs.com/issues/5194

Author: Jeff McCune
Status: Accepted
Priority: Normal
Assignee: 
Category: 
Target version: 
Affected Puppet version: 
Keywords: report reports normalize event yaml
Branch: 


Overview
========

Many end users of puppet would like to work with the event information the 
puppet agent conveys to the puppet master using the current --report and 
--reports configuration option.  The information available to them currently is 
a raw serialization of the internal Puppet event objects.  As features are 
added to puppet over time, code re-factored, names changed, etc...  these 
changes are directly reflected in serialized data.

Some middleware layer could take the raw data from puppet and massage it into a 
normalized format providing consistency for the end user who needs to process 
this event data.

Use Case
========

Event data from puppet audit and agent runs should be normalized and well 
documented for easy consumption.


-- 
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