testing
Probe, load-test, and instrument frontends from Grafana Cloud. Covers Synthetic Monitoring (HTTP / DNS / TCP / Ping / Traceroute / Multihttp / k6-browser scripted checks from 20+ global probes, alert on `probe_success` + TLS-cert expiry), Grafana Cloud k6 (distributed load tests across AWS load-zones, scenarios, `http_req_duration` thresholds, CI integration via `grafana/k6-action`), and Frontend Observability with Faro Web SDK (RUM, Core Web Vitals, custom events, `pushError`, distributed-trace
Security Assessment
Detected risks:
About testing
grafana-skills-testing helps you probe, load-test, and instrument web frontends and APIs from Grafana Cloud. It spans three pillars: Synthetic Monitoring for external uptime and protocol checks (HTTP, DNS, TCP, Ping, Traceroute, Multihttp, and scripted k6-browser checks) run from 20+ global probes; Grafana Cloud k6 for distributed load testing across AWS load zones with pass/fail thresholds; and Frontend Observability with the Faro Web SDK for real-user monitoring, Core Web Vitals, custom events, and error-to-trace correlation.
The skill provides concrete, verifiable workflows: creating a synthetic HTTP check via the Synthetic Monitoring API and confirming that probe_success metrics arrive, running a k6 cloud load test (validate locally first, then launch in the cloud and gate CI on threshold exit codes), and wiring Faro into a React or Vue app. It documents the required credentials (an sm:write token, a Grafana Cloud k6 token plus projectID, and a Faro app write-token) and includes rollback guidance such as deleting or disabling a check, keeping operations reversible.
It is aimed at SREs, platform, and frontend engineers who need multi-region uptime checks, release-gating load tests, TLS-certificate expiry alerts, or RUM and Core Web Vitals tracking — including when a user asks in plain terms like "is my login flow up?", "monitor my API", or "release-gate load test" without naming the underlying products.
FAQ
What three capabilities does this skill cover?
Synthetic Monitoring (external probing of HTTP/DNS/TCP/Ping/Traceroute/Multihttp/k6-browser from 20+ global probes), Grafana Cloud k6 (distributed load testing with thresholds and CI integration), and Frontend Observability via the Faro Web SDK (RUM, Core Web Vitals, custom events, trace correlation).
What credentials are required?
A Synthetic Monitoring access token with sm:write, a Grafana Cloud k6 token plus a projectID, and a Faro app write-token from Frontend Observability → Apps. Tokens are passed as bearer credentials to the respective APIs.
How does it gate a release on a load test?
Run the k6 script (validated locally first, then in the cloud); thresholds such as p95<500ms and error<1% decide pass/fail, and the CI exit code (0 = passed, 99 = threshold failed) gates the pipeline.
Are the operations reversible?
Yes. Synthetic checks can be removed with a DELETE or set to disabled, and the skill documents rollback steps alongside the create workflows.
Install testing
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
grafana/skills