@cellkit/traces
v0.1.0-rc.0
Published
Traces capability for Cellkit.
Readme
kind: cell-reference summary: Explain where time goes and how related work connects.
Traces
Responsibility
Traces follows an operation through asynchronous work and across service boundaries, helping explain delays and failures.
Use it when a request passes through several cells and you need to understand the complete path.
Contracts
Create spans around meaningful operations and carry their context to related work. Application results remain intact when telemetry is dropped. See the annotated Traces contract.
Providers
Keep traces locally during development or send them to a shared collector for investigation across services.
Dependencies
No other cell is required. Log can use trace context to connect individual events to the same operation.
Metadata
Traces are diagnostic output, not business records. Local retention is bounded.
Configuration
Choose where traces go, how much work to sample, and how much output to retain. Settings and defaults are in the configuration schema.
Observability
Inspect completed work, ongoing spans, and dropped or failed exports to assess diagnostic coverage.
Validation
Use the foundation tutorial for a working composition. Technical detail links the focused verification.
