Public product notes

Diagnostics, in context.

Native application logging and evidence-based diagnostics.

Under development — not releasedProduct overview

Purpose & status.

Follow native application events from capture to investigation. Compact binary logs, exact build catalogs and real viewers help engineers examine evidence while retaining its limits.

Under development — not released. These notes do not supply a supported installation, operational signup or subscription.

Capability scope.

Development implementation

Record compact, structured events

C++ calls record identifiers and bounded typed values. Automatically generated catalogs supply message formats and build identity during decoding; provider checks verify logging-only metadata removal.

Development implementation

Investigate through real viewers

The desktop Viewer and VS Code webview inspect native logs, exact catalogs, typed fields and trusted source mappings. Local searches cover loaded records.

Development implementation

Recover retained context

The full native decoder can recover committed events still present in supported Windows dumps and Linux cores. Missing, overwritten or uncaptured memory cannot be reconstructed.

Development implementation

Search on a configured local server

The Windows Helper can upload completed native files. A privately configured Windows x64 server supports bounded artifact search and export with scoped access. This is not a hosted service offer.

Development implementation

Keep AI investigation bounded

An optional development controller uses configured endpoints, read-only tools and separate evidence-disclosure permissions. Protocol fixtures do not qualify model accuracy or hosted privacy agreements.

Development implementation

Follow recorded trace context

Explicit trace/span identities and an opt-in trace-aware API connect recorded events. The static, field-free span lifecycle subset retains starts, ends, parentage, events, links and status. Complete distributed tracing remains unfinished.

Important limitations.

  • Under development, with no supported public product release or generally available hosted service. Preview labels identify implemented development capabilities.
  • Exact matching catalogs are required. Native capture, platform, delivery and resource qualification remain incomplete; logging is best-effort.
  • Explicit sensitive-field classification and redaction are not automatic PII discovery or whole-dump sanitization. Key-provider integration remains incomplete.
  • Partial trace correlation and static span lifecycle inspection do not establish complete distributed tracing. Server querying has bounded member size, record counts and coverage.
  • Lower CPU, memory, storage and I/O costs are design goals. Catalog separation does not establish universal overhead, measured savings, losslessness or availability guarantees.

Diagnostics component

Using the C++ SDK context.

The C++ SDK is the producer logging foundation and ordinary reference decoder. Customer headers require C++20; runtime and tools use C++23. The full product decoder and native Viewer add supported crash-log recovery and diagnostic inspection. Exact catalogs and compiler-derived evidence must match the selected build.

Local dump recovery needs the native backend; browser/WebAssembly recovery is unavailable. The current server and complete native Helper acquisition target Windows x64. macOS qualification and native Linux acquisition remain unfinished.

See actual Viewer interfaces