add-telemetry

Instrument Warp features with structured telemetry events via a TelemetryEvent trait.

Updated Apr 30, 2026

Search Tags:#observability #rust #instrumentation #telemetry #warp #telemetry-events

Ready to run

npx skills add https://github.com/lalaABC/waprcn --skill add-telemetry-lalaabc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: add-telemetry
Source: https://github.com/lalaABC/waprcn/tree/main/.agents/skills/add-telemetry
Command: npx skills add https://github.com/lalaABC/waprcn --skill add-telemetry-lalaabc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Instrument Warp features with structured telemetry to standardize how events are emitted, named, and observed across codebases.

Core Features & Use Cases

Define feature-scoped telemetry events by domain and implement the TelemetryEvent trait to encapsulate event name, payload, and enablement rules.
Register and expose events so they can be consumed by Warp's telemetry pipeline and analytics dashboards.
Send telemetry from code paths using the provided helpers, enabling consistent observability during development, debugging, and production monitoring.
Use cases include instrumenting feature lifecycle events, user actions, and system-state signals for proactive debugging and analytics.

Quick Start

Create a new telemetry event for your feature and wire it into the feature flow to start emitting events.

Frequently Asked Questions about add-telemetry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I instrument Rust features with structured telemetry events?▼

Instrument Rust features with structured telemetry by creating a TelemetryEvent enum, implementing the TelemetryEvent trait, and sending events from code paths using Warp's telemetry utilities.

What is the best way to standardize telemetry event naming across Rust modules?▼

Standardize telemetry event naming across Rust modules by applying feature-scoped telemetry events that encapsulate event names, payload structures, and enablement rules within the TelemetryEvent trait.

Can I control telemetry event enablement across development, staging, and production in Rust?▼

Control telemetry event enablement across development, staging, and production by defining enablement rules directly within the TelemetryEvent trait implementation for each feature module.

How do I register Rust telemetry events for analytics dashboards?▼

Register Rust telemetry events for analytics dashboards by exposing the implemented TelemetryEvent instances so they can be consumed by Warp's telemetry pipeline.

Does this telemetry instrumentation approach work without external dependencies?▼

This telemetry instrumentation approach works without external dependencies, relying solely on creating a TelemetryEvent enum and implementing the TelemetryEvent trait within the feature modules.

When do I need structured telemetry events in a Rust codebase?▼

Structured telemetry events are needed in a Rust codebase to standardize event emission for proactive debugging, monitoring feature lifecycle events, and tracking user actions during production.