Add domain-specific telemetry events to Warp features via TelemetryEvent trait.
npx skills add https://github.com/89jobrien/warpx --skill add-telemetry-89jobrien
Please help me install this Agent Skill. Skill: add-telemetry Source: https://github.com/89jobrien/warpx/tree/main/.agents/skills/add-telemetry Command: npx skills add https://github.com/89jobrien/warpx --skill add-telemetry-89jobrien
Warp telemetry integration guides how to instrument features, track user behavior, and measure metrics to improve development and debugging workflows.
Define a telemetry event enum for your feature and emit events at key milestones.
High-intent search queries and answers about installing and using this skill.
To add telemetry to Warp features, define a domain-specific telemetry event enum, implement the TelemetryEvent trait, and register the events in warp_core to instrument critical actions.
The TelemetryEvent trait is used to define domain-scoped telemetry events in Rust, allowing you to track user behavior and measure metrics for feature development and debugging workflows.
Configuring telemetry event payloads involves defining what data is sent within your event enums, enabling you to control when and what structured telemetry data is emitted around critical actions.
Yes, you can emit start and completion telemetry events around critical actions by placing event emission calls at key milestones within your Warp feature implementation for observability.
Yes, registering events in warp_core is required to properly instrument Warp features, ensuring your domain-specific telemetry events are recognized and emitted within the system.
fltmanScaffold new projects with CLAUDE.md and slash commands.
jacob-balslevDesign telemetry semantics mapping diagnostic questions to logs, metrics, traces, and events.
majiayu000Configure Prometheus metrics, OpenTelemetry traces, and JSON logs for LiteLLM gateway.
terzigoluInstrument Warp code with structured TelemetryEvent enums and trait implementations.
