5.3.6. HOWTO Enable Client Reporting¶
Puppet has the ability to send run status reports back to the server at the conclusion of each client run.
SIMP natively supports the store (default) and puppetdb report storage endpoints and can be configured as shown below.
188.8.131.52. Enable Client Reporting¶
Set the following in Hiera to enable client reporting:
--- pupmod::report: true
Once puppet applies this setting, clients will start sending reports to the server at the conclusion of each puppet run.
184.108.40.206. Filesystem Reports¶
By default, the puppet sever will enable the store reports target which will store the client reports on the local filesystem.
To view the raw reports, you can navigate to the directory output by
puppet config print reportdir.
If the system has been set up for puppetdb reports and you need to change it back to store, set the following in Hiera:
--- puppetdb::master::config::manage_report_processor: true puppetdb::master::config::enable_reports: false
220.127.116.11. PuppetDB Reports¶
Prior to proceeding, you should read HOWTO Enable PuppetDB if you have not already enabled puppetdb.
If you want to use a GUI application like Puppetboard to connect to puppetdb for reports, then you will need to ensure that the reports are being sent to puppetdb by the server.
To do this, set the following in Hiera:
--- puppetdb::master::config::manage_report_processor: true puppetdb::master::config::enable_reports: true
18.104.22.168. CLI Reporting¶
You can use the PuppetDB API to get node reporting using curl or any other application that connect to a web endpoint and process JSON output.
SIMP provides a tool called puppetlast that can read from both the PuppetDB API as well as the locally stored YAML reports for a simple view of your environment.
The puppetlast command is provided by the simp-utils RPM.