Skill: Grafana Alloy Collector Configs
by Grafana Labs
Grafana's official Alloy skill: write one collector config that carries metrics, logs, traces and profiles, validate it locally, and prove samples are actually leaving the box.
Grafana's official Tempo skill: stand up a tracing backend that needs nothing but object storage, then write TraceQL that finds the slow span instead of scrolling for it.
Add this skill to your favorite AI agent in a few steps.
Tempo is Grafana's distributed tracing backend, and its selling point is what it does not need: no Cassandra, no Elasticsearch, no index cluster. Traces go into Parquet blocks in S3, GCS or Azure, and that is the whole storage tier. This skill is the official Grafana Labs guidance for running it and querying it.
It is built around workflows rather than a feature tour. The first one stands Tempo up locally from the upstream Docker Compose example, pushes a synthetic OTLP span with a copy-pasteable curl, and — importantly — verifies the span actually landed by checking tempo_distributor_spans_received_total and fetching the trace back by ID. The second wires a real application in through Grafana Alloy, with the otelcol.receiver.otlp → otelcol.exporter.otlp config and the exporter metric to confirm spans are leaving. The fourth deploys the tempo-distributed Helm chart against an S3 bucket and checks every component pod is Ready before port-forwarding the query frontend.
The third workflow is TraceQL. The skill covers the scopes that matter (span., resource., event.), intrinsics such as duration, kind and status, the structural operators >> and << that let you ask "which server span had a downstream error", and the metrics functions rate() and quantile_over_time for turning a trace search into a time series. A curl example shows the same query through /api/search for anything scripted.
Ingestion covers OTLP, Jaeger, Zipkin, OpenCensus and Kafka. Multi-tenancy via X-Scope-OrgID is documented alongside the mismatch that causes the single most common complaint — traces are being written but Explore shows nothing because the writer and the datasource disagree on the tenant header. Other troubleshooting entries cover a 503 on /ready, 429s on push and the levers for a slow TraceQL query.
Apache-2.0, shipped in grafana/skills, and installable via npx skills add grafana/skills or the Claude Code plugin marketplace. Companion references go deeper on the full TraceQL cheat sheet and on architecture, ports, tuning, the metrics-generator for RED span metrics and service graphs, and the traces-to-logs / metrics / profiles datasource links.
by Grafana Labs
Grafana's official Alloy skill: write one collector config that carries metrics, logs, traces and profiles, validate it locally, and prove samples are actually leaving the box.
by Datadog
Install, instrument and analyse Datadog APM from an agent — Kubernetes and Linux Single-Step Instrumentation, service remapping, trace search and service maps.
by Grafana Labs
Grafana's official Loki skill: write LogQL that returns rows instead of timeouts, ship logs through Alloy, and reason about a store that indexes labels rather than log text.
by Grafana Labs
Grafana's official PromQL skill: write, validate, and optimise Prometheus queries, and hunt down the label that blew up your cardinality.