skills.rest
alex-voloshin-dev
alex-voloshin-devCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

telemetry-stacks

Reference query syntax for Prometheus, Datadog, Honeycomb, New Relic, Sentry, and OpenTelemetry.

2|Updated Mar 19, 2026
Search Tags:#debugging#monitoring#metrics#observability#telemetry#sre
One-click install
npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill telemetry-stacks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: telemetry-stacks
Source: https://github.com/alex-voloshin-dev/ai-skills/tree/main/plugin/skills/telemetry-stacks
Command: npx skills add https://github.com/alex-voloshin-dev/ai-skills --skill telemetry-stacks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves the complexity of navigating diverse production telemetry stacks by providing a unified reference for query syntax and diagnostic patterns across Prometheus, Datadog, Honeycomb, New Relic, Sentry, and OpenTelemetry.

Core Features & Use Cases

  • Cross-Stack Query Reference: Provides immediate access to specific query syntax for metrics, logs, and traces across six major observability platforms.
  • Contextual Diagnosis: Maps high-level observability signals like RED or USE methods to vendor-specific query implementations.
  • Use Case: When investigating a production latency spike, use this skill to identify the correct query syntax for your specific stack—whether it is PromQL for Prometheus or NRQL for New Relic—to isolate the root cause.

Quick Start

Use the telemetry-stacks skill to identify the correct query syntax for surfacing p99 latency in our Datadog environment.

Frequently Asked Questions about telemetry-stacks

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

FAQPage Schema
How do I query p99 latency across different observability platforms?▼

Yes, this skill provides a cross-stack query reference for Datadog, Honeycomb, New Relic, Prometheus, Sentry, and OpenTelemetry. It maps diagnostic patterns like RED or USE methods to vendor-specific query implementations.

How do I find the correct query syntax for investigating a production latency spike?▼

This skill maps high-level observability signals like RED or USE methods to vendor-specific query implementations. It translates diagnostic workflows into the correct query patterns for your specific production environment.

Does this telemetry reference support OpenTelemetry and Sentry?▼

You need to identify your deployed stack via infrastructure configuration files. Providing accurate, context-aware query instructions requires knowing exactly which observability platform your environment uses.

What is the best way to map RED or USE diagnostic methods to my current monitoring stack?▼

This skill supports querying metrics, logs, and traces across six major observability platforms. It focuses on providing query syntax and UI patterns rather than configuring the underlying telemetry collection infrastructure.

Related Skills

Explore More Software Engineering Skills→
syntropic137syntropic137

observability-queries

Provides validated LogsQL, PromQL, and Jaeger trace queries for telemetry retrieval.

Official
Intermediate
Arvo-AIArvo-AI
387

datadog

Query Datadog logs, metrics, traces, and events for root cause analysis.

Official
Intermediate
reverb256reverb256

monitoring-observability

Automate setup of monitoring and observability with Prometheus, Grafana, and Loki.

Community
Advanced
cedriczielcedricziel

opentelemetry-go

Instrument Go applications with OpenTelemetry for traces, metrics, and OTLP export.

Community
Advanced