Practical Monitoring

Errata for Practical Monitoring

Submit your own errata for this product.


The errata list is a list of errors and their corrections that were found after the product was released.

The following errata were submitted by our customers and have not yet been approved or disproved by the author or editor. They solely represent the opinion of the customer.


Color Key: Serious Technical Mistake Minor Technical Mistake Language or formatting error Typo Question Note Update



Version Location Description Submitted By Date Submitted
Printed Page 9
3rd paragraph

This is perhaps a debatable quibble, but the text says, "Remember, it's not ready for production until it's monitored." That was a bit distracting, as there'd been no prior statement to that effect. Perhaps a prior edit did, or perhaps the author felt it to be a common understanding. Given the introductory perspective of this first chapter, it's indeed a worthy assertion, so perhaps better wording might be "consider that" rather than "remember [that]". :-)

carehart  Sep 21, 2018 
Printed Page 18
1st line

"TSDB" is not defined until pg 19 but it would be better to define on first use

JP Vossen  Jan 09, 2019 
PDF Page 19
last paragraph

I'm reporting this on behalf of a reader of the Japanese edition who kindly reported this. The second sentence says "there would be 86400 datapoints for the past 24 hours of metrics" but the number of datapoints should be 1440 if metrics are collected every 60 seconds from a node (1 node * 60 times per hour * 24 hours = 1440).

Hayato Matsuura  Mar 30, 2019 
Printed Page 21
Last paragraph

On the section: Analytics and Reporting, second paragraph the books the following sentence: "One of the most common use cases here is determining and reporting on service-level-availability (SLA) of your applications and services. An SLA is an agreement between you and your customer..." SLA is more common the abbreviation for Service License Agreement and not Availability... Please check with the author!

Leandro Meinhardt  May 19, 2018 
Printed Page 57
3rd para

"KPIs" is used but not defined until the next section. Not a big deal, but better to define on first use.

JP Vossen  Jan 09, 2019 
Printed Page 75
third paragraph, third line

your apps have a ton of valuable information about their performance, many of which 'many' refers to the valuable information, not to your apps; it should probably be 'much'

Anonymous  Aug 31, 2018 
Printed Page 93
4th paragraph, last line

which I covered xref. I am pretty sure 'xref' is supposed to be a reference to another part of the book

Anonymous  Aug 31, 2018 
Printed Page 100
6th paragraph, 3rd line

strategies for fixing them, but \ the first I think the backslash should be removed.

Anonymous  Aug 31, 2018 
Printed Page 100, 110
various

I also noticed the existing unconfirmed errata for 100 extra "\" and 110 extra "=" markup.

JP Vossen  Jan 09, 2019 
Printed Page 105
6th line

magic - if: if run-backup.sh fails not clear why two ifs. this is minor, but reads more smoothly if 'if:' is removed

Anonymous  Aug 31, 2018 
Printed Page 108
2nd line

Why the standard OS metrics aren't as usual for alerts as you might think 'usual' should probably be 'useful'

Anonymous  Aug 31, 2018 
Printed Page 110
4th paragraph, 4th line

world such as =collectd=, but collectd is in the appropriate font, but I think the equals signs should be omitted.

Anonymous  Aug 31, 2018 
Printed Page 127
1st paragraph, 2nd line

that all nodes are both updating regularly and scans are both starting and finishing I think the first 'both' should be dropped.

Anonymous  Aug 31, 2018 
Printed Page 127
5th paragraph

a component direct hooks should add the word 'with' before 'direct'

Anonymous  Aug 31, 2018 
PDF Page 129
a quote from a Wikipedia page

The quote seems like it's from a Wikipedia page for McAfee but the page doesn't have the sentences. Should it be "Rootkit" instead of "McAfee"?

Anonymous  Sep 01, 2018