Documentation for automated readers
A curated documentation index is available at: https://grafana.com/llms.txt
A complete documentation index is available at: https://grafana.com/llms-full.txt
These indexes can help with page discovery before fetching individual documents.
This page is also available in Markdown, which may be easier for automated readers and AI tools to parse than HTML. The Markdown version is available at https://grafana.com/docs/grafana-cloud/observe-and-act/monitor-infrastructure/monitor-cloud-provider/home-page.md, or by sending Accept: text/markdown to https://grafana.com/docs/grafana-cloud/observe-and-act/monitor-infrastructure/monitor-cloud-provider/home-page/. For broader documentation discovery, the curated index is available at https://grafana.com/llms.txt and the complete index is available at https://grafana.com/llms-full.txt.
Cloud Provider home page
The home page is the entry point for Cloud Provider Observability. When you configure at least one cloud provider, the page becomes a live summary of your environment, so you can see what needs attention across AWS, Azure, and GCP without opening each provider individually.
The home page surfaces the operational signals that matter most: firing alerts, error log trends, and resource health, giving you a single place to triage issues and decide where to look next.
Why use the home page
The home page helps you:
- Get a bird’s-eye view. See resource counts, alerts, error logs, and health for every configured provider at a glance, rather than navigating to each provider section.
- Triage faster. Firing alerts, recent error logs, and unhealthy resources appear together, so you can move from noticing a problem to investigating it in fewer clicks.
- Focus on what you use. The page only includes your configured providers and lets you filter to the ones you want to review.
- Discover related tools. Quick links and per-provider actions take you to dashboards, alerts, logs, and the full resource health view.
Before you begin
To use the home page, you must have:
- Cloud Provider Observability configured with at least one provider connection for AWS, Azure, or GCP.
- Preconfigured alerts installed for Cloud Provider Observability.
- Read access to Cloud Provider Observability, which any Grafana Cloud basic role of Viewer or above grants. If you have a Cloud Provider plugin role but no Grafana Cloud basic role, you also need the
Datasources:Readerfixed role to see data on the home page.
If you haven’t configured a provider yet, the home page shows the provider picker instead of live data. Select a provider to start configuring it. Refer to AWS observability, Microsoft Azure observability, or Google Cloud Platform observability.
Open the home page
To open the home page, in the main menu select Observability > Cloud provider.
Filter and scope the view
Controls at the top of the page let you scope everything below them:
- Cloud Provider: Select one or more configured providers to include. All panels, cards, and totals update to match your selection. Your selection persists in the page URL and in your browser, so you can bookmark or share a filtered view and return to it later.
- Metrics datasource: Choose the Prometheus data source used for resource counts and health queries.
- Logs datasource: Choose the Loki data source used for the error log trends.
Review provider summary cards
Each configured provider has a summary card that shows:
- A Configured status badge.
- The number of firing alerts, when any alerts are firing.
- The number of monitored resources.
- Quick Links to Dashboards for common services, such as EC2 and RDS for AWS, or Virtual Machines and SQL Database for Azure.
Use these cards to confirm what’s connected and to jump straight to a provider’s dashboards.
Review firing alerts
The Firing Alerts panel lists alerts currently firing across the selected providers, sorted with the most recent first. For each alert, the table shows the provider, alert name, affected resource, severity, service, and how long the alert has been firing.
From this panel you can:
- Select View on any row to open that alert’s details in the Alerts tab.
- Select View AWS alerts, View Azure alerts, or View GCP alerts to open a provider’s alerts page filtered to firing alerts.
The table shows up to 10 alerts. When more alerts are firing, a footer indicates how many more pages of alerts there are with clickable numbers and arrows for you to select a different page of alerts.
Note
When the Knowledge graph is activated on your stack and the affected service is supported, each resource displays an Insights ring that summarizes the resource’s current health.
Review error log trends
The Error Log Trends panel shows error and warning log volume by provider over the last 24 hours, along with a total count for each provider. Use it to spot spikes in error activity and to see which provider is generating them.
Select View AWS Logs, View Azure Logs, or View GCP Logs to open a provider’s logs page for a closer look.
Review resource health
The Resource Health Overview panel shows the health status of your active cloud services, grouped by provider. Health is evaluated for key service categories such as compute, storage, and databases, using service-specific metrics over a rolling one-hour window.
For each service, the panel shows:
- A status badge of Healthy, Unhealthy, or No data. The badge reflects the whole service. It shows Unhealthy when any resource in that service is unhealthy, Healthy only when every resource is healthy, and No data when no health data is available. Hover over the badge to see the health definition used for that service.
- A summary of the service’s current state, shown as either an availability percentage or the number of healthy or unhealthy resources. This summary tells you the scope and severity behind the badge, so you can prioritize before you drill in. An availability percentage shows how close a service is to its target, letting you tell a minor dip from a service-wide outage. A resource count shows how many resources are affected out of the total, so you can tell a single unhealthy instance from a widespread failure. Two services can both show Unhealthy while needing very different responses, and the summary is what distinguishes them.
- An Explore action that opens Grafana Explore in a new tab, pre-loaded with the service’s health query against the selected metrics data source over the last hour. Use it to inspect and adjust the underlying query rather than to open a dashboard.
Because a single unhealthy resource marks the whole service Unhealthy, expand the row to see exactly which resources are affected. Each unhealthy resource in the expanded list links to that resource’s drilldown page, where you can investigate it in the service dashboard.
The panel shows up to five services per provider. To see every service, select View all services, which opens the full resource health page with no limit.
Note
When the Knowledge graph is activated on your stack, unhealthy resources display an Insights ring that reflects insights from connected entities.
Next steps
From the home page, you can move directly into deeper investigation:
- Analyze cloud resources with the Knowledge graph to explore relationships between resources and run root cause analysis.
- Analyze alerts and build dashboards with Grafana Assistant to investigate alerts and generate dashboards without leaving the app.
Was this page helpful?
Related resources from Grafana Labs


