--- title: "Wolverine embraces Observability" url: https://daily.dev/posts/wolverine-embraces-observability-3oikve4ic source_url: https://timdeschryver.dev/blog/wolverine-embraces-observability type: article source: "Tim Deschryver" author: "Tim Deschryver" published: 2026-05-31T07:47:20.028Z updated: 2026-06-01T04:02:13.898Z tags: ["devops", ".net", "observability", "opentelemetry"] reading_time: 6 upvotes: 0 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Wolverine embraces Observability **[Tim Deschryver](https://daily.dev/sources/timdeschryver)** · [@timdeschryver](https://daily.dev/timdeschryver) · 6 min read · 0 upvotes · 0 comments ## Summary Wolverine, a .NET messaging library, has built-in OpenTelemetry support that can be enabled with just two lines of configuration. Adding `AddSource` enables distributed tracing that visualizes the full lifecycle of messages including retries and dead-letter queue events. Adding `AddMeter` enables metrics like success/failure counters. Both work without modifying application code and are compatible with any OTel-compatible backend such as Azure Application Insights or Honeycomb. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Use OpenTelemetry with Observability Pipelines for vendor-neutral log collection and cost control](https://daily.dev/posts/use-opentelemetry-with-observability-pipelines-for-vendor-neutral-log-collection-and-cost-control-3av2frw5s) · Datadog · 1 upvotes · 0 comments --- Tags: [#devops](https://daily.dev/tags/devops), [#.net](https://daily.dev/tags/.net), [#observability](https://daily.dev/tags/observability), [#opentelemetry](https://daily.dev/tags/opentelemetry) [View this post on daily.dev](https://daily.dev/posts/wolverine-embraces-observability-3oikve4ic)