Grafana Cloud MOC

A book-shaped table of contents for Grafana Cloud: platform foundations through telemetry collection, Mimir/Loki/Tempo/Pyroscope, visualization, application observability, reliability tooling, developer experience, governance, and enterprise reference architectures — cross-linking existing notes instead of duplicating them.

· §202607221744-54 ·

Grafana Cloud

If this were a book, this page is the table of contents. Each Part below is a chapter; each chapter links out to Grafana product notes and this wiki’s existing concept treatments — PromQL, Mimir, Loki, Tempo, cardinality, SLOs — instead of duplicating them. Chapters are numbered per Part and restart at 1 in every Part. Chapters not yet written are marked — _(stub)_.

Parts

00 — Platform Foundations

The product surface every later Part assumes: what Grafana Cloud is versus OSS/Enterprise, how an organization’s stacks/users/RBAC are structured, and how to navigate the UI day to day.

01 — Telemetry Collection

How telemetry actually gets into Grafana Cloud. Alloy is genuinely new ground for this wiki — every existing mention of it elsewhere is a passing reference, not a treatment — while the OpenTelemetry data model itself is already covered in depth in Instrumentation.

02 — Metrics (Grafana Mimir)

Grafana Cloud’s hosted metrics backend and the language for querying it. PromQL is already a full, deep Part elsewhere in this wiki — this Part links into it rather than re-teaching the language, and owns the Mimir-as-a-product and cost/cardinality layers instead.

03 — Logs (Grafana Loki)

Grafana Cloud’s log aggregation backend and its query language, building on the architecture already written up in Loki.

04 — Traces & Continuous Profiling

Distributed tracing and continuous profiling as Grafana Cloud products, and the cross-signal navigation that ties metrics, logs, traces, and profiles into one investigation flow.

05 — Visualization & Alerting

The day-to-day surface for looking at and reacting to telemetry — dashboards, ad hoc exploration, unified alerting, and sharing. Alerting concept and routing depth already lives in observability/; this Part owns the Grafana-specific mechanics (contact points, notification policies, panel/variable design).

06 — Application Observability

Grafana Cloud’s Application Performance Monitoring layer — automatic service discovery, RED metrics, and the entity/service graph underneath it. Genuinely new product surface, not covered elsewhere in this wiki.

07 — Specialized Monitoring

Monitoring domains that each get their own dedicated Grafana Cloud product: Kubernetes, the browser, synthetic checks, and load testing.

08 — Reliability Engineering

Grafana’s SRE product suite — SLO tracking, incident management, on-call scheduling, and IRM — layered on top of the SLI/SLO/error-budget theory already written up in observability/.

09 — Developer Experience & Platform Engineering

Treating Grafana Cloud itself as code: the gcx CLI, the REST APIs underneath it, the Terraform provider, and GitOps for dashboards/alerting. gcx already covers the CLI command surface and token model in depth — this Part’s GCX chapter should extend that note rather than restate it.

10 — Administration & Governance

The governance layer: security and access, cost control, agent fleet management, AI-assisted operations, and the naming/folder standards that keep a shared Grafana Cloud org from decaying into chaos.

11 — Enterprise Architectures

Full reference architectures for running Grafana Cloud alongside the major clouds and Kubernetes, plus the production and troubleshooting playbooks a Principal/Staff candidate is expected to reason from.

12 — Appendices

Quick-reference material — CLI/API/query-language cheat sheets, pattern catalogs, and certification/interview prep — mirroring how prometheus/ represents its own appendices as a trailing Part rather than a separate construct.

Metadata

AuthorAmit Singh
Scopegrafana-cloud

Local graph

Full graph →

Related notes