OBSERVABILITY / grafana
OpenTelemetry with Grafana
Connect application telemetry through direct OTLP export or an Alloy/Collector pipeline.
“Instrument any app with OpenTelemetry and ship metrics / logs / traces to Grafana Cloud or self-hosted Mimir / Loki / Tempo / Pyroscope. …”
01 / THE REASONING
Why this made the selection.
- It wires OpenTelemetry export to Grafana Cloud or a local Alloy collector and checks auth with an empty OTLP POST.
- A 400 on that probe means the endpoint accepted the credentials, while a 401 means the instance id or token is wrong.
- The definition separates direct SDK export, collector forwarding, Operator injection and head versus tail sampling; troubleshooting includes bundler hooks and post-fork provider setup.
- Choose SDK instrumentation versus a collector with sampling
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- skills/grafana-core/opentelemetry/SKILL.md
- README.md
- LICENSE
Our findings
- The first workflow builds an OTLP auth header and curls the Grafana Cloud traces endpoint.
- An empty POST is expected to return 400, not 401 or 404.
- Applications can export to a local Alloy endpoint at http://localhost:4317 instead of directly to Cloud.
- The skill does not claim head sampling keeps rare errors.
- The definition separates direct SDK export, collector forwarding, Operator injection and head versus tail sampling; troubleshooting includes bundler hooks and post-fork provider setup.
- The troubleshooting section distinguishes Node bundlers defeating require hooks from Python worker processes needing provider reinitialization after a fork.
Not established by this review
- The resource was not executed and its tools were not called.
- No skill execution, authenticated service operation, or outcome benchmark was performed.
- Not executed: it was not installed or run.
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Add a skill to your workflow.
DOCUMENTED COMMAND
npx skills add grafana/skills/skills/grafana-core/opentelemetry Run in your terminal to choose your AI tools, project or global scope, and installation method. This short command follows the current upstream version; the review covers the revision shown above.
Optional: install the reviewed revision
Keeps the original source and installer version where recorded, while leaving your AI tools and installation scope for you to choose.
npx skills add https://github.com/grafana/skills/tree/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/opentelemetry - Install the pinned skill directory interactively, retaining its bundled references and scripts.
- Identify the actual stack OTLP endpoint and required publisher credentials, then choose http/protobuf or gRPC consistently.
- Generate application traffic and inspect receiver/exporter counters plus a retrievable trace.
Before you start
- An application and compatible instrumentation package
- OTLP receiver and optional Grafana Cloud credentials
04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Pinned skill definition ↗Checked
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/opentelemetry/SKILL.md
Supports: summary, whySelected, bestFor, limitations, install, access, review
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/README.md
Supports: install
- Apache-2.0 licence ↗Checked
https://github.com/grafana/skills/blob/1ccacf29049fde66637fe01ab93a83a772da323b/LICENSE
Supports: license
https://raw.githubusercontent.com/grafana/skills/1ccacf29049fde66637fe01ab93a83a772da323b/skills/grafana-core/opentelemetry/SKILL.md
Supports: review.findings, bestFor, upstreamDescription