SYSTEM Cited by 1 source
Grafana Cloud¶
Grafana Cloud is Grafana Labs' fully-managed observability platform — a single vendor-operated stack combining Grafana dashboards, metrics (Mimir-powered, Prometheus-compatible), logs (Grafana Cloud Logs / Loki), traces (Tempo), continuous profiles (Pyroscope 2.0), synthetic monitoring, frontend observability (Faro-based), application observability, and Kubernetes monitoring. It is the managed-hosted counterpart of the open-source Grafana stack.
Why it shows up on this wiki¶
Grafana Cloud is the control-plane target for multiple
Grafana-ecosystem CLIs, MCP servers, and as-code workflows. The
2026-04-29 gcx launch canonicalises Grafana Cloud's full
observability lifecycle as the surface an agent-ergonomic CLI
can cover end-to-end: instrumentation validation → alert
generation → SLO definition → synthetic probes → dashboards /
alerts / SLOs / checks as code.
Surface areas (as addressed by gcx and Instrumentation Hub)¶
- Instrumentation — accept OpenTelemetry data; validate that metrics/logs/traces are flowing; confirm data is landing in the right metric/log/trace backend.
- Alerting, SLOs, synthetics — alert rules over emitted signals; SLOs defined against real latency/availability indicators (Service Level Objectives); synthetic probes as first-class Cloud resources.
- Frontend Observability — Faro browser SDK with sourcemap management.
- Application Observability — backend service onboarding (OTel-based).
- Kubernetes Monitoring — cluster and workload onboarding.
- Everything as code — every resource listed above pull-able as local files, edit-able with an agent, push-able back.
- Deep links into the UI — documented generator emits URL deep-links into specific dashboards / alerts / SLOs for human handoff from CLI / agent sessions.
Design posture¶
Grafana Cloud sits at the intersection of three wiki themes:
- Managed counterpart of the open-source stack. Same Loki / Mimir / Pyroscope engines as the OSS bundle, but Grafana Labs operates the database tier and retention. The Grafana Labs page canonicalises the "managed-first rollout for new architecture" pattern — Logline-powered needle-in-haystack log queries launched in Grafana Cloud Logs under operational control before OSS general availability.
- CLI + MCP + agent-skills target. As of 2026-04, Grafana Labs ships both the gcx CLI (direct-exec for agents) and a Grafana MCP server (see the deep-links guide referenced in the gcx launch post). The managed platform is the control-plane endpoint for both.
- Observability-as-code destination. Dashboards, alerts, SLOs, and synthetic checks are all addressable as pull-edit-push resources via gcx, making Grafana Cloud a canonical instance of patterns/observability-as-code.
Seen in¶
- sources/2026-04-29-grafana-get-observability-in-the-terminal-for-you-and-your-agents-with-the-gcx-cli-tool — gcx launch post. Canonicalises Grafana Cloud as the end-to-end observability-lifecycle surface exposed by gcx — instrumentation validation, alert generation, SLO definition, synthetic probes, and everything-as-code. Ties the platform to the "open a [deep link] into Grafana Cloud the moment a human needs to look" handoff pattern.
Related¶
- systems/grafana — the visualisation / dashboarding surface
- systems/grafana-mimir — metrics backend
- systems/loki — log backend
- systems/pyroscope-2 — continuous-profiling backend
- systems/grafana-cloud-logs — managed Loki offering, named companion product
- systems/grafana-faro — frontend-observability SDK
- systems/gcx-cli — the agent-ergonomic CLI that targets this platform
- systems/opentelemetry — primary instrumentation protocol Grafana Cloud ingests
- systems/prometheus — protocol compatibility
- concepts/observability
- concepts/observability-as-code
- concepts/service-level-objective
- patterns/observability-as-code
- patterns/deep-link-to-ui-from-cli
- companies/grafana