What problem does it solve?
Observability establishes a clear separation between local diagnostic logs and telemetry to prevent accidental exposure of user data while providing actionable analytics and startup performance insights. It prevents PII leakage to analytics, ensures consistent token cost accounting, and adds lightweight profiling so engineers can pinpoint import and initialization regressions.
Core Features & Use Cases
- Local structured debugging using a local-only debug logger for rich context that never goes to telemetry.
- PII-safe telemetry events via typed analytics metadata and event naming conventions for cross-boundary operations.
- Startup profiling and token cost tracking with checkpoint timers and a shared cost accumulator for UI and internal policies.
- Use Case: Instrument a new tool to emit a PII-safe completion event, write detailed error traces only to local logs, and add profile checkpoints around initialization phases.
Quick Start
Replace console.log calls with the local debug logger, add PII-safe analytics events for operation outcomes, and insert profileCheckpoint markers to measure startup timing.
