Viewing Reports and Inventory Data
A newer version is available; see the version menu above for details.
When nodes fetch their configurations from the puppet master, they send back inventory data and a report of their run. These end up in the console, where you can view them in that node’s detail page.
Depending on how its last Puppet run went, every node is in one of six states. Each state is indicated by a specific color in graphs and the node state summary, and by an icon beside the report or the node name in a report list or node list view.
- Unresponsive: The node hasn’t reported to the puppet master recently; something may be wrong. The cutoff for considering a node unresponsive defaults to one hour, and can be configured in
no_longer_reporting_cutoffsetting. Represented by dark grey text. This state has no icon; the node retains whatever icon the last report used.
- Failed: During its last Puppet run, this node encountered some error from which it couldn’t recover. Something is probably wrong, and investigation is recommended. Represented by red text or the failed icon.
- No-op: During its last Puppet run, this node would have made changes, but since it was either running in no-op mode or found a discrepancy in a resource whose
noopmetaparameter was set to
true, it simulated the changes instead of enforcing them. See the node’s last report for more details. Represented by orange text or the pending icon.
- Changed: This node’s last Puppet run was successful, and changes were made to bring the node into compliance. Represented by blue text or the changed icon.
- Unchanged: This node’s last Puppet run was successful, and it was fully compliant; no changes were necessary. Represented by green text or the unchanged icon.
- Unreported: Although Dashboard is aware of this node’s existence, it has never submitted a Puppet report. It may be a newly-commissioned node, it may have never come online, or its copy of Puppet may not be configured correctly. Represented by light grey text or the error icon.
Each node detail page has a pair of graphs: a histogram showing the number of runs per day and the results of those runs, and a line chart tracking how long each run took. (Run status histograms also appear on class detail pages, group detail pages, and last-run-status pages.)
The daily run status histogram is broken down with the same colors that indicate run status in the console’s sidebar: red for failed runs, orange for pending runs (where a change would have been made, but the resource to be changed was marked as no-op), blue for successful runs where changes were made, and green for successful runs that did nothing.
The run-time chart graphs how long each of the last 30 Puppet runs took to complete. A longer run usually means changes were made, but could also indicate heavy server load or some other circumstance.
Each node page has a short list of recent reports, with a More button at the bottom for viewing older reports:
Each report represents a single Puppet run. Clicking a report will take you to a tabbed view that splits the report up into metrics, log, and events.
Metrics is a rough summary of what happened during the run, with resource totals and the time spent retrieving the configuration and acting on each resource type.
Log is a table of all the messages logged during the run.
Events is a list of the resources the run managed, sorted by whether any changes were made. You can click on a changed resource to see which attributes were modified.
Viewing Inventory Data
Each node’s page has a section called inventory. This section contains all of the fact values reported by the node on its most recent run.
Facts include things like the operating system (
operatingsystem), the amount of memory (
memorytotal), and the primary IP address (
ipaddress). You can also add arbitrary custom facts to your Puppet modules, and they too will show up in the inventory.
The facts you see in the inventory can be useful when filtering nodes in the live management page.