---
title: "Where cloud provider observability fits | Grafana Labs"
description: "Understanding where cloud provider observability fits in your observability journey"
---

> For a curated documentation index, see [llms.txt](/llms.txt). For the complete documentation index, see [llms-full.txt](/llms-full.txt).

## Observability builds in layers

[Hierarchy of Observability Needs](https://grafana.com/media/docs/learning-hub/instrumentation-hub-hierarchy-of-needs.png "Hierarchy of Observability Needs")

| Level       | Focus          | Question answered               |
|-------------|----------------|---------------------------------|
| **Level 1** | Infrastructure | “Is my cloud healthy?”          |
| **Level 2** | Services       | “Which service is the problem?” |
| **Level 3** | Transactions   | “Why is this request slow?”     |
| **Level 4** | Business logic | “What’s happening in my code?”  |

## Key takeaway

Cloud provider observability gives you Level 1 visibility into your AWS, Azure, and GCP infrastructure.

> You can’t troubleshoot services if you don’t know your cloud is healthy. Cloud provider observability builds that foundation.