This site uses cookies to improve your experience. By viewing our content, you are accepting the use of cookies. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country we will assume you are from the United States. View our privacy policy and terms of use.

Remove Availability Remove Azure Remove DevOps Remove Handbook
article thumbnail

Lessons learned from enterprise service-level objective management

Dynatrace

MAY 19, 2022

Every organization’s goal is to keep its systems available and resilient to support business demands. A service-level objective ( SLO ) is the new contract between business, DevOps, and site reliability engineers (SREs). In this case, the customer offers a managed service that runs on Amazon Web Services, Microsoft Azure, and Google.

Automotive 270
Automotive Latency Architecture Azure 270
article thumbnail

Tutorial: Guide to automated SRE-driven performance engineering

Dynatrace

MAY 28, 2020

While Google’s SRE Handbook mostly focuses on the production use case for SLIs/SLOs, Keptn is “Shifting-Left” this approach and using SLIs/SLOs to enforce Quality Gates as part of your progressive delivery process. Dynatrace however not just gives us the standard SLO metrics based on Google’s SRE handbook.

Engineering 192
Engineering Performance Metrics Best Practices 192
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

 

Stay Connected

Join 5,000+ Insiders by signing up for our newsletter

About
About
Editions
Editions
Topics
Powered by Aggregage | Terms and Conditions | Your California Rights and Privacy Policy
© Aggregage 2024