Sarvalekha / Developer tools & services
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. No supported release or subscription is established.
Implemented development capabilities
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.
The desktop Viewer and VS Code webview inspect native logs, exact catalogs, typed fields and trusted source mappings. Local searches cover loaded records.
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.
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.
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.
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.
Know the boundaries
Part of Diagnostics
The SDK provides the C++ producer foundation, automatic catalog generation and reference decoding. It keeps its developer identity as a Diagnostics component. The full product decoder adds crash and diagnostic inspection beyond ordinary SDK decoding.
Read the SDK scope notesA place in the wider picture
What comes next
Actual interfaces · Provider-generated example logs
These are actual development interfaces. Cloud UI shows a local server, and Extension shows the production webview renderer through its test bridge. Neither picture establishes a hosted service or installed extension qualification.
Keep evidence deliberate
Automatically generated catalogs separate static message descriptions from the application's recorded events. Provider verification checks removal of logging-only metadata from the final image for the selected build; unrelated strings, symbols and runtime values are outside that claim.
Developers explicitly classify sensitive fields and can redact a selected field before recording. That does not sanitize an entire process dump, discover all PII, or enforce geographic boundaries. Catalogs, source, symbols, raw export and model disclosure need their own permissions.
Explore compliance and data residencyLocal and server development profiles
Native artifacts and matching catalogs are the current authority. Database-backed metadata is a possible extension, not a requirement for today's native profile.
Read available logs and supported retained crash evidence using the exact catalog and native backend. Source navigation needs trusted mappings.
The current Windows x64 development server accepts completed files and supports bounded search and export. Scoped certificates and a provisioned owner session are distinct from federated team identity.
Hosted availability, complete delivery and acquisition qualification, live tail, distributed queries, and broader identity integration remain unfinished.
Before an evaluation
No. Local investigation uses available native logs and matching catalogs. Supported dump/core recovery uses the native full-product backend. This does not promise an unrestricted air-gapped distribution workflow.
No. Recovery can reveal committed events retained in captured logger memory. Uncaptured or overwritten information cannot be recreated, and evidence gaps remain important.
No generally available hosted service is established. The Cloud UI screenshot is an actual local server development interface.
Start with one application
Record your platform, build profile, representative workload, privacy boundaries and success criteria. The downloadable checklist prepares your notes; it does not submit an inquiry.
