Common signals
Pods, nodes, throttling, health checks, cloud events, route changes, resource saturation, deploys, and dependency failures.
Use Cases
Cloud and Kubernetes Outages
Cloud and Kubernetes outages often require evidence from clusters, cloud APIs, logs, metrics, deployments, and ownership context. OpsRabbit can use scoped connections and infrastructure docs to investigate without giving every agent broad credentials.
What this page covers
Use AWS, Azure, GCP, OCI, Kubernetes, SSH, and monitoring connections for bounded diagnostic commands.
Attach infrastructure context that explains VPCs, clusters, node pools, service tiers, failover behavior, and ownership.
Keep destructive remediation behind approval and sandbox policy while allowing read-only diagnostics to move quickly.
Operational detail
How OpsRabbit supports Cloud and Kubernetes Outages
Cloud and Kubernetes outages often require evidence from clusters, cloud APIs, logs, metrics, deployments, and ownership context. OpsRabbit can use scoped connections and infrastructure docs to investigate without giving every agent broad credentials.
Credential design
Prefer least-privilege cloud roles, scoped Kubernetes contexts, and named environment-specific connections.
Outcome
A useful investigation names the failing layer, affected workloads, likely trigger, rollback path, and validation commands.
Related pages