qyl 2.0.0

qyl

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

The latest public qyl release is 1.1.8; the main branch is the 2.0.0 source line. The site and documentation are at qyl.at. The other two hosted surfaces are endpoints rather than pages: https://api.qyl.at serves the collector read API and OTLP ingest under their route prefixes, and https://mcp.qyl.at/mcp is the MCP endpoint, which answers 401 to anything without an OAuth 2.1 bearer token.

Run the stack

dotnet tool install --global qyl
qyl up

qyl up starts the collector and its embedded dashboard 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.

Observe Codex workflows

qyl codex owns the Codex app-server connection so the workflow journal is factual rather than inferred from generic telemetry:

export QYL_API_KEY='your-qyl-ingest-key'
qyl codex --

It verifies the installed Codex app-server schema, starts an authenticated loopback server and the normal Codex TUI, and records immutable runs, attempts, collaboration, tools, content references, and controls. Uploads are idempotent. Network failures leave an encrypted spool under ~/.qyl/codex/ for retry instead of losing or rewriting events. The bundled Observe Graph plugin discovers the current run through the local qyl observer-bridge; that bridge is modern-only MCP 2026-07-28.

Send telemetry from an application

dotnet add package Qyl.Telemetry.Hosting

using Qyl;

builder.AddQyl();

AddQyl() is what wires the pipeline: it activates automatic instrumentation, registers the qyl activity sources and meters, and exports traces, metrics, and logs over OTLP — to OTEL_EXPORTER_OTLP_ENDPOINT when set, otherwise QYL_ENDPOINT, otherwise a collector discovered on localhost. Environment variables on their own export nothing; without the call there is no exporter to configure.

qyl stores and serves traces, logs, and metrics. Metric points land in a series index plus a point table, and are queried by metric name, attribute matchers, a time range, and a step — aggregated server-side into buckets, never returned as raw points. OTLP's summary point is the one shape qyl declines: its pre-computed quantiles cannot be re-aggregated over a window or merged across series, so it is reported back as a partial_success naming the instrument rather than stored unqueryable.

Artifacts and release lines

qyl is one dependency graph with several independently released packages. Each line carries its own version — the 1.0.0 launch is an event, not a number every package adopts. The versions below are the source and dependency lines targeted by main, not a claim that every target has already been published. Package registries are authoritative for public availability.

Qyl.Sdk and the Qyl.OpenTelemetry.* package IDs are retired. They stop at their last published versions and receive no further releases; the table above lists their successors.

Architecture

ARCHITECTURE-1.0.0.md is the normative document: component taxonomy, boundary law, the dependency-edge list, the generated loops, and the gates. docs/component-taxonomy.html is a view of the same content. On conflict the Markdown wins.

One graph, one truth, many artifacts.

Build and verify

Requires the .NET SDK pinned in global.json.

dotnet run --project eng/build/build.csproj -- Ci

Ci builds and tests the backend, builds and tests the dashboard, runs its Release-product Playwright smoke, verifies the generated contract package, and checks the collector semantic catalog.

License

MIT