article thumbnail

Implementing service-level objectives to improve software quality

Dynatrace

SLOs can be a great way for DevOps and infrastructure teams to use data and performance expectations to make decisions, such as whether to release and where engineers should focus their time. Service-level objectives help teams define an acceptable level of downtime for a service or a particular issue. SLOs aid decision making.

Software 306
article thumbnail

Site reliability done right: 5 SRE best practices that deliver on business objectives

Dynatrace

How site reliability engineering affects organizations’ bottom line SRE applies the disciplines of software engineering to infrastructure management, both on-premises and in the cloud. There are now many more applications, tools, and infrastructure variables that impact an application’s performance and availability.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Perform 2023 Guide: Organizations mine efficiencies with automation, causal AI

Dynatrace

Data lakehouse architecture stores data insights in context — handbook Organizations need a data architecture that can cost-efficiently store data and enable IT pros to access it in real time and with proper context. However, turning those logs into meaningful insights requires a data lakehouse. That’s where a data lakehouse can help.

article thumbnail

Tutorial: Guide to automated SRE-driven performance engineering

Dynatrace

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.

article thumbnail

9 key DevOps metrics for success

Dynatrace

While DevOps is often referred to as “agile operations,” the widely quoted definition from Jez Humble, co-author of The DevOps Handbook, calls it “a cross-disciplinary community of practice dedicated to the study of building, evolving, and operating rapidly-changing resilient systems at scale.”

DevOps 246
article thumbnail

2017 Wheel of Fortune

J. Paul Reed

The DevOps Handbook was published last year, and I think that will put the question to eternal rest. Even though there are numerous other books (and opinions, for that matter) on the subject, I believe The DevOps Handbook will become the de facto arbiter of what officially is and is not “DevOps.” Of course, I could be wrong.

DevOps 40
article thumbnail

Smashing Podcast Episode 42 With Jeff Smith: What Is DevOps?

Smashing Magazine

And infrastructure changes. Jeff: You’re seeing this a lot more with infrastructure automation as well, right, where it’s like, “Hey, are our requests per second are reaching our theoretical maximum. Jeff: And then from there, diving into any of the DevOps handbook. What can we do to just simplify this?”

DevOps 102