otel_riverpod 0.3.0

OpenTelemetry instrumentation for `package:riverpod`. A ProviderObserver emitting short-lived spans for provider add, update, fail and dispose, so you can see your state graph.

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.

0.3.0 - 2026-10-11

Changed

• Requires dartastic_opentelemetry_api >=1.0.0-rc.4 <1.0.0-rc.5.
• Breaking: depends on dartastic_opentelemetry_api only, no longer on the SDK. The application chooses and initializes the OpenTelemetry SDK. Parameters and fields typed with SDK classes now use the API types (APITracer, APISpan, APILogger, ...); SDK instances are still accepted wherever an API type is expected.

0.2.0 - 2026-08-10

Added

• example/otel_riverpod_example.dart — a runnable, pub.dev-visible example driving every observer hook against a standard OTLP endpoint.

Removed

• The internal example_app/ (never shipped in the pub archive), superseded by example/.

0.1.0-beta.1 - 2026-05-16

Added

• OTelRiverpodObserver — a ProviderObserver that emits one short span per Riverpod observer callback (didAddProvider, didUpdateProvider, providerDidFail, didDisposeProvider). Each span carries the OTel semconv-style riverpod.* attributes (provider name / type / argument / family / auto-dispose flag, value type, plus mutation when present).
• RiverpodSemantics — typed attribute-key enum implementing OTelSemantic, package-local because OTel has no upstream semantic convention for state-management frameworks yet.
• providerDidFail is recorded via recordException then setStatus(SpanStatusCode.Error, ...), in OTel-spec order.
• recordValues flag (off by default) for capturing value content on add / update events; valueAttributeMaxLength for clipping.
• Targets riverpod: ^3.0.0. Works with both pure-Dart ProviderContainer and Flutter's ProviderScope.