Errata

... called the RED method, for Requests, Errors, and Duration.

should be:

... called the RED method, for Rate, Errors, and Duration.

Tom Wilkie who has popularized RED Method said "What is RED Method" as follows in his talk at GrafanaCon EU 2018:

- Rate (the number of requests per second)
- Errors (the number of those requests that are failing)
- Duration (the amount of time those requests take)

https://grafana.com/blog/2018/08/02/the-red-method-how-to-instrument-your-services/

escaping{foo="newline \n backslash \\ double quote \" "} 1

should be:

escaping{foo="newline \\n backslash \\ double quote \" "} 1

"\n" in the value of the foo label should be escaped.

... would be sum by (version)(python_version).

should be:

... would be sum by (version)(python_info).

Out of the box, Prometheus 2.2.1 has support for Azure, Consul, DNS, EC2, OpenStack, File, Kubernetes, Marathon, Nerve, Serverset, and Triton service discovery...

It seems that "GCE" service discovery is missing in supported list.

..., puts the replacement value metrics in the team label.

should be:

..., puts the replacement value monitor in the team label.

- source_labels: [__meta_consul_tag]

should be:

- source_labels: [__meta_consul_tags]

While we already saw version 0.6.0 of the Consul exporter in “Consul” on page 169, ...
*1 These metrics will likely be in the 0.7.0 version of the Consul exporter.

should be:

While we already saw version 0.3.0 of the Consul exporter in “Consul” on page 169, ...
*1 These metrics will likely be in the 0.4.0 version of the Consul exporter.

In "Consul" on page 169, Consul exporter 0.3.0 is used.

To be more precise, at least one of the matchers in a selector must not match the
empty string. So {foo=""}, {foo!=""}, and {foo=~".*"} will return an error, while
{foo="",bar="x"} or {foo=~".+"} are permitted.

should be

To be more precise, at least one of the matchers in a selector must not match the
empty string. So {foo=""} and {foo=~".*"} will return an error, while
{foo!=""}, {foo="",bar="x"} or {foo=~".+"} are permitted.

Note from the Author or Editor:
{foo!=""} should be in the permitted list in the chapter 13 Matchers section.

avg without(instance)(0.5, rate(process_cpu_seconds_total[5m]))

should be:

avg without(instance)(rate(process_cpu_seconds_total[5m]))

deriv(node_filesystem_free_bytes{job="node"}[1h]) * 4 * 3600
+
node_filesystem_free_bytes{job="node"}[1h]


The 'deriv' function returns an instant vector while the second clause is a range vector. Correct expression should be:

deriv(node_filesystem_free_bytes{job="node"}[1h]) * 4 * 3600
+
node_filesystem_free_bytes{job="node"}

Note from the Author or Editor:
Fix is as stated.

`hour() > 9 < 17` should be `hour() >= 9 < 17`.

It is not correct to write "This alert will only fire from 9 a.m. to 5 p.m." about `hour() > 9 < 17`. This alert would trigger from 10 a.m, as the value of `hour()` will be 9 from 9:00:00.000 until 9:59:59.999.

I think short explanation of what I outlined above would be valuable, as this is something I encounter in alerting rules very often.

Note from the Author or Editor:
Indeed, in Chapter 18 that should be >= 9, and for consistency it should also be changed in Chapter 15.

`prometheus_rule_group_last_duration_second` should be `prometheus_rule_group_last_duration_seconds`.

The example describes a way to compute the number of 9s of successes of an API endpoint as follows:

log10(
1 - (
sum without(instance)(rate(requests_failed_total[1h]))
/
sum without(instance)(rate(requests_total[1h]))
)
) * -1

I believe this is incorrect. The correct formula should be:

log10(
sum without(instance)(rate(requests_failed_total[1h]))
/
sum without(instance)(rate(requests_total[1h]))
) * -1

Note from the Author or Editor:
Thanks, you are correct.

In this paragraph, there is an incorrect hyphen in the words "check-metrics". It should read simply "check metrics" (no quotes, remove the hyphen)

Check Metrics
Prometheus 2.0 uses a custom parser for efficiency. So just because a /metrics can be scraped doesn’t mean that the metrics are compliant with the format. Promtool is a utility included with Prometheus that among other things can verify that your metric output is valid and perform lint checks.
curl http localhost:8000/metrics | promtool check-metrics

Brazil, Brian. Prometheus: Up & Running . O'Reilly Media. Kindle Edition.

Note from the Author or Editor:
This changed from check-metrics to check metrics with Prometheus 2.0.0, so I've updated accordingly.