Working with individual reports

To examine a report in greater detail, click Report time. This opens a page that provides details for the node’s resources in three sections: Events, Log, and Metrics.

Events

The Events tab lists the events for each managed resource on the node, its status, whether correction was applied to the resource, and — if it changed — what it changed from and what it changed to. For example, a user or a file might change from absent to present.

To filter resources by event type, click Filter by event status and choose an event.

Sort resources by name or events by severity level, ascending or descending, by clicking the Resource or Events sorting controls.

To download the events data as a .csv file, click Export data. The filename is events-<node name>-<timestamp>.

Log

The Log tab lists errors, warnings, and notifications from the node's latest Puppet run.

Each message is assigned one of the following severity levels:

Standard Caution (yellow) Warning (red)
debug warning err
info alert emerg
notice   crit

To read the report chronologically, click the time sorting controls. To read it in order of issue severity, click the severity level sorting controls.

To download the log data as a .csv file, click Export data. The filename is log-<node name>-<timestamp>.

Metrics

The Metrics tab provides a summary of the key data from the node's latest Puppet run.

Metric Description
Report submitted by: The certname of the primary server that submitted the report to PuppetDB.
Puppet environment The environment assigned to the node.
Puppet run

  • The time that the Puppet run began

  • The time that the primary server submitted the catalog

  • The time that the Puppet run finished

  • The time PuppetDB received the report

  • The duration of the Puppet run

  • The length of time to retrieve the catalog

  • The length of time to apply the resources to the catalog

Catalog application Information about the catalog application that produces the report: the config version that Puppet uses to match a specific catalog for a node to a specific Puppet run, the catalog UUID that identifies the catalog used to generate a report during a Puppet run, and whether the Puppet run used a cached catalog.
Resources The total number of resources in the catalog.
Events A list of event types and the total count for each one.
Top resource types A list of the top resource types by time, in seconds, it took to be applied.