|
| 1 | +# v1.1.2 — OpenTelemetry |
| 2 | + |
| 3 | +**Release date:** 2026-06-09 |
| 4 | + |
| 5 | +## Summary |
| 6 | + |
| 7 | +OpenTelemetry instrumentation is now a first-class citizen in Ratatosk. This release introduces a new package `Ratatosk.Extensions.OpenTelemetry` along with comprehensive tracing and metrics support across the client facade, the connectors layer, and each individual channel connector. |
| 8 | + |
| 9 | +## New Package |
| 10 | + |
| 11 | +- **`Ratatosk.Extensions.OpenTelemetry`** — Convenience extensions for wiring up Ratatosk's telemetry sources into OpenTelemetry. Provides `AddRatatoskInstrumentation()` methods on `TracerProviderBuilder` and `MeterProviderBuilder`, and a `WithOpenTelemetry()` shortcut on `MessagingBuilder`. |
| 12 | + |
| 13 | +## Tracing (ActivitySources) |
| 14 | + |
| 15 | +- `Ratatosk.Client` — spans from the `IMessagingClient` facade covering send, receive, and status operations. |
| 16 | +- `Ratatosk.Connector.*` — per-connector spans (Twilio, SendGrid, Firebase, Facebook, Telegram) for fine-grained observability. |
| 17 | + |
| 18 | +## Metrics (Meters) |
| 19 | + |
| 20 | +- `Ratatosk.Client` — client-level counters and histograms (sent count, send duration, etc.). |
| 21 | +- `Ratatosk.Connector.*` — per-connector metrics (sent/received/failed counts, latency histograms). |
| 22 | +- New `ConnectorMeter` utility class for consistent meter naming across connectors. |
| 23 | + |
| 24 | +## New Request Classes |
| 25 | + |
| 26 | +- `SendRequest`, `ReceiveRequest`, `ReceiveStatusRequest`, `StatusRequest`, `BatchSendRequest` — strongly-typed request objects that carry operation parameters and telemetry context, enabling richer activity tracking. |
| 27 | + |
| 28 | +## Telemetry Infrastructure |
| 29 | + |
| 30 | +- `ClientTelemetry` — centralized telemetry coordination for the messaging client. |
| 31 | +- `ConnectorTelemetry` — per-connector telemetry implementation handling activities and metrics. |
| 32 | +- `MessagingSemanticConventions` — semantic convention constants for messaging attributes (messaging system, destination name, operation type, etc.). |
| 33 | +- `MessageContext` — context object for attaching trace information to message delivery. |
| 34 | + |
| 35 | +## Other |
| 36 | + |
| 37 | +- `ChannelConnectorBase` refactored to integrate with new telemetry infrastructure. |
| 38 | +- `MessagingClient` significantly refactored to leverage request classes and centralized telemetry. |
| 39 | +- New test projects: OpenTelemetry extension tests, connector telemetry tests. |
| 40 | +- New documentation: `docs/telemetry.md` — comprehensive telemetry guide. |
| 41 | +- Updated `ROADMAP.md` and `README.md`. |
| 42 | +- Solution file updated to include the new package. |
| 43 | + |
| 44 | +## Full Changelog |
| 45 | + |
| 46 | +``` |
| 47 | +eb200be feat: add OpenTelemetry support for tracing and metrics in Ratatosk framework |
| 48 | +ef97672 feat: add ConnectorMeter utility for consistent meter naming in telemetry |
| 49 | +88b3c91 feat: enhance telemetry metrics with message count and improve activity scope management |
| 50 | +7f1b2e4 feat: enhance telemetry with additional messaging attributes and improve activity tracking |
| 51 | +9a39bf6 feat: enhance telemetry metrics for message sending, receiving, and status queries |
| 52 | +4b9af24 feat: introduce request classes for messaging operations and enhance telemetry context handling |
| 53 | +``` |
| 54 | + |
| 55 | +**Files changed:** 36 files, +3,089 / −681 |
0 commit comments