Archestra Dev Observability
archestra-ai/archestra
A skill your agent uses when changing Archestra tracing, metrics, OpenTelemetry, Tempo, Grafana, Prometheus, LLM/MCP spans, observability labels, or local observability setup.
Finds where a Prometheus metric stops existing, whether at the target, the scrape, relabeling or the query, using the tools of a connected Prometheus MCP server.
Install Prometheus Missing Data Troubleshooting
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-data --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .claude/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .claude/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-dataType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-data --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .agents/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .agents/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-data --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .cursor/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .cursor/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/prometheus/prometheus-mcp.git --path pkg/mcp/assets/skills/troubleshoot-missing-data--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-data --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .gemini/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .gemini/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-dataInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .github/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .github/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .github/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install prometheus/prometheus-mcp troubleshoot-missing-data --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/prometheus/prometheus-mcp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pkg/mcp/assets/skills/troubleshoot-missing-data .opencode/skills/troubleshoot-missing-data && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "troubleshoot-missing-data" agent skill from https://github.com/prometheus/prometheus-mcp/tree/main/pkg/mcp/assets/skills/troubleshoot-missing-data into .opencode/skills/troubleshoot-missing-data/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshoot-missing-data", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
troubleshoot-missing-data- GitHub stars
- 117
- Token cost
- ~587 tokens
- SKILL.md length
- 278 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Finds where a Prometheus metric stops existing, whether at the target, the scrape, relabeling or the query, using the tools of a connected Prometheus MCP server.
- A dashboard panel suddenly shows no data
- SKILL.md covers Getting oriented, Topics worth exploring and Reporting findings
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- A metric stopped reporting after an upgrade or deploy
What it does
This skill works out why an expected metric or series is absent: the target is not being scraped, no longer exposes the metric, the labels changed, or the query itself misses data that exists. It begins with the MCP tools list_targets for scrape health and last errors, label_values on __name__ to see whether the name exists, targets_metadata for what a target exposes, and config for jobs, relabeling and intervals.
From there it suggests checking whether the target is up, searching for renamed or relabeled versions of the metric, running a range query to find when the series disappeared and correlating that with deploys, looking for relabel rules that drop it, and ruling out staleness, a narrow time window or a strict matcher. Rejection counters in Prometheus's own scrape metrics can explain silent drops. The final report says where the data stops, since when and what change would restore it.
When your agent uses it
- A dashboard panel suddenly shows no data
- A metric stopped reporting after an upgrade or deploy
- A scrape target is down or was never scraped
- A query returns nothing although the metric should exist
Example prompts
- “Our http_requests_total series disappeared yesterday, so work out where the data stops.”
- “The payments job shows as down in our dashboards, so check target health and scrape errors.”
- “Why does the up query for the checkout job return nothing?”
Requirements
- A connected Prometheus MCP server
- Compatibility (from SKILL.md): Requires the tools of a connected Prometheus MCP server
What it can do on your machine
Read from SKILL.md and the folder at commit 856fb45. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Compatibility
Requires the tools of a connected Prometheus MCP server
From compatibility in the SKILL.md frontmatter.
Context cost
Prometheus Missing Data Troubleshooting loads about 587 tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 278 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from prometheus/prometheus-mcp at commit 856fb45, republished under its Apache-2.0 licence (© prometheus). 278 words, ~587 tokens.
Download SKILL.mdSave it as
.claude/skills/troubleshoot-missing-data/SKILL.md (or your agent's skills folder).- name
- troubleshoot-missing-data
- description
- Diagnose missing metrics, absent series, or scrape gaps. Use when queries unexpectedly return empty, a metric stopped reporting, a target is down or unscraped, or dashboards show no data; walks target health, metadata, and config checks.
- compatibility
- Requires the tools of a connected Prometheus MCP server
- license
- Apache-2.0
Troubleshooting Missing Data
Work out why an expected metric or series is absent: the target is not being scraped, the target no longer exposes it, the labels changed, or the query itself misses data that exists. Narrow down where the pipeline breaks.
Getting oriented
- list_targets shows scrape target health, the lastError for failing scrapes, and the labels applied at scrape time.
- label_values on name (optionally with matchers) confirms whether a metric name exists at all right now.
- targets_metadata lists which metrics a given target actually exposes.
- config shows the scrape configuration: job definitions, relabeling, and intervals.
- Prometheus's own scrape metrics explain silent drops: nonzero rates on the prometheus_target_scrapes_* rejection counters (sample_out_of_order, sample_out_of_bounds, duplicate_timestamp, exceeded_sample_limit) mean samples arrived but were rejected at ingestion.
Topics worth exploring
Treat these as starting points and follow where the data stops:
- Is the target up and scraped? query up{job="
<job>"} and check list_targets for down or missing targets and their scrape errors. - Does the metric exist under a different shape? Search broadly, e.g. series with a matcher like {name=~".
<keyword>."} -- renames and label changes are common after upgrades. - Did it exist before? range_query the series over a wide window to find exactly when it disappeared, then correlate with deploys or config changes.
- Is relabeling dropping it? Look through relabel_configs and metric_relabel_configs in config for rules that drop the target, metric, or label you expected.
- Is it the query, not the data? Staleness handling (series go stale after 5m without samples), a too-narrow time window, or an over-strict matcher can make live data look absent.
Reporting findings
State where the data stops existing (target, scrape, relabeling, or query), since when, and what change would restore it.
© prometheus, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in pkg/mcp/assets/skills/troubleshoot-missing-data of prometheus/prometheus-mcp.
Open the folder on GitHubat commit 856fb45
Compare with similar skills
Prometheus Missing Data Troubleshooting next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prometheus Missing Data Troubleshooting this skillprometheus/prometheus-mcp | 117 | — | ~587 | Automated safety check: Pass | Apache-2.0 | |
| Archestra Dev Observabilityarchestra-ai/archestra | 4.3k | — | ~1.2k | Automated safety check: Pass | Custom licence | |
| Frontmcp Observabilityagentfront/frontmcp | 146 | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Live Debugmacro-inc/macro | 4.6k | — | ~2.4k | Automated safety check: Notes | AGPL-3.0 | |
| Cx Telemetry Queryingcoralogix/cx-cli | 121 | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| AWS Cost OperationsMicrock/ordinary-claude-skills | 401 | 1 repos | ~2.5k | Automated safety check: Pass | Custom licence |
Similar skills
Frontmcp Observability
agentfront/frontmcp
A skill your agent uses when adding tracing, structured logging, metrics, or monitoring to a FrontMCP server.
Live Debug
macro-inc/macro
Debug the running local stack with traces, logs, and a shared headless browser.
Cx Telemetry Querying
coralogix/cx-cli
A skill your agent uses for any question involving telemetry data: "investigate an issue", "debug a problem", "find out why something is slow", "check error rates", "analyze user behavior"…
AWS Cost Operations
Microck/ordinary-claude-skills
This skill provides AWS cost optimization, monitoring, and operational best practices with integrated MCP servers for billing analysis, cost estimation, observability, and security assessment.
Grafana Observability
automateyournetwork/netclaw
Grafana observability platform — dashboards, Prometheus PromQL, Loki LogQL, alerting, incidents, OnCall schedules, annotations, datasource queries, panel rendering (75+ tools).
More from prometheus/prometheus-mcp
Prometheus System Health Check
prometheus/prometheus-mcp
Builds a picture of whether Prometheus itself is healthy and successfully monitoring its targets, covering readiness, firing alerts, target health and TSDB load.
Prometheus Top Resource Consumers
prometheus/prometheus-mcp
Find the top CPU, memory, or disk consumers. Use for capacity reviews, noisy-neighbor hunts, and top-N questions about which jobs, pods, or instances use the…
Prometheus Error Rate Investigator
prometheus/prometheus-mcp
Quantifies elevated error rates with PromQL, compares them to a baseline, and isolates which jobs or instances an error spike is concentrated in.
Prometheus Cardinality Optimizer
prometheus/prometheus-mcp
Finds the metrics and labels behind a Prometheus series explosion using a connected Prometheus MCP server, then proposes relabeling, dropping or recording-rule fixes with measured impact.
Prometheus Rules Review
prometheus/prometheus-mcp
Audits Prometheus recording and alerting rules through a connected Prometheus MCP server, finds gaps and noisy alerts, and drafts improved rule-group YAML.
Tune Prometheus Config
prometheus/prometheus-mcp
Review and tune Prometheus configuration and performance. An agent skill from prometheus/prometheus-mcp.
Related
Works with
Categories
Questions about Prometheus Missing Data Troubleshooting
What does Prometheus Missing Data Troubleshooting do?
Finds where a Prometheus metric stops existing, whether at the target, the scrape, relabeling or the query, using the tools of a connected Prometheus MCP server. This skill works out why an expected metric or series is absent: the target is not being scraped, no longer exposes the metric, the labels changed, or the query itself misses data that exists. It begins with the MCP tools list_targets for scrape health and last errors, label_values on __name__ to see whether the name exists, targets_metadata for what a target exposes, and config for jobs, relabeling and intervals.
When should I use Prometheus Missing Data Troubleshooting?
Prometheus Missing Data Troubleshooting fits situations like: A dashboard panel suddenly shows no data; A metric stopped reporting after an upgrade or deploy; A scrape target is down or was never scraped; A query returns nothing although the metric should exist.
How do I install Prometheus Missing Data Troubleshooting in Claude Code?
Run `npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a claude-code`. Or copy the skill folder (pkg/mcp/assets/skills/troubleshoot-missing-data in prometheus/prometheus-mcp) into .claude/skills/troubleshoot-missing-data in your project. Claude Code loads it when a task matches its description.
How do I install Prometheus Missing Data Troubleshooting in Codex?
Run `npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a codex`. Or copy the skill folder (pkg/mcp/assets/skills/troubleshoot-missing-data in prometheus/prometheus-mcp) into .agents/skills/troubleshoot-missing-data in your project. Codex loads it when a task matches its description.
Can I use Prometheus Missing Data Troubleshooting in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add prometheus/prometheus-mcp --skill troubleshoot-missing-data -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshoot-missing-data, .gemini/skills/troubleshoot-missing-data, .github/skills/troubleshoot-missing-data and .opencode/skills/troubleshoot-missing-data in your project.
What does Prometheus Missing Data Troubleshooting need to run?
SKILL.md names no scripts, command-line tools or credentials: Prometheus Missing Data Troubleshooting is instructions for the agent only. Our summary lists: A connected Prometheus MCP server. Compatibility (from SKILL.md): Requires the tools of a connected Prometheus MCP server.
Does Prometheus Missing Data Troubleshooting access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Prometheus Missing Data Troubleshooting safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Prometheus Missing Data Troubleshooting use?
Prometheus Missing Data Troubleshooting is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Prometheus Missing Data Troubleshooting use?
About 587 tokens (SKILL.md is roughly 2.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Prometheus Missing Data Troubleshooting?
Skills that share tags, products or a category with Prometheus Missing Data Troubleshooting: Archestra Dev Observability (archestra-ai/archestra, 4.3k stars), Frontmcp Observability (agentfront/frontmcp, 146 stars), Live Debug (macro-inc/macro, 4.6k stars) and Cx Telemetry Querying (coralogix/cx-cli, 121 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prometheus Missing Data Troubleshooting?
prometheus (a GitHub organization) maintains it in prometheus/prometheus-mcp, which has 117 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on October 4, 2026.
Source: prometheus/prometheus-mcp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.