Forge Home

report_all_the_things

Dumps the complete Puppet report for processing by a report processor.

14,251 downloads

14,251 latest version

4.5 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Support the Puppet Community by contributing to this module

You are welcome to contribute to this module by suggesting new features, currency updates, or fixes. Every contribution is valuable to help ensure that the module remains compatible with the latest Puppet versions and continues to meet community needs. Complete the following steps:

  1. Review the module’s contribution guidelines and any licenses. Ensure that your planned contribution aligns with the author’s standards and any legal requirements.
  2. Fork the repository on GitHub, make changes on a branch of your fork, and submit a pull request. The pull request must clearly document your proposed change.

For questions about updating the module, contact the module’s author.

Version information

  • 0.1.0 (latest)
released Jul 13th 2015
This version is compatible with:
  • Puppet Enterprise 2023.8.x, 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 2.7.26

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'danzilio-report_all_the_things', '0.1.0'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add danzilio-report_all_the_things
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install danzilio-report_all_the_things --version 0.1.0

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.

Download

Documentation

danzilio/report_all_the_things — version 0.1.0 Jul 13th 2015

Puppet Forge Build Status Documentation Status

Are you a data nerd? Are you never able to get enough information out of your Puppet reports? Me too. There's a wealth of information in the Puppet reports. For large environments, this data is essential when trying to diagnose performance issues or detecting trends. Most report processors focus on small bits of information like the metrics, logs, or the summary sections. This is fine for some environments, but it's just not enough data for me! PuppetDB with dashboards like Puppetboard or Puppet Explorer are great for getting a quick glance at the status of your Puppet environment, but aren't powerful enough to get a good picture of the larger trends. I have big analytics platforms at my disposal and I want to use them. This is an attempt to solve this problem.

This module is really just a helper, not a report processor. This module provides some primitives for building report processors. The meat of this module is the Puppet::ReportAllTheThings::Helper module (ruby module, not Puppet module). This module contains a report_all_the_things method that takes a Puppet::Transaction::Report report object as an argument. This method calls the to_data_hash method on that report and iterates over the resulting data structure to ensure that all of the objects are serialized as regular hashes. The method will return a hash with all of the report data in it. You can then use this output to ship the data wherever you want.

I've written a report processor based on this module that ships reports to a Scribe log server (see: scribe_reporter).

Development

  1. Fork it
  2. Create a feature branch
  3. Write a failing test
  4. Write the code to make that test pass
  5. Refactor the code
  6. Submit a pull request

We politely request (demand) tests for all new features. Pull requests that contain new features without a test will not be considered. If you need help, just ask!