Query Grafana Tempo

Query Grafana Tempo traces via curl and save results to a temporal text file.

10|1|Updated Nov 24, 2010
One-click install
npx skills add https://github.com/narqo/dotfiles --skill query-grafana-tempo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Query Grafana Tempo
Source: https://github.com/narqo/dotfiles/tree/main/claude/skills/tempo-query
Command: npx skills add https://github.com/narqo/dotfiles --skill query-grafana-tempo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you fetch and analyze distributed traces from Grafana Tempo via the Tempo API, saving time and enabling offline analysis.

Core Features & Use Cases

  • Trace retrieval: Pull traces within a specified time window.
  • Multi-instance support: Query both ops and dev Tempo instances for testing.
  • Offline analysis: Store results in a temporal file for offline analysis.

Quick Start

Query a trace by ID using curl against the Tempo API, with start and end times in unix epoch seconds (UTC), and save the output to a temporary file for offline analysis.

Frequently Asked Questions about Query Grafana Tempo

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

FAQPage Schema
How do I query traces from Grafana Tempo using the API?

Query Grafana Tempo traces by using curl with the Tempo API endpoint, specifying start and end times as Unix epoch seconds in UTC. The Skill retrieves distributed traces within your specified time window and saves results to a file for offline analysis.

What format do I need for start and end times when querying Tempo?

Tempo API queries require start and end times as Unix epoch seconds in UTC. Convert your desired time range to epoch format before passing it to curl --get against the Tempo endpoint.

Can I query traces from multiple Tempo instances?

Yes, this Skill supports querying both ops and dev Tempo instances. You can pull traces from different instances by specifying different endpoint URLs and authentication tokens as needed.

How do I authenticate when querying Tempo via curl?

Authentication to Tempo uses token files. Store your API token in a file and reference it in your curl request to authenticate against the Tempo endpoint.

Why would I save Tempo trace results to a file?

Saving trace results to a temporal file enables offline analysis of distributed traces for debugging, performance investigation, and SLA auditing without requiring continuous API access.