Repost.Client.OpenTelemetry 1.0.8

Repost.Client.OpenTelemetry

Thin OpenTelemetry glue for the Repost webhook publish client.

Repost.Client already emits spans and metrics through its own built-in ActivitySource and Meter (both named Repost.Client) — the platform-blessed layering, no vendored instrumentation. This package adds exactly two things on top:

1. One-call registration of that source and meter with the OpenTelemetry SDK, and
2. the frozen naming conventions as public constants, so dashboards, collector configs, and assertions reference the same strings the runtime emits.

No callbacks, no enrichment, no wrapping. Resource attribution stays with the standard SDK (ResourceBuilder.AddService); this package does not duplicate it.

Wiring — ASP.NET Core

using OpenTelemetry.Metrics;
using OpenTelemetry.Trace;
using Repost.Client.OpenTelemetry;

var builder = WebApplication.CreateBuilder(args);

builder.Services.AddRepostClient(builder.Configuration.GetSection("Repost"));
builder.Services.AddOpenTelemetry()
    .ConfigureResource(resource => resource.AddService("orders-api"))
    .WithTracing(tracing => tracing
        .AddAspNetCoreInstrumentation()
        .AddRepostInstrumentation()   // subscribes the "Repost.Client" ActivitySource
        .AddOtlpExporter())
    .WithMetrics(metrics => metrics
        .AddAspNetCoreInstrumentation()
        .AddRepostInstrumentation()   // subscribes the "Repost.Client" Meter
        .AddOtlpExporter());

An inbound request's span becomes the parent of the repost.send operation span: the runtime captures Activity.Current at send-admission time and parents explicitly (never ambient flow), and writes the W3C traceparent/tracestate request headers from the attempt span itself.

Wiring — console Worker

using OpenTelemetry;
using Repost.Client.OpenTelemetry;

using var tracerProvider = Sdk.CreateTracerProviderBuilder()
    .AddRepostInstrumentation()
    .AddOtlpExporter()
    .Build();
using var meterProvider = Sdk.CreateMeterProviderBuilder()
    .AddRepostInstrumentation()
    .AddOtlpExporter()
    .Build();

Naming conventions

Frozen in RepostOpenTelemetry as public constants:

Every operation produces one repost.send span with one repost.send.attempt span per transport attempt, parented on the operation span. Counters and histograms carry the low-cardinality outcome/delivery-state/status-class tags (error_code on failing outcomes only); the retries counter carries only error_code. Spans and measurements exist only when a listener is registered and RepostClientOptions.TelemetryEnabled is true (the default); set it to false to keep registration but silence emission.

Target frameworks

netstandard2.0, net472, net8.0 — the runtime's full matrix. The OpenTelemetry dependency is pinned centrally (Directory.Packages.props) at the lowest line clearing the repository's NuGetAudit gate.