Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Puppet Reporting and Monitoring

You're reading from   Puppet Reporting and Monitoring Create insightful reports for your server infrastructure using Puppet

Arrow left icon
Product type Paperback
Published in Jun 2014
Publisher
ISBN-13 9781783981427
Length 186 pages
Edition Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Michael Duffy Michael Duffy
Author Profile Icon Michael Duffy
Michael Duffy
Arrow right icon
View More author details
Toc

Table of Contents (16) Chapters Close

Puppet Reporting and Monitoring
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
1. Setting Up Puppet for Reporting 2. Viewing Data in Dashboards FREE CHAPTER 3. Introducing Report Processors 4. Creating Your Own Report Processor 5. Exploring PuppetDB 6. Retrieving Data with the PuppetDB API 7. Writing Custom Reports with PuppetDB 8. Creating Your Own Custom Dashboard 9. Looking Back and Looking Forward Index

Creating our dashboard


The first step to creating our own dashboard is to create our own layout of widgets to represent our data. We want to ensure that our prospective users have enough data to tell them how Puppet is doing in general, but we also don't want to overload them with data. We're going to introduce the following items onto our dashboard:

  • Number of hosts that have changed in the past 30 minutes

  • Number of hosts with pending changes in the past 30 minutes

  • Number of hosts that failed a resource in the past 30 minutes

  • List of nodes that have failed their Puppet run

  • Number of hosts Puppet is managing at this point in time

  • The total number of managed resources

  • The average number of managed resources per node

These details give our users a good amount of information without overloading them with extraneous detail; they should be able to very quickly see if everything is running fine. And if there are issues, such as a large amount of changed or failed hosts, they should be immediately apparent...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime