Monitoring & Observability across clouds
The native metrics, logs and alerting baseline for each cloud, wired up rather than left at defaults.
3 verified modules, 2 of them live-tested apply→verify→destroy; the rest are static-validated, live-test pending.
Compare by provider
| Provider | Module | Verification |
|---|---|---|
| AWS | CloudWatch Logs, Alarm & Dashboard | ✓ live-tested |
| Azure | Azure Monitor & Log Analytics Baseline | ✓ live-tested |
| Google Cloud | Cloud Monitoring, Alerting & Log Export | static-validated |
How to choose
Start with the native service whatever else you run: it already collects the control-plane signals no third party can see, and it is the only place some of them exist. Add an external tool on top when you need correlation across clouds or longer retention than the native tier gives.
When not to use
Native monitoring is per-cloud by construction. Run in two clouds and neither of these gives you one view; that is the problem an external tool is actually solving.
Other solutions
Managed Relational Database18Managed Kubernetes15Virtual Machines13Messaging & Pub/Sub11Load Balancer10DNS & Traffic Management10Virtual Private Cloud (VPC)9Serverless Containers7Secrets & Key Management7Serverless Functions6Object Storage5API Gateway5Identity & Access5Container Registry3CDN & Edge Delivery3In-Memory Cache3WAF & Edge Security3Shared File Storage3