The Puppet Labs Issue Tracker has Moved: https://tickets.puppetlabs.com

Feature #2760

Clients should provide a direct interface to reports

Added by Luke Kanies over 4 years ago. Updated about 3 years ago.

Status:AcceptedStart date:10/29/2009
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:agent
Target version:3.x
Affected Puppet version:0.25.1 Branch:
Keywords:

We've Moved!

Ticket tracking is now hosted in JIRA: https://tickets.puppetlabs.com

This ticket may be automatically exported to the PUP project on JIRA using the button below:


Description

If software is calling Puppet, it is currently difficult for that software to figure out what has happened in a Puppet run.

It should be possible to have the report provided on stdout or some equivalent, in such a way that the caller can easily figure out exactly what happened.

For this to be any use, #2759 needs to also be included.


Related issues

Related to Puppet - Feature #630: Fine-grained reporting should be added. Duplicate
Related to Puppet - Feature #2759: Reports should provide structured data on events Closed 10/29/2009
Related to Puppet - Feature #5288: Change the default of report to true Closed 11/13/2010

History

#1 Updated by Luke Kanies over 4 years ago

  • Priority changed from Normal to High

#2 Updated by Luke Kanies about 4 years ago

  • Assignee set to Luke Kanies

#3 Updated by Luke Kanies about 4 years ago

Anyone have any opinion on how this should be implemented?

I’m thinking some combination of a —show-report flag on the client, and/or storing the most recent report on the client.

Just the latter would be a good start, I think, but not quite there.

#4 Updated by James Turnbull about 4 years ago

  • Status changed from Accepted to Needs Decision

I think the proposed approach would work as a first cut.

#5 Updated by Jesse Wolfe about 4 years ago

  • Priority changed from High to Normal
  • Target version changed from 2.6.0 to 52

#6 Updated by Peter Meier almost 4 years ago

There should definitely be a way to store reports on the client!

#7 Updated by Luke Kanies almost 4 years ago

  • Status changed from Needs Decision to Accepted
  • Assignee deleted (Luke Kanies)
  • Target version changed from 52 to 2.7.x

I figure just starting by storing the latest report on the client is good enough.

#8 Updated by Nigel Kersten about 3 years ago

  • Target version changed from 2.7.x to 3.x

#9 Updated by Luke Kanies about 3 years ago

Any objections to always storing the most recent report on disk?

I think this would be useful for multiple purposes.

#10 Updated by R.I. Pienaar about 3 years ago

atm reports are already stored on the client disk but only when reporting is enabled

#11 Updated by Luke Kanies about 3 years ago

Where does the report get stored?

#12 Updated by Luke Kanies about 3 years ago

And now that reporting is enabled by default, this should be better, at least.

#13 Updated by R.I. Pienaar about 3 years ago

Where lastrunreport points to which is $statedir/last_run_report.yaml and also pretty awesome from quick feedback is last_run_summary.yaml which is always written and just have a summary – more or less the metrics in report, really nice for quickly figuring out what happens.

Also available in: Atom PDF