- Add PuppetDB HA Metrics
- Add a script to zip up metrics for sharing
- Tidy script does not work without bzip (not installed on RHEL 7 by default)
- The tidy script now uses gzip which is more regularly available
- PR #45
- Tidy script would not exit on error
- Config file could change every run if you use puppetdb_query to find the hosts
- PuppetDB metrics could not be gathered by default in PE < 2016.4.0
- Allow connecting over http instead of https for PuppetDB
- PR #37
- In order to use pass
--no-ssland--metrics_portto the tk_metrics script
- No longer pass certificates to connect to metrics endpoint
- Tidy cron jobs would only delete metric files exactly retention_days away
- PE versions < 2016.2 now GET each metric individually instead of using a POST
- Allow not saving a metrics file
- Add a
--output-dirCLI argument to metrics scripts which tells the script where to save metrics output to. - If
--output-diris not specified then no file is saved
- Add a
- Metrics scripts print to STDOUT by default
- Use
--no-printto silence output to STDOUT
- Use
- Retrieve all additional metrics with one POST instead of multiple GETs
- Add a
--printcommand line argument to the metrics scripts- This allows for integrations with other tools that can read the output from stdout.
- PR #24
- Move script configuration into a YAML file
- Allow the metrics scripts to be stored as static files instead of templates
- PR #25
This is a major release because some of the PuppetDB metrics are renamed. For most users this update is only additive, however, if you are post processing the output of the module then you may need to update to the new names of the metrics.
- Rename some PuppetDB metrics
- command_processing_time is now global_processing_time
- command_processed is now global_processed
- replace_catalog_time is now storage_replace-catalog-time
- replace_facts_time is now storage_replace-facts-time
- store_report_time is now storage_store-report-time
- *_retry and *_retry-counts metrics are renamed to include mq_ at the front
- We now collect the output of the status endpoint for orchestrator
- We now collect HakariCP connection pooling metrics for PuppetDB
- We now collect the global metrics for PuppetDB
- We now collect the storage metrics for PuppetDB
- Each component now has its own class to allow customizing parameters per component
- Stagger compression of files between midnight and 3AM to prevent a CPU spike
- Every parameter, file name, etc... that contained puppet_server is rewritten
to puppetserver
- The existing parameters remain but are deprecated and should not be used
- Metric storage format is a single JSON blob instead of the exact output from whichever endpoint was queried
- Metrics gathering scripts are rewritten in ruby
- Metrics are now stored in one file per component
- PuppetDB metrics were previously stored with one file per metric
- Metrics are now stored in one directory per server
- PuppetDB metrics now gathers the status endpoint
- This is the preferred way to get the queue_depth metric
- Opt-in collection of ActiveMQ metrics is available
- Metrics are compressed daily for a 90% reduction in disk space
- Metrics are retained for 90 days by default instead of 3 days
- Retained metrics still take less space due to compression savings
- Metrics are retained for 90 days by default instead of 3 days
- The metrics tidy cron job previously ran every minute between 2-3 AM. It now runs just once at 2AM.