Cohesive.Adapters.OpenTelemetry 0.1.0-alpha.120

Cohesive.Adapters.OpenTelemetry

Cohesive.Adapters.OpenTelemetry interprets Cohesive's existing ActivitySource and Meter scopes through native OpenTelemetry builders. Core packages continue to emit standard .NET diagnostics without depending on OpenTelemetry. This adapter does not define another telemetry model and it does not select exporters, collectors, sampling, resources, propagation, processors, logging, or hosting.

Install

dotnet add package Cohesive.Adapters.OpenTelemetry

Register core instrumentation

Register all core scopes in an existing host pipeline:

using Cohesive.Adapters.OpenTelemetry;

services.AddOpenTelemetry()
    .WithTracing(tracing => tracing
        .AddCohesiveCoreInstrumentation())
    .WithMetrics(metrics => metrics
        .AddCohesiveCoreInstrumentation());

Core is explicit in the aggregate name because other adapter and provider scopes remain host selections. Trace and metric registration project the same internal paired core-scope membership, and conformance tests require the aggregate to remain behaviorally equivalent to the block helpers composed together. Register a smaller surface when the host does not use every core block:

services.AddOpenTelemetry()
    .WithTracing(tracing => tracing
        .AddCohesiveExecutionInstrumentation()
        .AddCohesiveRelationsInstrumentation())
    .WithMetrics(metrics => metrics
        .AddCohesiveExecutionInstrumentation()
        .AddCohesiveRelationsInstrumentation());

The extension methods operate on TracerProviderBuilder and MeterProviderBuilder; the same methods work with Sdk.CreateTracerProviderBuilder() and Sdk.CreateMeterProviderBuilder() outside dependency injection.

Scope authority and parentage

The instrumentation owner remains the source of truth for every name, activity, instrument, unit, status, and tag. This package copies no scope names. Its internal collection-membership list pairs the public activity-source and meter constants owned by each block so trace and metric registration cannot drift independently.

Cohesive activities start beneath Activity.Current. In an ASP.NET host, the framework request activity is therefore the parent of logical Cohesive work. Provider SDK or HTTP activities started while a Cohesive activity is current are its children. Do not add a second wrapper activity around an already-instrumented provider call merely to measure the same interval.

Other adapter and provider scopes

The core-scope aggregate intentionally does not reference other adapter assemblies. A host registers only the adapters it selected, using the constants owned by those packages:

services.AddOpenTelemetry()
    .WithTracing(tracing => tracing
        .AddCohesiveCoreInstrumentation()
        .AddSource(CosmosRelationQueryTelemetry.InstrumentationName)
        .AddSource(CosmosClientFactory.OperationActivitySourceName))
    .WithMetrics(metrics => metrics
        .AddCohesiveCoreInstrumentation()
        .AddMeter(CosmosRelationQueryTelemetry.InstrumentationName));

The adapter deliberately does not offer typed helpers for these external scopes. Doing so here would pull every supported infrastructure adapter into one package; doing so in each adapter would make OpenTelemetry mandatory for all of that adapter's consumers. Hosts therefore use the selected package's compile-time constants with native AddSource and AddMeter calls.

Current adapter scopes are:

Attribute and metric safety

• Metric dimensions must remain closed, bounded, and low-cardinality. Use only dimensions documented by the owning telemetry contract.
• Exact request, process, attempt, generation, document, tenant, resource, payload, query, evidence, and fingerprint identities are trace-only unless the owner explicitly documents a bounded metric interpretation.
• Query text, payload content, credentials, authorization material, raw exception messages, and connection strings are prohibited by default. Enable a provider's sensitive-data option only through that provider's native configuration and only with an explicit data-handling decision.
• Static service, deployment, environment, region, and version attributes belong on the OpenTelemetry Resource, not on every activity or metric point.
• Missing telemetry is not success evidence. Sampling, export failure, process loss, and inactive listeners remain distinct from a measured successful operation.

Cohesive.ServiceLevels can later bind stable semantic operation identities to objectives and indicators. This package only makes runtime evidence collectible; it does not define objectives or evaluate compliance.

Service export conformance

The adapter tests invoke a real declared transition-backed service through a native OpenTelemetry provider and processor. Both successful and failed exporter responses preserve the successful commit and canonical trace fingerprint. Exported service evidence retains caller parentage and excludes fixture tenant, subject and business values from tags. These tests establish local SDK collection/export behavior; they do not establish remote collector delivery, retention or authorized inspection. Listener-owning tests share one collection because native diagnostic listeners are process-wide.

Service bindings also emit cohesive.execution.invocations (counter) and cohesive.execution.invocation.duration (seconds histogram) through the existing execution meter. These measure each service invocation boundary, including Process admission/result reads; they do not measure the entire asynchronous Process lifetime. Only the closed activity-family and outcome dimensions are attached. No service, tenant, entity or invocation identifiers become metric labels. Metrics are independent of trace sampling and retain best-effort listener-failure isolation. Existing activation histograms are authoritative status snapshots and are not interchangeable with invocation counts.