Basic knowledge of monitoring, networking, and containers is useful but is not mandatory.

All the test environments were validated using macOS and Linux, while enforcing specific software versions for added compatibility, so those are the best candidates to guarantee you won't run into issues. Chapter 3, Setting Up a Test Environment, provides all the technical information on this subject.

Decent internet connectivity is required to download the software dependencies, as is a modern browser to ensure access to all the web interfaces presented in the book.

You can download the example code files for this book from your account at www.packt.com. If you purchased this book elsewhere, you can visit www.packtpub.com/support and register to have the files emailed directly to you.

You can download the code files by following these steps:

1. Log in or register at www.packt.com.
2. Select the Support tab.
3. Click on Code Downloads.
4. Enter the name of the book in the Search box and follow the onscreen instructions.

Once the file is downloaded, please make sure that you unzip or extract the folder using the latest version of:

• WinRAR/7-Zip for Windows
• Zipeg/iZip/UnRarX for Mac
• 7-Zip/PeaZip for Linux

The code bundle for the book is also hosted on GitHub at https://github.com/PacktPublishing/Hands-On-Infrastructure-Monitoring-with-Prometheus. In case there's an update to the code, it will be updated on the existing GitHub repository.

We also have other code bundles from our rich catalog of books and videos available at https://github.com/PacktPublishing/. Check them out!

We also provide a PDF file that has color images of the screenshots/diagrams used in this book. You can download it here: https://www.packtpub.com/sites/default/files/downloads/9781789612349_ColorImages.pdf.

There are a number of text conventions used throughout this book.

CodeInText: Indicates code words in text, database table names, folder names, filenames, file extensions, pathnames, dummy URLs, user input, and Twitter handles. Here is an example: "Now, you can run vagrant status."

A block of code is set as follows:

 annotations:
     description: "Node exporter {{ .Labels.instance }} is down."
     link: "https://example.com"

When we wish to draw your attention to a particular part of a code block, the relevant lines or items are set in bold:

 annotations:
     description: "Node exporter {{ .Labels.instance }} is down."
     link: "https://example.com"

Any command-line input or output is written as follows:

vagrant up

Bold: Indicates a new term, an important word, or words that you see onscreen. For example, words in menus or dialog boxes appear in the text like this. Here is an example: "You can find this page by going into Status | Rules on the top bar."