Qyl.Telemetry.Hosting 28.2.3

Qyl.Telemetry.Hosting

One-line telemetry for a .NET 10 application, NativeAOT included. builder.AddQyl() wires the OpenTelemetry SDK, activates qyl's automatic instrumentation, registers the activity sources and meters, and exports traces, metrics and logs over OTLP.

dotnet add package Qyl.Telemetry.Hosting

using Qyl;

builder.AddQyl();

That is the whole integration. There is no per-library enable step: every supported source is on unless its OTEL_DOTNET_AUTO_<ID>_INSTRUMENTATION_ENABLED toggle turns it off.

The package also carries SKILL.md, the guide for a coding agent working in the application: what AddQyl() already records, the generated span starters (Spans.Work, Spans.DbClient, ...), native typed attributes for business keys, RecordFailure, and the three things the compiler cannot check.

Your own spans

Use Qyl.Spans for the generated application scope, or register an application-owned ActivitySource with options.AdditionalSources.Add(sourceName):

using var span = Spans.Work("checkout");
span?.SetTag("checkout.order.id", orderId);
try
{
    await checkout.RunAsync(order);
}
catch (Exception exception)
{
    span?.RecordFailure(exception);
    throw;
}

Where the telemetry goes

AddQyl() exports to the first of these that is set:

1. OTEL_EXPORTER_OTLP_ENDPOINT — the standard variable, which also redirects every other OTLP exporter in the process.
2. QYL_ENDPOINT — an HTTP/protobuf collector for the qyl exporters alone. For gRPC, use the standard OTLP endpoint/protocol variables or set both CollectorEndpoint and CollectorProtocol.
3. A qyl collector discovered on localhost or the host qyl at 4318/4317, which is what qyl up from the qyl dotnet tool provides.

To see spans without any collector, add OpenTelemetry's console exporter through the tracing hook:

dotnet add package OpenTelemetry.Exporter.Console

builder.AddQyl(o => o.ConfigureTracing = t => t.AddConsoleExporter());

Options

AddQyl(o => ...) takes a QylTelemetryOptions. Every option has a zero-config default.

What it pulls in

This package depends on Qyl.Telemetry.AutoInstrumentation (the instrumentation runtime) and Qyl.Telemetry.AutoInstrumentation.Hosting (the listener bootstrap). An application that wires the OpenTelemetry SDK itself should reference Qyl.Telemetry.AutoInstrumentation.Hosting directly and register the Qyl.Telemetry.AutoInstrumentation source by hand, instead of this package.

Publishing with -p:PublishAot=true produces no trim, AOT or analyzer warning from this package.

More

• Which libraries are instrumented, the toggles, and the qyl attributes: repository README
• Every environment control with its evidence: coverage matrix
• Changes per version: CHANGELOG
• The product around it: qyl.at