Click here to close now.


Microservices Expo Authors: PagerDuty Blog, Liz McMillan, Derek Weeks, Elizabeth White, Ian Khan

Related Topics: Microservices Expo, Microsoft Cloud, API Journal, IoT User Interface, Agile Computing, Cloud Security

Microservices Expo: Blog Post

Your Service Level Agreement Stinks

Here’s what to look for – or avoid – in an SLA

When you're dealing with something as critical as your business infrastructure, you want to be sure that you'll get what you signed up for. If a company promises something, and you promise your colleagues something based on it, you want it to happen. That's where the service level agreement comes in. It's part of your contract that tells you what to expect and what happens if the company fails to meet those marks. Simple enough, right? Wrong.

Not all service level agreements are created equal. At a minimum, an SLA will formally define the services in a contract. In their highest forms, SLAs embody the values and capabilities of an entire organization, and they provide a clear benchmark for employee performance and customer satisfaction. If you are comparing IT service providers, it's time to set the bar high. Simply put, you want an SLA that is transparent, accountable, holistic, and logical for the provider. Here's how to spot it.

Most SLAs
Typical SLAs are buried in 20 pages of legalese. If you can find it, and cut through all the jargon, you might gain a vague idea of what will happen when your service provider fails you. And when your service experiences a disruption - which will eventually happen in one form, no matter which provider you choose - it will fall on you to translate the SLA and request credit, and of course, the company will make it as tiresome as possible to get your money.

Few customers actually get rebated by companies like this, and that, I can assure you, is a business strategy. If you provide a strong service, you don't need to hide behind a labyrinth of legal jargon. And if you are a customer, you do not want to entrust your IT infrastructure or assets with a company that is opaque, indifferent, and irresponsible.

Good providers tell their customers exactly what they're going to get, and tell them exactly what is going on at all times. This is all that customers ask. Speed, though desirable, can never compensate for unpredictability and deceptiveness. An enlightened SLA needs to detail specific, measurable commitments that tell customers what service they will receive, how quickly they're going to receive it, and what happens if they don't get that service.

Let me give a clear example from my experience with IT infrastructure hosting and cloud computing at SingleHop. We have an SLA we call the "Customer Bill of Rights." It more or less anchors every facet of our service. It is in fact an extension of our entire system. We operate on a principle called "Operational Transparency." This means that if a server goes down, we update affected clients in real time. If they wonder "have our servers gone down? If so, how long have they been down this quarter?" or "how much time do I wait for a response from tech support?" they can view a digital Report Card that details each item in their SLA and shows continuously updated data on how SingleHop is performing relative to each agreement. That is transparency. When you combine operational transparency with a detailed SLA, it turns all the usual mirrors around into clear glass.


What happens when a company messes up? Well, several things can happen:

  1. Irate customers cancel their contract.
  2. Irate customers invite their provider to a brawl in the legal ring.
  3. Irate customers watch their provider take responsibility and then respect them for it.

Everyone should prefer option #3. Cancelling a contract and shifting providers is costly and legal battles are very expensive. Migrations are dangerous and can disrupt business. You want an SLA that holds your provider accountable for any failures - be they outages or just slow responses. You should know the exact deployment time for a server and know exactly how much you will be credited if your service provider exceeds that time. You should know the expected response time from tech support, and know exactly how much you will be compensated if they take longer.

You know all this information not because you've been timing your service provider, but because they offer this information upfront. Don't work with a company that you must lasso and tie-down for a rebate.

How many interactions does the SLA cover? And, do items in the SLA conflict? For example, if an SLA promises support updates every three hours, but does not give a first response time, what good is the SLA? You could still bleed money for eight hours before getting a life raft. Great SLAs are comprehensive and holistic. They encourage customer-provider symbiosis. The best SLAs actually play into the interests of the provider - remember, they want lots of happy, sustainable customers.

As a customer, map out your anticipated interactions. If the SLA covers each interaction, it is holistic. If not, you can do or request better.

Understanding What's Not Mentioned
There are a lot of different aspects to an IaaS SLA that should but are not always mentioned. These are obvious to providers but not all customers see them right away. How fast does it take to replace a broken hard drive? Does the company keep replacement parts in stock or does it need to order them? Is there a senior tech available at all hours, and if so, how fast do escalations take? Make a list of the concerns you have, talk to people who have been through it and ask lots of questions. Sometimes when something is omitted, it's omitted for a reason.

Business Logic
Finally, a great SLA should be good for the receiver and the provider. If you are the customer, you should want transparency, accountability, and comprehensiveness to be in the interest of your service provider. Why? Because in an ideal world, you can rely on the same IT infrastructure for years and years, and frankly, that means your provider must succeed. And, if meeting the SLA is in the interest of the provider, then the provider will probably use it to evaluate their employees, sift out the bad eggs, and measure company-wide improvement. If, however, the SLA is against the interests of the company, then your provider may in fact discourage its employees from being too forthcoming and helpful.

Think about an SLA as the ‘moral' code for a company. If being "good" actual falls in line with a company's desire for profit, then that company is more likely to follow their code. If being "good" exacts cruel and unusual punishment on a company, then they will prefer to be "bad." Look for alignment between a company's interests and SLA. If they disagree, run for the hills.

Be Fruitful and Provide
A Service Level Agreement is a template for how a business intends to interact with customers. If it is transparent, accountable, holistic, and business-savvy, it is a winner. If you need a machete and $400 per hour guide to find it in the legal jungle and understand it, it is time to explore other options.

More Stories By Dan Ushman

Dan Ushman, Co-Founder and CMO of SingleHop, focuses on the company’s global marketing strategy and operations. He regularly attends and speaks at industry and marketing events. As a recognized thought leader in online marketing, Dan is one of the few internet marketing professionals to hold a Horizon Award for Marketing Innovation. When he isn’t working, he can be found in his kitchen whipping up homemade BBQ sauce, or in front of the grill with a spatula putting that sauce to work.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

