mirror of
https://github.com/badlogic/pi-mono.git
synced 2026-11-05 23:37:25 +00:00
- 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
2.2 KiB
2.2 KiB
Changelog
[Unreleased]
Breaking Changes
- Adapters must implement
TelemetrySpan.addLink(). Normalized span snapshots include carrier-shaped context and parent identities and ordered links. - Adapters with optional metric or propagation capabilities must carry them through
TelemetryContext.metricsandTelemetryContext.propagationon roots, spans, and extracted parents.
Added
- Opaque string-map carriers and optional
TelemetryPropagationinjection/extraction, with passive root fallback for absent or invalid carriers and sharedNOOP_TELEMETRY_PROPAGATION. - Initial
SpanOptions.linksand latespan.addLink()with context targets and optional attributes, including settled target spans and extracted remote parents. - Optional
TelemetryMetricscounters, up-down counters, and histograms with boundary hints and exemplar contexts, plus sharedNOOP_TELEMETRY_METRICSinstruments. - Optional context capability members, populated by the no-op and in-memory adapters and checked by adapter conformance.
NOOP_TELEMETRY_CONTEXTis typed asTelemetrySpan, matching the shared inert span it provides.- Metric schema definitions and
createTypedMetrics()with exact instrument names, kinds, and required/optional low-cardinality attributes. - In-memory propagation across processes, link and measurement snapshots, and adapter conformance cases for propagation, links, and optional metrics.
[1.3.0] - 2026-10-15
[1.2.0] - 2026-10-12
[1.1.0] - 2026-10-07
[1.0.4] - 2026-10-05
[1.0.3] - 2026-10-05
[1.0.2] - 2026-10-04
[1.0.1] - 2026-10-03
[1.0.0] - 2026-10-01
[0.99.2] - 2026-09-30
[0.99.1] - 2026-09-29
[0.99.0] - 2026-09-29
[0.87.1] - 2026-09-22
[0.87.0] - 2026-09-21
[0.86.1] - 2026-09-20
[0.86.0] - 2026-09-19
[0.85.1] - 2026-09-05
[0.85.0] - 2026-09-04
[0.84.4] - 2026-08-28
[0.84.3] - 2026-08-24
[0.84.2] - 2026-08-14
[0.84.1] - 2026-08-07
[0.84.0] - 2026-08-06
Added
- Added the callback-based telemetry context contract, shared no-op context, deterministic in-memory reference adapter, reusable adapter conformance suite, typed serializable schema utilities, and multi-schema typed span starters with explicit child propagation.