Blue Matador proactively monitors your AWS infrastructure
Our proactive monitoring engine is built to find these six different categories of events.
Calendar events can always be planned for, because there is a known date associated with them.
Outlier events are generated from metrics that don’t match your normal usage by hour, day, and week.
Hard Limit Events
Hard limits can be high (100% full) or low (0 memory), but can always be projected and anticipated.
Static Threshold Events
Static thresholds measure a known bad state in your infrastructure, regardless of use case.
System Status Events
System status events track known bad states, similar to static thresholds, but don’t have an associated metric.
Config events happen when configuration doesn’t match the recommended values.
Onboarding with Blue Matador is easy: 1) connect your AWS accounts using read-only IAM credentials, 2) optionally install our agent on your servers, and 3) integrate your team’s notification providers like Pagerduty or Slack.
That’s it. It takes about 15 minutes.
With reactive monitoring tools, you also have to specify which metrics to monitor, get your own baselines, create alerts, and get endlessly granular to avoid false positives. With Blue Matador’s proactive monitoring, we do that work for you, and the result is far better.
Some notifications require immediate attention, but most don’t. This is the source of alert fatigue in most organizations. An SSL certificate expiring in 30 days shouldn’t have the same urgency as a primary database server losing connectivity.
To handle this, Blue Matador has three notification urgencies.
Our proactive monitoring tool reduces your millions of metrics and billions of data points to a simple set of outliers. We don’t show metrics from your app, they give false security in the form of a needle-in-the-haystack problem for humans.
The timeline view reduces the search space for root-cause analysis.
Our timeline shows only a manageable list of alerts, warnings, and anomalies, which can be scrolled through in minutes. When your system is healthy, the timeline reports nothing. Listing issues in this way is the best possible way to look for leads on your root cause analyses.
Managing your monitoring tools can be fun, but ultimately decreases your efficiency as an engineer. So, our dashboard, as with our alerts, come pre-configured and ready to go.
Our dashboard builds awareness of production.
From our account-wide SSI™ score, to the rotating set of current issues, and the status of current integrations, our dashboard was built to increase awareness of production in dev teams and operations teams.