ELBs present over 50 options metrics during setup and operation. HealthyHostCount is just the tip of the iceberg for ensuring ELBs are healthy, yet most organizations stop monitoring at this one metric.
Blue Matador automatically alerts on HealthyHost Count, 5xx errors, lopsided zones and instances, and more.
All of them! In a managed database environment, you run the risk of unknown problems like secondary failures, replica lag, and deadlocks. Monitoring the bare-minimum is a recipe for disaster.
Blue Matador proactively monitors the cluster status, CloudWatch metrics, and engine statistics of all your RDS instances.
CPU Credits are Amazon’s way of handling oversubscribed hardware. When you run out, your access to CPU time will be throttled. 8/10 sysadmins don’t realize that CPU stealing can take place even with full CPU credits.
Our tool uses leading indicators, like CPU credit balance and steal time, to give pre-emptive, actionable alerts and warnings.
Kubernetes pods can get stuck in Pending state when the cluster doesn’t have enough resources and when there’s an issue with the specified image.
Blue Matador catches pods in pending state, broken masters, unhealthy deployments, pod limits on a node, and more.
95% of all engineers use a spreadsheet or rely on the CA’s reminder email for SSL certificate expirations. The reminder is a single point of failure that causes catastrophic results to software companies each year.
Blue Matador discovers expiring certificates in AWS ACM for ELBs, ALBs , and Cloudfront.
CloudWatch is reactive, along with most other monitoring tools. It focuses on root cause analysis, data visualization, and customized monitoring of your resources, not automated alerting.
Blue Matador is the automated alerting tool you've always wanted.
