Errata
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" Note from the Author or Editor: |
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. Note from the Author or Editor: |
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: |
Christopher Winter | Jul 26, 2022 | ||
Page Chapter 15 At multiple locations |
In several places, the SLO assessment units are counted as 43,800 units over 30 days. But if it is 1 unit per minute (some say 1,440 units per day), then 60 * 24 * 30 = 43,200 units seems correct. Note from the Author or Editor: |
Kazunori Otani | Aug 21, 2022 | ||
Page 171 2nd paragraph |
> The concepts explored in this chapter are most acutely felt when operating observability solutions at scale. Note from the Author or Editor: |
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. Note from the Author or Editor: |
Yoshi Yamaguchi | Aug 10, 2022 |