next-observer 0.3.26 → 0.3.27

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/README.md +6 -0
  2. package/dist/ui/assets/index-CXUv4-u5.js +20 -0
  3. package/dist/ui/index.html +1 -1
  4. package/package.json +1 -1
  5. package/dist/ui/assets/index-BsgdkOcd.js +0 -20
package/README.md CHANGED
@@ -60,6 +60,12 @@ this call compares with the others of its kind.
60
60
 
61
61
  ![A trace with the critical path highlighted and a table of where the time went](https://raw.githubusercontent.com/ataztech910/nextjs-observe/master/docs/screenshots/trace.png)
62
62
 
63
+ A span can be fast, without an error, and still carry the wrong answer. When the app records its own verdict as a span
64
+ event — `integrity_check` with `ok`, `expected`, `actual` — the observer raises an anomaly on the first `ok: false` and the
65
+ trace says so:
66
+
67
+ ![A trace with a Wrong data banner: getProductById asked for 1 and got back 3](https://raw.githubusercontent.com/ataztech910/nextjs-observe/master/docs/screenshots/wrong-data.png)
68
+
63
69
  **One operation up close** — its latency distribution, and a note when the calls fall into two clearly separate speeds
64
70
  (a fast and a slow path, or the version before and after a deployment).
65
71