qyl 17.0.8

qyl

A local OpenTelemetry investigation stack for .NET. Run the collector on your own machine, instrument an application with one line, and read the traces, logs and metrics back through the collector API or MCP.

dotnet tool install --global qyl
qyl up

qyl up starts the collector API on 127.0.0.1:5100, diagnostics on :5200, OTLP ingestion on :4318 and :4317, and the runner API on :18889. Telemetry is stored under ~/.qyl/, never in the working directory. All five ports are checked up front, so a conflict fails the command instead of leaving a half-bound stack.

The runner observes itself the way every qyl process does: its own telemetry (service qyl-runner: health probes, orchestration logs, meters) goes to the diagnostics collector on :5200, next to the product collector's self-telemetry, and never into the product collector on :5100.

The tool and the collector it starts are framework-dependent .NET 10 applications: the qyl package selects the matching qyl.<rid> package for linux, macOS and Windows on x64 and arm64. Only the hosted collector container is NativeAOT.

Send telemetry to it

dotnet add package Qyl.Telemetry.Hosting

using Qyl;

builder.AddQyl();

AddQyl() activates the automatic instrumentation and exports traces, metrics and logs over OTLP, discovering the running collector on localhost. Environment variables alone export nothing; without the call there is no exporter to configure.

Read it back

• The collector API under /api/v1/: traces, logs, and metrics aggregated server-side into buckets by name, attribute matchers, time range and step.
• MCP, for an agent: qyl-mcp-server over stdio locally, or the hosted endpoint at https://mcp.qyl.at/mcp.

More

• Site and documentation: qyl.at
• Building an API that is instrumented from the first line: Qyl.Api.Sdk
• Source, samples and the release lines: github.com/ANcpLua/qyl
• Changes per version: CHANGELOG