@capxul/observability 3.1.0 → 4.0.0
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.
- package/README.md +7 -0
- package/dist/index.d.mts +642 -2
- package/dist/index.mjs +488 -4
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -53,6 +53,7 @@ client has no session recording manager.
|
|
|
53
53
|
|
|
54
54
|
```ts
|
|
55
55
|
import {
|
|
56
|
+
CAPXUL_OPERATIONS,
|
|
56
57
|
PostHogTelemetryAdapter,
|
|
57
58
|
TELEMETRY_EVENT_SCHEMAS,
|
|
58
59
|
initializeCapxulBrowserAnalytics,
|
|
@@ -63,6 +64,12 @@ import {
|
|
|
63
64
|
} from "@capxul/observability";
|
|
64
65
|
```
|
|
65
66
|
|
|
67
|
+
`CAPXUL_OPERATIONS` is the closed vocabulary for stable operations that cross
|
|
68
|
+
an error or observation boundary. Use its values in production code. Use
|
|
69
|
+
`normalizeCapxulOperation` at trust boundaries. Unknown input becomes
|
|
70
|
+
`"unknown"`. JSON-RPC methods, Convex function paths, event names, span names,
|
|
71
|
+
and error codes remain separate vocabularies.
|
|
72
|
+
|
|
66
73
|
Catalog presence is not delivery proof. Some financial-operations events are
|
|
67
74
|
explicit planned targets; `FINANCIAL_OPS_TARGET_TELEMETRY_PRODUCERS` records
|
|
68
75
|
which target events are not yet wired. Producer code and its tests are the
|