Ask a software development or service desk expert these questions, and no answer would be wrong. They’d just be different and grounded in each of these experts’ experiences as all DevOps teams are not the same. There are progressive DevOps teams that have a fully integrated stack view and absolutely see the downstream enterprise implications. And there are more traditional teams that are adopting agile and have implemented DevOps in small team structures and are looking to scale. And there’s also a hybrid of the two. We’re going to focus on the last two.
ITOps and DevOps: What Keeps Them Apart
When you understand the essence of both practices, the cause of the ITOps vs. DevOps conflict becomes clear. While ITOps takes a broad view of the entire technology landscape that your organization relies on to conduct its business mission, DevOps focuses on the task at hand. DevOps teams don’t always have the visibility or awareness of the downstream implications on the enterprise stack. (And this is where can modern ITOps team can help.)
That’s not a criticism of either ITOps or DevOps. It’s just the way it is under traditional ITOM. And while the two disciplines should operate in a complementary manner, the reality is that IT environments are too often comprised of so many different elements—from on-premises legacy systems to cutting-edge cloud services—that IT management and cultural inertia keep the two apart. They are stymied by the same challenges that keep them occupied every day:
- Operational silos
- Multiple data models
- Lack of complete and contextual visibility needed to quickly diagnose and resolve the problems that arise
Data and Speed: The Heart of Conflict
What’s more, these problems and their underlying causes tend to become more acute in larger enterprises where the scale of technical heterogeneity is most evident. Why? Because DevOps teams tend to be small, agile, driven by innovation, and focused on addressing tasks in an accelerated manner. According to the Gartner report, “Don’t Fail Fast in Production; Embed Monitoring Earlier in Your DevOps Cycle,” agility is one of the top five objectives of DevOps. But DevOps teams aren’t trying to cause problems for ITOps. Their mandate for the project they are tackling at any time is typically aligned with a specific line of business.
Under traditional IT management, the data they rely on for their feedback loop is confined to the service or application they are working on. If there’s a downstream effect and they aren’t aware of it, they can’t address it. It’s up to ITOps to pick up the pieces. As the enterprise integrates more advanced technologies like cloud, microservices, containers, virtual storage, and other software-defined elements, the problem only worsens as the infrastructure managed by ITOps draws closer to the world occupied by DevOps.
DevOps and ITOps, Unified by Data
How do we get there? It starts by providing both the ITOps and DevOps teams with precise, complete, real-time, contextual data drawn from a data lake, under a common data model. When trustworthy data is the foundation for decision making, and when that data is available in real time, it allows the DevOps team to operate with a feedback loop that lets them know how the decisions they make may affect other aspects of the enterprise. And when the DevOps team pushes their code out into the enterprise, it means ITOps knows about it when it happens and understands how those changes affect all associated downstream functions.
With a common data model, sources of data can be captured and enriched between platforms across the entire IT ecosystem, ensuring continuity, enhancing automation, and creating sources of trusted data that can be leveraged by DevOps teams. Then, when the DevOps team pushes their code out into the enterprise, ITOps knows about it when it happens and understands how those changes affect all associated downstream functions.
That kind of environment can’t happen when an enterprise is reliant on legacy management platforms. Modernization requires an IT operations management platform that is designed to natively handle yesterday’s legacy technology, today’s cloud-forward technology, and whatever software-defined innovations may be introduced tomorrow. That kind of environment requires an IT operations management platform that is driven by machine learning and capable of handling the volume, variety, and velocity of data at a scale required by today’s largest global enterprises.
How do successful ITOps teams embrace DevOps? AIOps.
That kind of environment requires that enterprises evolve from traditional ITOps and adopt IT operations management powered by artificial intelligence, or AIOps. In fact, according to the Gartner report, “Augment Decision Making in DevOps Using AI Techniques,” DevOps teams that leverage AIOps platforms to deploy, monitor, and support applications will increase delivery cadence 20% by next year. AIOps is architected to support the direction of today’s cloud-native enterprises as well as those enterprise environments that are highly hybridized, containing both on-premises legacy systems and cloud and virtual components.
The fact is, the success of DevOps (and IT management’s frustration with DevOps) has put the ITOps vs. DevOps debate in stark contrast, showing the need for a shift from legacy ITOps to the current AIOps model. When you have a management platform that is intelligent enough to identify all the components of an enterprise’s infrastructure, fast enough to map their activity in real time (including ephemeral, on-demand services that may blink in and out of existence) and is able to unify all the disparate sources of data in a single model, you are able to support both ITOps and DevOps faster and more efficiently. That’s because smarter IT needs trusted data and getting that data to where it is needed, when it is needed, is foundational to the success of both camps.
And even if the unexpected happens, the time required to resolve any resulting issues will be minimized because ITOps has the necessary visibility and contextual information to diagnose and fix the problem. AIOps can even lead to the implementation of autonomous problem resolution. That is the gap that AIOps can close.
The enterprise should operate under a maturity model that takes into account a journey from traditional IT operations management to a management model that is increasingly automated—including eventually becoming fully autonomous. That maturity model recognizes that the enterprise must function as a single entity and not as a collection of individual components.
Ready to learn more about how AIOps can help your team? Read this eBook>