@MicroservicesExpo Stories
Hiring the wrong candidate can cost a company hundreds of thousands of dollars, and result in lost profit and productivity during the search for a replacement. In fact, the Harvard Business Review has found that as much as 80 percent of turnover is caused by bad hiring decisions. But when your organization has implemented DevOps, the job is about more than just technical chops. It’s also about core behaviors: how they work with others, how they make decisions, and how those decisions translate t...
In his General Session at DevOps Summit, Asaf Yigal, Co-Founder & VP of Product at, explored the value of Kibana 4 for log analysis and provided a hands-on tutorial on how to set up Kibana 4 and get the most out of Apache log files. He examined three use cases: IT operations, business intelligence, and security and compliance. Asaf Yigal is co-founder and VP of Product at log analytics software company In the past, he was co-founder of social-trading platform Currensee, which...
People want to get going with DevOps or Continuous Delivery, but need a place to start. Others are already on their way, but need some validation of their choices. A few months ago, I published the first volume of DevOps and Continuous Delivery reference architectures which has now been viewed over 50,000 times on SlideShare (it's free to registration required). Three things helped people in the deck: (1) the reference architectures, (2) links to the sources for each architectur...
The Internet of Things (IoT) is growing rapidly by extending current technologies, products and networks. By 2020, Cisco estimates there will be 50 billion connected devices. Gartner has forecast revenues of over $300 billion, just to IoT suppliers. Now is the time to figure out how you’ll make money – not just create innovative products. With hundreds of new products and companies jumping into the IoT fray every month, there’s no shortage of innovation. Despite this, McKinsey/VisionMobile data...
Culture is the most important ingredient of DevOps. The challenge for most organizations is defining and communicating a vision of beneficial DevOps culture for their organizations, and then facilitating the changes needed to achieve that. Often this comes down to an ability to provide true leadership. As a CIO, are your direct reports IT managers or are they IT leaders? The hard truth is that many IT managers have risen through the ranks based on their technical skills, not their leadership ab...
Just over a week ago I received a long and loud sustained applause for a presentation I delivered at this year’s Cloud Expo in Santa Clara. I was extremely pleased with the turnout and had some very good conversations with many of the attendees. Over the next few days I had many more meaningful conversations and was not only happy with the results but also learned a few new things. Here is everything I learned in those three days distilled into three short points.
One of the most important tenets of digital transformation is that it’s customer-driven. In fact, the only reason technology is involved at all is because today’s customers demand technology-based interactions with the companies they do business with. It’s no surprise, therefore, that we at Intellyx agree with Patrick Maes, CTO, ANZ Bank, when he said, “the fundamental element in digital transformation is extreme customer centricity.” So true – but note the insightful twist that Maes adde...
DevOps is about increasing efficiency, but nothing is more inefficient than building the same application twice. However, this is a routine occurrence with enterprise applications that need both a rich desktop web interface and strong mobile support. With recent technological advances from Isomorphic Software and others, rich desktop and tuned mobile experiences can now be created with a single codebase – without compromising functionality, performance or usability. In his session at DevOps Su...
As organizations realize the scope of the Internet of Things, gaining key insights from Big Data, through the use of advanced analytics, becomes crucial. However, IoT also creates the need for petabyte scale storage of data from millions of devices. A new type of Storage is required which seamlessly integrates robust data analytics with massive scale. These storage systems will act as “smart systems” provide in-place analytics that speed discovery and enable businesses to quickly derive meaningf...
Using any programming framework to the fullest extent possible first requires an understanding of advanced software architecture concepts. While writing a little client-side JavaScript does not necessarily require as much consideration when designing a scalable software architecture, the evolution of tools like Node.js means that you could be facing large code bases that must be easy to maintain.
Continuous processes around the development and deployment of applications are both impacted by -- and a benefit to -- the Internet of Things trend. To help better understand the relationship between DevOps and a plethora of new end-devices and data please welcome Gary Gruver, consultant, author and a former IT executive who has led many large-scale IT transformation projects, and John Jeremiah, Technology Evangelist at Hewlett Packard Enterprise (HPE), on Twitter at @j_jeremiah. The discussion...
Discussions of cloud computing have evolved in recent years from a focus on specific types of cloud, to a world of hybrid cloud, and to a world dominated by the APIs that make today's multi-cloud environments and hybrid clouds possible. In this Power Panel at 17th Cloud Expo, moderated by Conference Chair Roger Strukhoff, panelists addressed the importance of customers being able to use the specific technologies they need, through environments and ecosystems that expose their APIs to make true ...
Microservices are a very exciting architectural approach that many organizations are looking to as a way to accelerate innovation. Microservices promise to allow teams to move away from monolithic "ball of mud" systems, but the reality is that, in the vast majority of organizations, different projects and technologies will continue to be developed at different speeds. How to handle the dependencies between these disparate systems with different iteration cycles? Consider the "canoncial problem"...
The Internet of Things is clearly many things: data collection and analytics, wearables, Smart Grids and Smart Cities, the Industrial Internet, and more. Cool platforms like Arduino, Raspberry Pi, Intel's Galileo and Edison, and a diverse world of sensors are making the IoT a great toy box for developers in all these areas. In this Power Panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists discussed what things are the most important, which will have the most profound...
PubNub has announced the release of BLOCKS, a set of customizable microservices that give developers a simple way to add code and deploy features for realtime apps.PubNub BLOCKS executes business logic directly on the data streaming through PubNub’s network without splitting it off to an intermediary server controlled by the customer. This revolutionary approach streamlines app development, reduces endpoint-to-endpoint latency, and allows apps to better leverage the enormous scalability of PubNu...
Growth hacking is common for startups to make unheard-of progress in building their business. Career Hacks can help Geek Girls and those who support them (yes, that's you too, Dad!) to excel in this typically male-dominated world. Get ready to learn the facts: Is there a bias against women in the tech / developer communities? Why are women 50% of the workforce, but hold only 24% of the STEM or IT positions? Some beginnings of what to do about it! In her Day 2 Keynote at 17th Cloud Expo, San...
In today's enterprise, digital transformation represents organizational change even more so than technology change, as customer preferences and behavior drive end-to-end transformation across lines of business as well as IT. To capitalize on the ubiquitous disruption driving this transformation, companies must be able to innovate at an increasingly rapid pace. Traditional approaches for driving innovation are now woefully inadequate for keeping up with the breadth of disruption and change facin...
I recently attended and was a speaker at the 4th International Internet of @ThingsExpo at the Santa Clara Convention Center. I also had the opportunity to attend this event last year and I wrote a blog from that show talking about how the “Enterprise Impact of IoT” was a key theme of last year’s show. I was curious to see if the same theme would still resonate 365 days later and what, if any, changes I would see in the content presented.
You may have heard about the pets vs. cattle discussion – a reference to the way application servers are deployed in the cloud native world. If an application server goes down it can simply be dropped from the mix and a new server added in its place. The practice so far has mostly been applied to application deployments. Management software on the other hand is treated in a very special manner. Dedicated resources are set aside to run the management software components and several alerting syst...
It's been a busy time for tech's ongoing infatuation with containers. Amazon just announced EC2 Container Registry to simply container management. The new Azure container service taps into Microsoft's partnership with Docker and Mesosphere. You know when there's a standard for containers on the table there's money on the table, too. Everyone is talking containers because they reduce a ton of development-related challenges and make it much easier to move across production and testing environm...