Wondering what Service Level Objectives (SLOs) are? In this article, we will explain service level objectives and how they relate to SLAs, SLIs, and error budgets. A Service Level Objective (SLO) is a reliability target, measured by a Service Level Indicator (SLI) and sometimes serves as a safeguard for a Service Level Agreement (SLA). SLOs represent customer happiness and guide the development team’s velocity.

Containerization has evolved from the early days of Linux control groups to out-of-the-box solutions offered by cloud providers. Market analysts expect a rise to more than 70% of global organizations using one or more containers by 2023, a huge uptick from less than 20% of them running containers for their applications in 2019.

A new case study shows how Desjardins uses Flyway Teams to standardize the way migration scripts are created and versioned across its multi-database estate, which includes Oracle, SQL Server and PostgreSQL. With assets of over $350 billion and seven million members and clients, Desjardins is the leading financial cooperative in North America.

SLIs, or service level indicators, are powerful metrics of service health. They’re often built up from simpler metrics that are monitored from the system. SLIs transform lower level machine data into something that captures user happiness. Your organization might already have processes with this same goal. Techniques like real-time telemetry and using synthetic data also build metrics that meaningfully represent service health.

Welcome back! We’re nearing the end of our five-part series, and I hope you’ve gotten the information you need as a DBA to mature your business. In this part of the series, we’ll discuss Level 4 and the importance of servicing customers and teams with the skills acquired in levels one, two, and three.

The results of our 2021 State of IT Operations Management survey are now available for the UK! Some common themes emerged with our US survey results published in April: Tool sprawl is real in IT operations departments in both countries as ops teams wrestle with multiple tools and report that legacy tools are holding them back from innovating. UK and US IT teams will both look to adopt digital operations platforms to combat tool sprawl, driven by better capabilities for AIOps and automation.

“Mean time to X” is a common term used to describe how long, on average, a particular milestone takes to achieve in incident response. There’s mean time to detect, acknowledge, mitigate, etc. And then there’s the elusive “mean time to recover,” also known as “MTTR.” MTTR, a hotly debated acronym and concept, measures how long it takes to resolve an incident on average. The problem with MTTR, though, is that it doesn’t matter.

The U.S. government is instituting stricter requirements on federal agencies and federal contractors to address cybersecurity threats. Adopting the right set of tools and practices will help organizations secure their software development supply chains and be prepared to meet these standards. However, the initial requirements also provide a valuable framework for any organization trying to reduce its security risk—not just government institutions and those doing business with them.

Last year, VMware Tanzu Mission Control introduced data protection capabilities to help enterprises safely and confidently run critical workloads on Kubernetes. With this unique feature, enterprises can centrally manage data protection on their clusters across multiple environments, easily backing up and restoring their Kubernetes clusters and namespaces.

For years, reports analyzing the evolution of the DevOps movement have been eagerly awaited by members of this growing global community. This research has helped establish benchmarks for DevOps adoption, identify best practices, and analyze DevOps outcomes—in other words, the results achieved by DevOps leaders vs. DevOps laggards. It’s interesting to see how the conversation around DevOps research has changed over the years.