Book Image

Puppet 5 Essentials - Third Edition

By : Martin Alfke, Felix Frank
Book Image

Puppet 5 Essentials - Third Edition

By: Martin Alfke, Felix Frank

Overview of this book

Puppet is a configuration management tool that allows you to automate all your IT configurations, giving you control over what you do to each Puppet Agent in a network, and when and how you do it. In this age of digital delivery and ubiquitous Internet presence, it's becoming increasingly important to implement scaleable and portable solutions, not only in terms of software, but also the system that runs it. This book gets you started quickly with Puppet and its tools in the right way. It highlights improvements in Puppet and provides solutions for upgrading. It starts with a quick introduction to Puppet in order to quickly get your IT automation platform in place. Then you learn about the Puppet Agent and its installation and configuration along with Puppet Server and its scaling options. The book adopts an innovative structure and approach, and Puppet is explained with flexible use cases that empower you to manage complex infrastructures easily. Finally, the book will take readers through Puppet and its companion tools such as Facter, Hiera, and R10k and how to make use of tool chains.
Table of Contents (10 chapters)

Using Puppet 5 server metrics

With Puppetserver Version 5 the former Puppet Enterprise only metrics system has been ported to Puppet Open Source.

The metrics system allows you to read internal information like compile times, status of file serving and function runtimes from a JMX console or to push the data to a graphite system.

Enabling the metrics system is straightforward by editing the puppet server metrics.conf file located at /etc/puppetlabs/puppetserver/conf.d/metrics.conf.

There are three important settings. At the metrics.server-id one can specify an ID which is later used in the Grafana dashboard. The metrics.registry.puppetserver.reporters.graphite.enabled value must be set to true and the metrics.reporters.graphite hash must mention the graphite hostname and port and the update interval setting:

# settings related to metrics
metrics: {
# a server id that will be used...