AWS is constantly releasing new products and features. Your application is constantly evolving for your users. You need a fully-automated, cloud-native monitoring tool that is constantly looking for relevant events and actionable insights.
Create a new read-only IAM user or role for calls to Cloudwatch and other AWS APIs. For virtual machines and containers, install an agent to get additional coverage.
Set up notifications to match your workflow in Slack, OpsGenie, email, or others. Specify whether to receive alerts, warnings, anomalies, or a mix of events.
Watch the dashboard, Slack channels, and incident management tools for events. Use the timeline to diagnose root causes. Become all-knowing about your infrastructure overnight.
We gather baselines to understand usage patterns.
We maintain dynamic thresholds that change every minute.
We triage all events into alerts, warnings, and anomalies.
When the issue is over, we update the dashboard and notifications.
All of your resources in every region and availability zone will be discovered and monitored automatically.
ELB Unhealthy Instances
RDS Low Disk Space
Lambda Invocation Errors
EBS Burst Balance
EC2 Instance Termination
We monitor the number of healthy instances every one of your load balancers, whether it be classic (CLB), network (NLB), or application (ALB). As instances fail the health check, we’ll notify your team when it’s time to act. The event severity will depend on how many healthy instances are still receiving traffic.
Our full coverage of ELB also includes monitoring on surge queue length, bytes processed, 4XX and 5XX HTTP status codes, latency, and more.
We monitor the available disk space in your RDS cluster, EC2 instances, and Elasticsearch clusters. Consumables like disk space are projected using weighted historical averages to see how much time is left before utilization is 100%. A warning means to respond soon, and an alert means add space now.
Our full coverage of RDS also includes monitoring on replica lag, commit throughput, deadlocks, connection limit, failover events, and more.
We monitor the number of errors thrown in your Lambda functions. Each function is baselined to understand normal number of errors, and then a dynamic threshold is created that adjusts itself on a minutely basis. When you spike on errors, the system notifies you.
Our full coverage of Lambda also includes monitoring on iterator age, function duration anomalies, function timeouts, throttling, and more.
We monitor your IOPS burst balance for EBS volumes. Much like CPU Credit Balance for EC2 instances, each EBS volume has a burstable credit that it earns over time. Running out of burst capacity results in slow I/O, request timeouts, and errors to users. We’ll track your usage and balance for you.
Our full coverage of EBS also includes monitoring on IOPS throughput, volume health check status, queue length, and more.
We track your scheduled events in EC2 in a central place. Too often, the emails are lost or forgotten, and the instance dies or restarts without any notice. Calendar events are escalated from anomaly to warning to alert as the date approaches and the issues remains unresolved.
Our full coverage of scheduled events also includes EC2 scheduled restarts, scheduled terminations, RDS cluster failovers, Route53 domain expiration notices, and more.
Blue Matador is a recognized Standard Technology Partner in the AWS Partner Network.
AWS is a minefield of gotchas: service limitations, database throttling, misconfigurations, and more. As your application grows, you need a reliable method of finding what will break next.
Blue Matador finds the unknowns and notifies you about them in advance.
Zero configuration. Zero maintenance.
Nobody likes CloudWatch alarms. They’re limited in scope, time-consuming to create, and costly to adequately monitor your infrastructure.
With Blue Matador, you’re done creating CloudWatch alarms forever. All your alarms will be automatically created and maintained inside of our ML engine.
Reduce the overhead in spinning up new infrastructure — let Blue Matador do the monitoring for you. We detect new resources and create new monitors every time you:
Use AWS tags or naming rules to split your resources by environment, team, SLA requirements, or any other arbitrary grouping. Resources can belong to multiple projects and vice-versa.
Select your project (environment, team, etc) on the dashboard, timeline, or other pages to limit scope to only that project’s resources and events.
Notification channels can be specific to projects, too. Send dev notifications to email and production alerts to PagerDuty.
Hybrid environments are complex, but monitoring them doesn’t have to be. Our alert automation spans multiple public clouds and multiple accounts on the same cloud. With a single subscription, and on a single dashboard, you’ll be able to monitor:
With CloudWatch, you decide which metrics to monitor, which alarms to create, and which thresholds to set. You pick the time intervals, the missing data options, and the aggregation function. If you miss anything, it’s your fault.
With Blue Matador, you focus on delighting your users. We do the heavy lifting on monitoring. We pick the thresholds, triage the issues, and guarantee the full coverage of all your AWS resources.
Keep using your favorite notification tools. Use Blue Matador to find new events, but keep using the tools you know and love to receive notifications. Our integrations are always first-class citizens and rely on API access, not email, to deliver notifications to you. Where supported, we also send an update for the “resolve” event.
Tony Santucci Director of Technology TicketFire