Enabling SLA Measurement with Armory Spinnaker

Oct 24, 2017 by Ben Mappen

One of Spinnaker’s core value propositions is the ability to perform safe & repeatable deployments. But how do you know if a deployment is truly safe?

A common approach to quantifying an application’s general health is with an SLA (service level agreement). To measure how safe a deployment is, we can look at the delta in SLA before and after a given deployment. And, over time, we’d hope to see your service’s SLA increase as we add automation and implement best practices for deployments, monitoring, and testing.

We’ve implemented a turn-key SLA measurement service directly within Armory Spinnaker in order to ensure you are constantly improving the safety of your deployments.

To calculate SLA, we look at uptime, response time, and error rates within CloudWatch. At some regular interval (default is every minute), we’ll check to see if those three metrics are within your specified thresholds, and if all three pass then you are within your SLA for that time interval. If any one of the tests fail, you are NOT within your SLA for that time interval. The overall SLA score is simply the percentage of time intervals that are within SLA divided by total intervals.

Here’s how you configure the thresholds for your SLA.

alt

Once you configure your SLA for each application, here’s what your SLA dashboard will look like:

alt

How to Enable the SLA Feature

  1. Add SLA_ENABLED=true to your prod.env file
  2. Restart Spinnaker with this command service armory-spinnaker restart (or by redeploying Spinnaker with your Spinnaker Deploy Spinnaker pipeline)

Roadmap

We realize that not every application’s SLA can be effectively quantified with just uptime, response time, and error rate. You may want to look at custom metrics or perform other types of tests to truly determine if your service is available. In future versions of this service, we will allow you to define additional metrics that contribute to your SLA.

Learn More

Let us know in the form below if there are specific types of metrics that you’d like to see us add.

Recently Published Posts

How Armory Uses Makelog to Drive New Feature Adoption from Day One

Jun 23, 2022

original post For teams that practice CI/CD and ship multiple times a day, waiting weeks to communicate these updates to customers defeats the purpose. After all, if a feature ships and nobody knows about it, did it really ship? You miss out on delivering value to customers sooner, learning which features they’re most excited about, […]

Read more

Armory Continuous Deployment-as-a-Service is Now Available

Jun 6, 2022

Over the last two years, our customers and prospects have said one thing: everyone wants Continuous Deployment, but adopting CD to production is too hard for many companies. Today we’re excited to announce that Armory is making production-grade continuous deployment available to all users of Kubernetes, regardless of size. Armory Continuous Deployment-as-a-Service has been in […]

Read more

Introducing OpenCost—An Open Source Project for Monitoring Kubernetes Spend

Jun 2, 2022

We are excited to share the launch of OpenCost, an open source project that provides real-time cost monitoring for teams running Kubernetes workloads.   As container and Kubernetes adoption continues to grow, navigating the complexities around measuring and allocating cost is becoming a business-critical challenge. A recent CNCF survey showed overspend is increasingly a problem for […]

Read more