Collection method by cloud provider
| Cloud | Quick start | Production |
|---|---|---|
| AWS | Scrape Jobs | Metric Streams |
| Azure | Scrape Jobs | Scrape Jobs / Alloy |
| GCP | — | Alloy |
Recommendation by scenario
| Scenario | Recommendation |
|---|---|
| AWS production | Metric Streams |
| Azure production | Scrape Jobs |
| Quick evaluation (any cloud) | Scrape Jobs |
| Multi-cloud environment | Grafana Alloy |
| Want managed/workload identity | Alloy |
Script
Here’s the executive summary on metrics collection.
For AWS production workloads, we recommend metric streams. They have a better cost profile at scale, lower latency for alerting, and are easier to maintain long-term.
Scrape jobs are still great for quick evaluation and proof-of-concept setups.
For Azure, the serverless scrape jobs work great for production. Simple setup with no infrastructure to manage. Alloy is also an option if you need more flexibility or multi-cloud support.
For GCP, Grafana Alloy is the primary collection method.
If you’re running multi-cloud or want the security benefits of managed identity instead of API keys, Grafana Alloy gives you one collector that handles everything.
A common pattern: start with scrape jobs to prove value quickly, then migrate to the recommended production approach once you’re ready to scale.
