Errata

Observability Engineering

Errata for Observability Engineering

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. If the error was corrected in a later version or reprint the date of the correction will be displayed in the column titled "Date Corrected".

The following errata were submitted by our customers and approved as valid errors by the author or editor.

Color key: Serious technical mistake Minor technical mistake Language or formatting error Typo Question Note Update

Version Location Description Submitted By Date submitted Date corrected
Page Chap. 1
Unknown

"completely unique" should be "unique"

High cardinality means that the column contains a large percentage of completely unique values.

Note from the Author or Editor:
Thanks for reporting. "Completely unique" is redundant and "unique" will suffice. This should be fixed in the next release.

Anonymous  May 14, 2021  May 06, 2022
Page -
Chapter 1: What is Observability?,"Applying observability to software systems" section, 2nd paragraph , 2nd point

written: Understand any system state your application *many* have gotten itself into.
should be: Understand any system state your application *may* have gotten itself into.

it should be may instead of many.

Note from the Author or Editor:
Thanks, this was corrected in proofing and is fixed in our print edition.

Rajneesh Mehta  Oct 02, 2021  May 06, 2022
Page Page 66, Chapter 6, Instrumenting a Trace the Hard Way
3rd code sample

The name of the function in the code sample changes from `rootHandler` to `loginHandler`.

Note from the Author or Editor:
Confirmed. The code sample should use `rootHandler` and not `loginHandler`.

Christopher Winter  Jul 26, 2022 
Page 171
2nd paragraph

> The concepts explored in this chapter are most acutely felt when operating observability solutions at scale.

I believe "chapter" here should be "part".

Note from the Author or Editor:
Confirmed. Text should read: "The concepts explored in this part are most acutely felt when operating observability solutions at scale."

Yoshi Yamaguchi  Aug 08, 2022 
Page 232
Between Figure 18-1 and 18-2

> However, a complex setup can have a chain of receiver → buffer → receiver → buffer → exporter, as shown in Figure 18-2.

Second "receiver" should be "processor" according to the diagram in Figure 18-2.

Note from the Author or Editor:
This error should be corrected. Report is correct. The stated text should read:

"However, a complex setup can have a chain of receiver → buffer → processor → buffer → exporter, as shown in Figure 18-2."

Yoshi Yamaguchi  Aug 10, 2022