pi-mono/packages/telemetry/test
Mario Zechner 2ec55d808d
Some checks are pending
CI / build-check-test (push) Waiting to run
CI / mcp-conformance (push) Waiting to run
feat: Durable and pi-ai telemetry; Context.telemetry is always a span
- pi-ai: AI_TELEMETRY_SCHEMA; pi.ai.request and pi.ai.poll spans around Models requests via a lazyStream observer
  (no provider changes), first_chunk and block events (never per delta), usage/cost end attributes, provider_error
  status with a bounded message, aborted stays ok; duration, first-chunk, token and cost metrics; option renamed
  telemetryContext -> telemetry (a parent span)
- pi-telemetry: TelemetryContext carries readonly metrics and propagation capabilities on every span
- chord/context: Context.telemetry is always a TelemetrySpan (NOOP default); withTelemetry takes spans
- durable: DURABLE_TELEMETRY_SCHEMA; pi.durable.submit (inputs start their own trace linked to the caller) and
  pi.durable.phase spans for every task phase; stored carriers on submissions and tasks (TaskOptions.trace, links);
  entry, submission, checkpoint, replay and report events after commit; resumed tasks stay in their trace; phase
  duration, active task and report metrics; failed phases carry fixed categories with bounded messages
2026-10-19 06:26:02 +00:00
..
conformance.test.ts feat: telemetry propagation, span links and metrics; telemetry member in chord/context 2026-10-18 20:36:08 +00:00
metrics.test.ts feat: telemetry propagation, span links and metrics; telemetry member in chord/context 2026-10-18 20:36:08 +00:00
propagation-worker.ts feat: telemetry propagation, span links and metrics; telemetry member in chord/context 2026-10-18 20:36:08 +00:00
propagation.test.ts feat: telemetry propagation, span links and metrics; telemetry member in chord/context 2026-10-18 20:36:08 +00:00
telemetry.test.ts feat: Durable and pi-ai telemetry; Context.telemetry is always a span 2026-10-19 06:26:02 +00:00