Issue #4712 has been updated by James Turnbull. Status changed from Unreviewed to Accepted Target version set to Statler Affected version set to 2.6.0
---------------------------------------- Bug #4712: Agent and master reports should be renamed to events http://projects.puppetlabs.com/issues/4712 Author: Jeff McCune Status: Accepted Priority: Normal Assignee: Category: reports Target version: Statler Affected version: 2.6.0 Keywords: reports report event rename Branch: Overview There is some confusion around the name "reports" as far as the puppet agent and puppet master are concerned. The information conveyed from the agent to the master at the end of a puppet run is not actually a human consumable report, but rather a log of events. As a result, please rename the report agent option to send_events and the reports master option to event_processors Background information Jeff said: >>> Essentially, we use the word "report" to mean two things in puppet and >>> when we've been saying "there _is_ better reporting in 2.6" we didn't >>> mean what everyone else thinks we meant. We actually mean "2.6 makes >>> it easier to create better reports, but they don't exist yet." Luke said: >> I agree. I've always mentally separated reporting from analytics, but I've >> never pushed such a separation into client terminology. >> >> Given this vagueness on the difference between data that the client produces >> and information that the dashboard displays, is there a clean way to >> differentiate them? We should probably rename the process of sending data >> from the client, since people intuitively think of the graphical aspects as >> 'reporting'. Jeff said: > I think the "stuff" puppetd collects and conveys to the master should > be called "events" rather than a "report" The dashboard or "event > processors" on the master should then compile "reports" to be consumed > by a person. The process would then be renamed "send_events" which is > an action with a verb and the configuration could be > --send_events=true rather than --report=true > > On the server side, we could rename the reports option to > "event_processors" so it would look like > --event_processors=store,log,rrdgraph > > An event processor may or may not produce a report. > Luke said: Interesting. It's not entirely correct, because more is sent than events, but I'm comfortable with that or a similar re-framing. Could you open a ticket for it? -- 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.
