Development edition · 16 November 2026. Commands using repository paths, Make targets or sample projects require access to the Quinzee source checkout. No public installer is available. Examples use disposable local environments.
12. Telemetry and Azure monitoring
Platform diagnostics and Azure application monitoring are separate paths. The platform's per-host telemetry service captures bounded request events, metrics and correlated JSON logs. The monitoring modules accept application telemetry into independently scoped, persistent workspaces. Enabling one does not imply that every event is copied into the other.
Platform path
W3C version-00 trace context enters at host dispatch and is propagated explicitly through deployment jobs, engine mailboxes and application queue messages. Thread-local request binding is non-owning and restored by RAII; it cannot be implicitly used as asynchronous context. The .NET consumer retains producer links for leased work recovered after restart.
Native request history and export queues are bounded. Metrics use fixed categories; URLs, credentials, payloads, SQL parameters and trace IDs do not become metric labels. Optional provider gauges include bounded sampled queue counts and explicit truncation. Transport metrics describe actual parsed HTTP exchanges, while handler metrics describe module calls and prepared body bytes.
The native OTLP/HTTP JSON adapter uses existing Boost/OpenSSL facilities. A
worker performs verified HTTPS requests with cancellation/deadlines and bounded
responses. Delivery is best effort with explicit failure/drop accounting.
The private exchange coroutine's borrowed parameters are safe because the
synchronous post() scope drains the I/O loop before destroying them; this
narrow lifetime exception is documented at the declaration. The exporter is
destroyed before captured host/worker providers.
The fixed C++ mapping is an OTLP producer, not a general OpenTelemetry SDK. The .NET application uses official OpenTelemetry/Azure Monitor libraries; the Python helper uses a small bounded fixed-schema producer. Interoperability is checked against a real Collector and persisted Prometheus/Loki/Tempo data.
Azure-compatible path
log_analytics owns workspace resources and bounded row storage.
application_insights depends on that capability and owns components/ingestion.
ARM IDs and generated customer/App/instrumentation IDs remain stable across
redeployments. Component workspace bindings are immutable.
Ingestion normalizes the six supported envelope types, validates each item, batches atomic writes by workspace and reports partial acceptance/durable failure. The query evaluator implements only its documented, read-only pipeline; it has no external query engine or filesystem expressions. Component queries filter resource ID, workspace queries load only their workspace, and audiences separate ingestion/query/ARM. Full per-workspace RBAC is not implemented.
Use observability operations (source checkout required) for collector, TLS, retention and metric semantics; monitoring contracts (source checkout required) for APIs, limits, mappings and unsupported features; and the verification record (source checkout required) for failure-driven tests.