Slide 6 of 10

Cloud Provider Observability overview

Unified visibility across AWS, Azure, and GCP

CloudMetricsLogs
AWSCloudWatch Scrape, CloudWatch StreamsCloudWatch Logs, Firehose
AzureAzure Monitor via AlloyEvent Hub, Azure Functions
GCPCloud Monitoring via AlloyPub/Sub

Choose your strategy

StrategyHow it worksBest for
Store in Grafana CloudCollect metrics/logs → Grafana Cloud storageLong retention, unified alerting
Query directlyQuery cloud APIs on demandQuick setup, no data movement
HybridStore critical, query the restBalance cost and capability

Questions answered

With Cloud Provider Observability, you can answer…
How do my AWS EC2 instances compare to Azure VMs in one view?
Which cloud region has the highest latency?
What were my Lambda function errors last month?
How is my multi-cloud infrastructure performing overall?

Problems solved

ProblemSolution
Metrics siloed in each cloudUnified multi-cloud visibility
Limited cloud provider retention13 months for metrics in Grafana Cloud
Different query languagesPromQL/LogQL for everything

Script

If you’re running workloads in AWS, Azure, or GCP, or across multiple clouds, Cloud Provider Observability is how you bring all that visibility together.

Each cloud provider has its own monitoring system: CloudWatch for AWS, Azure Monitor, Google Cloud Monitoring. They’re fine on their own, but trying to compare EC2 performance against Azure VMs? Or troubleshooting an issue that spans multiple clouds? That’s where things get painful.

Cloud Provider Observability solves this by giving you options. You can collect metrics and logs from each cloud and store them in Grafana Cloud. Great for long retention and unified alerting. Or you can query each cloud’s native monitoring directly. Quick setup, no data movement. Most teams do a hybrid: store the critical stuff, query the rest.

The result? You can answer questions like “Which cloud region has the highest latency?” or “What were my Lambda errors last month?” all from one place, using a consistent query language.