add-telemetry

To add structured telemetry events to a Warp feature, define a feature-specific TelemetryEvent enum, implement the TelemetryEvent trait, register the event, and emit telemetry using send_telemetry_from_ctx! or send_telemetry_from_app_ctx! macros.

The best way to measure product metrics without unstructured logging is using feature-specific TelemetryEvent enums. This structured pattern ensures you can observe Warp feature behavior in production while maintaining user privacy.

The TelemetryEvent trait works by requiring implementations for name, payload, description, enablement_state, contains_ugc, and event_descs fields. These define the structured telemetry event payload emitted from Warp modules.

You can use send_telemetry_from_app_ctx! to emit telemetry from application contexts, while send_telemetry_from_ctx! is used for standard contexts. Choosing between them depends on the specific context available in your Warp code.

Adding telemetry to Warp features does not require external dependencies. The instrumentation process relies entirely on defining TelemetryEvent enums and implementing the TelemetryEvent trait within your existing Rust codebase.

You should instrument Warp code with structured telemetry events when adding new features, diagnosing production issues, or quantifying product metrics. This approach replaces global logging with targeted, feature-specific observability.