LogBrew.OpenTelemetry 0.1.1

LogBrew.OpenTelemetry

LogBrew.OpenTelemetry is an optional .NET integration for apps that already own an OpenTelemetry TracerProvider.

dotnet add package LogBrew
dotnet add package LogBrew.OpenTelemetry

using LogBrew;
using LogBrew.OpenTelemetry;
using OpenTelemetry;
using OpenTelemetry.Trace;
using System.Diagnostics;

var client = LogBrewClient.Create(
    Environment.GetEnvironmentVariable("LOGBREW_API_KEY") ?? "LOGBREW_API_KEY",
    "checkout-api",
    "1.0.0");

using var source = new ActivitySource("Checkout.Api", "1.0.0");
using var provider = Sdk.CreateTracerProviderBuilder()
    .AddSource("Checkout.Api")
    .AddLogBrew(client, options => options
        .WithServiceName("checkout-api")
        .WithServiceVersion("1.0.0")
        .WithDeploymentEnvironment("production"))
    .Build();

using (var activity = source.StartActivity("GET /checkout/{id}", ActivityKind.Server))
{
    activity?.SetTag("service.name", "checkout-api");
    activity?.SetTag("service.version", "1.0.0");
    activity?.SetTag("deployment.environment.name", "production");
    activity?.SetTag("telemetry.sdk.name", "opentelemetry");
    activity?.SetTag("http.request.method", "GET");
    activity?.SetTag("http.route", "/checkout/{id}");
    activity?.SetTag("http.response.status_code", 200);
}

using var exporterSource = new ActivitySource("Checkout.Exporter", "1.0.0");
using var exporter = new LogBrewOpenTelemetrySpanExporter(client, options => options
    .WithEventIdPrefix("checkout_otel_exporter")
    .WithServiceName("checkout-worker")
    .WithServiceVersion("1.0.0")
    .WithDeploymentEnvironment("staging"));
using var exportProcessor = new SimpleActivityExportProcessor(exporter);
using var exporterProvider = Sdk.CreateTracerProviderBuilder()
    .AddSource("Checkout.Exporter")
    .AddProcessor(exportProcessor)
    .Build();

using (var activity = exporterSource.StartActivity("POST /jobs/{id}", ActivityKind.Producer))
{
    activity?.SetTag("messaging.system", "memory");
    activity?.SetTag("messaging.operation", "publish");
}

Console.WriteLine(client.PreviewJson());

The integration adds LogBrewOpenTelemetrySpanProcessor, TracerProviderBuilder.AddLogBrew(...), and LogBrewOpenTelemetrySpanExporter for apps that prefer standard OpenTelemetry export processors such as SimpleActivityExportProcessor or BatchActivityExportProcessor. It captures ended, recorded W3C Activities through the same privacy-bounded LogBrewActivitySpanTelemetry path as the core SDK: trace/span IDs, parent span ID, sampled flag, duration, Activity name/kind/source, capped Activity event summaries, capped Activity link summaries, type-only OpenTelemetry exception event counts and types, escaped-exception error inference, explicit service context, safe service.name/service.version/deployment.environment.name/telemetry.sdk.name resource-convention tags, and a small allowlist of primitive semantic tags such as HTTP method/route/status, DB system/operation, messaging system/operation, and exception type. Each captured span also carries matching TelemetryContext trace identity plus typed service and deployment resource fields, so related LogBrew issues, logs, actions, and metrics can join the same trace without parsing flat metadata.

It does not create an OpenTelemetry provider, sampler, resource detector, instrumentation package, baggage/tracestate reader, global Activity listener, HTTP/database patch, arbitrary resource copier, payload/header/full-URL/query capture, exception message/stack capture, support ticket, OTLP forwarding path, or background upload path. Apps keep ownership of their OpenTelemetry pipeline and LogBrew only receives sanitized ended spans after the app opts in.

The packaged examples/OpenTelemetrySpanProcessorTelemetry.cs file shows copyable processor and exporter Activity-to-LogBrew span correlation setup with service context.