nebius-grafana-query

Run read-only Grafana MCP queries for Nebius metrics, logs, traces, and dashboards.

7|5|Updated Jul 22, 2025
One-click install
npx skills add https://github.com/nebius/nebius-ps-services --skill nebius-grafana-query-nebius
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nebius-grafana-query
Source: https://github.com/nebius/nebius-ps-services/tree/main/skills/nebius-grafana-query
Command: npx skills add https://github.com/nebius/nebius-ps-services --skill nebius-grafana-query-nebius

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Answering observability questions about Nebius cloud resources requires navigating Grafana datasources, PromQL, LogQL, and TraceQL while respecting strict scope, authorization, and read-only boundaries. This Skill provides a bounded, fail-closed workflow for querying metrics, logs, traces, and dashboards through a pre-configured grafana-nebius MCP server without risking mutations, credential misuse, or unscoped queries. ## Core Features & Use Cases - Scoped read-only queries: Resolve explicit tenant, project, and resource scopes into fail-closed predicates, discover datasources and labels, and run bounded Prometheus, Loki, and Tempo queries with fixed execution limits. - Structured result reports: Return ranked, signal-aware reports with per-group statistics, coverage and access evidence, and explicit truncation disclosure instead of raw telemetry dumps. - Embedded evidence provider: Supply troubleshoot and sdlc-evaluate workflows with a fixed facts envelope, one-time readiness checks, and cumulative fast/deep query budgets. - Use Case: Ask for CPU and memory usage per node in a specific MK8s cluster over the last 24 hours and receive a problem-first ranked table with minimum, average, and maximum values, plus coverage and limitation notes. ## Quick Start Ask the agent to show GPU utilization by node for a specific project ID over the last 24 hours using the configured Grafana MCP server.

Frequently Asked Questions about nebius-grafana-query

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

FAQPage Schema
How do I query Nebius metrics and logs with Grafana MCP?

Invoke the skill with explicit tenant, project, or resource IDs and a time range. It discovers accessible datasources and labels, builds fail-closed scope predicates, and runs bounded native Prometheus or Loki queries, returning a ranked report with coverage details.

What happens if the grafana-nebius MCP server is not configured?

The skill never installs or repairs the MCP server itself. In direct mode it stops and directs you to the explicit install-grafana-mcp-for-nebius workflow; in embedded evidence-provider mode it returns unavailable and disables observability for that run.

Can this skill create dashboards, alerts, or annotations in Grafana?

No. The skill is strictly read-only and refuses any mutation such as dashboards, alerts, incidents, annotations, snapshots, service accounts, or datasources. A requested write requires an explicit write-capable workflow chosen by the user.

What are the query limits for metrics, logs, and traces?

Fixed bounds include a one-hour default window, at most 20 scopes, 100 metric series, 20 displayed rows, 20 log lines, 20 trace summaries, and 3 explicit full traces, with four concurrent calls, 120-second per-call timeouts, and a ten-minute total deadline.

Why did my observability request get rejected before any query ran?

Embedded evidence requests are rejected with zero tool calls when authority is missing, selectors are not deterministic, windows are not absolute, budgets are invalid, or the required signal_fit or criterion_fit is absent or malformed.

Does the skill fall back to raw Grafana API requests when tools fail?

Only narrowly: a GET-only datasource-proxy fallback to a discovered signal-compatible UID is allowed when a native tool is unavailable or has a known decode defect. It is never used after 401/403, timeouts, 429, empty results, or 5xx errors.