rust-observability

Implement OpenTelemetry tracing, metrics, and structured logging for Rust applications.

44|7|Updated Jan 22, 2026

Search Tags:#logging #metrics #observability #rust #diagnostics #tracing #opentelemetry

Ready to run

npx skills add https://github.com/huiali/rust-skills --skill rust-observability-huiali

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rust-observability
Source: https://github.com/huiali/rust-skills/tree/main/.codex/skills/rust-observability
Command: npx skills add https://github.com/huiali/rust-skills --skill rust-observability-huiali

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes agents (resource) components.

What problem does it solve?

This Skill addresses the challenge of quickly identifying and resolving production failures in Rust applications by providing a structured approach to telemetry.

Core Features & Use Cases

Structured Telemetry: Integrates logs, traces, and metrics for comprehensive system visibility.
Production Incident Diagnostics: Aids in pinpointing the root cause of failures by analyzing signal data.
Use Case: Debugging a slow API endpoint by examining trace data for latency bottlenecks, reviewing structured logs for errors, and checking metrics for resource saturation.

Quick Start

Use the rust-observability skill to diagnose a production incident in a Rust application.

Frequently Asked Questions about rust-observability

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

FAQPage Schema

How do I implement tracing and structured logging in Rust to diagnose production incidents?▼

Implement Rust observability by establishing an OpenTelemetry pipeline that unifies tracing, structured logging, and metrics. This signal model pinpoints root causes of production failures by analyzing latency bottlenecks and resource saturation.

What is the best way to avoid high-cardinality labels when instrumenting Rust metrics?▼

To avoid high-cardinality label issues in Rust metrics, apply defined instrumentation rules that restrict label dimensions. This prevents excessive time-series generation and keeps your observability pipeline performant during production diagnostics.

How does OpenTelemetry work with Rust applications for comprehensive system visibility?▼

OpenTelemetry works in Rust by integrating logs, traces, and metrics into a single pipeline for comprehensive visibility. It correlates structured telemetry signals to identify failure points and reduce mean time to resolve production incidents.

Can I use this observability approach to debug a slow Rust API endpoint?▼

Yes, you can debug slow Rust API endpoints by examining trace data for latency bottlenecks, reviewing structured logs for errors, and checking metrics for resource saturation. This integrated approach quickly identifies the root cause.

What are common pitfalls when setting up Rust production diagnostics and how do I verify the configuration?▼

Common Rust diagnostics pitfalls include high-cardinality labels and verbose logs. Verify your observability configuration by applying a review checklist and running specific verification commands to ensure instrumentation priorities are correctly set.

Do I need OpenTelemetry to build an effective observability pipeline in Rust?▼

OpenTelemetry is central to building an effective Rust observability pipeline, providing the framework to connect logs, traces, and metrics. It defines the signal model and instrumentation priorities needed to reduce incident resolution time.