#179: For many decades, the use of service level objectives (SLOs) in IT has been a routine part of day-to-day business. The objectives are based on measurable impacts that each individual customer or operational unit should experience with a specific IT service. These SLOs are typically associated with costs and benefits that can be tracked over time.
But what do you need to do if you are new to SLOs? What are the pitfalls associated with introducing SLOs into an environment where they have not yet been a part of the culture? For those of you that have been working with IT for any length of time, there has probably been one idea in the IT space that has received more flak from different teams than anything else. Many people and teams still do not understand what SLOs are, how to use them and why some companies use them and others do not.
In this episode, we speak with Brian Singer, the Chief Product Officer at Nobl9, about the mechanics of implementing and maintaining SLOs in your organization.
Brian’s contact information:
Twitter: https://twitter.com/brian_singer
LinkedIn: https://www.linkedin.com/in/briantsinger/
YouTube channel:
https://youtube.com/devopsparadox/
Books and Courses:
Catalog, Patterns, And Blueprints
https://www.devopstoolkitseries.com/posts/catalog/
Review the podcast on Apple Podcasts:
https://www.devopsparadox.com/review-podcast/
Slack:
https://www.devopsparadox.com/slack/
Connect with us at:
Flere episoder fra "DevOps Paradox"
Gå ikke glip af nogen episoder af “DevOps Paradox” - abonnér på podcasten med gratisapp GetPodcast.
