Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Hands-On Infrastructure Monitoring with Prometheus
  • Toc
  • feedback
Hands-On Infrastructure Monitoring with Prometheus

Hands-On Infrastructure Monitoring with Prometheus

By : Joel Bastos, Pedro Araújo
3.1 (7)
close
Hands-On Infrastructure Monitoring with Prometheus

Hands-On Infrastructure Monitoring with Prometheus

3.1 (7)
By: Joel Bastos, Pedro Araújo

Overview of this book

Prometheus is an open source monitoring system. It provides a modern time series database, a robust query language, several metric visualization possibilities, and a reliable alerting solution for traditional and cloud-native infrastructure. This book covers the fundamental concepts of monitoring and explores Prometheus architecture, its data model, and how metric aggregation works. Multiple test environments are included to help explore different configuration scenarios, such as the use of various exporters and integrations. You’ll delve into PromQL, supported by several examples, and then apply that knowledge to alerting and recording rules, as well as how to test them. After that, alert routing with Alertmanager and creating visualizations with Grafana is thoroughly covered. In addition, this book covers several service discovery mechanisms and even provides an example of how to create your own. Finally, you’ll learn about Prometheus federation, cross-sharding aggregation, and also long-term storage with the help of Thanos. By the end of this book, you’ll be able to implement and scale Prometheus as a full monitoring system on-premises, in cloud environments, in standalone instances, or using container orchestration with Kubernetes.
Table of Contents (21 chapters)
close
Free Chapter
1
Section 1: Introduction
5
Section 2: Getting Started with Prometheus
11
Section 3: Dashboards and Alerts
15
Section 4: Scalability, Resilience, and Maintainability

From logs to metrics

In a perfect world, all applications and services would have been properly instrumented and we would only be required to collect metrics to gain visibility. External exporters are a stop-gap approach that simplifies our work, but not every service exposes its internal state through a neat API. Older daemon software, such as Postfix or ntpd, makes use of logging to relay their inner workings. For these cases, we're left with two options: either instrument the service ourselves (which isn't possible for closed source software) or rely on logs to gather the metrics we require. The next topics go over the available options for extracting metrics from logs.

mtail

Developed by Google, mtail is a very...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete