Skip to main content

DevOps and AIOps: Developing A New Culture

Will Cappelli
Moogsoft

In today's competitive landscape, businesses must have the ability and process in place to face new challenges and find ways to successfully tackle them in a proactive manner. For years, this has been placed on the shoulders of DevOps teams within IT departments. But, as automation takes over manual intervention to increase speed and efficiency, these teams are facing what we know as IT digitization. How has this changed the way companies function over the years, and what do we have to look forward to in the coming years?

While this all began with the introduction of the Internet in the late 90s, it took a turn after the economic crash in 2007. At this time, automation became the main driver of innovation and a key focus to support revenue. Now, in today's landscape, if automation is not a top concern for IT teams and doesn't sit at the heart of IT strategies, companies risk losing their competitive edge, ultimately resulting in failure.

There has also been an increase in demand over the last decade for IT to have more of a proactive approach to technological pivots, and the pressure to respond quickly has grown. Because of this, development teams have taken the lead to change the role of the IT department within the business by positioning IT as a strategic revenue driver. DevOps within IT departments has also come a long way. Specifically, there are three major changes within these teams worth spotlighting.

For starters, departments were adopting agile development practices to speed up the delivery of creation changes into the production environment. Then, DevOps introduced automation into change delivery.

The final step after accepting the two previous changes, is the alignment of development and operations teams. In the past, DevOps and operations have worked separately: DevOps managed the development, while operations handled the environment. But, as automation takes a more prominent role in companies, it becomes essential that these two teams align. It's no longer feasible to have them in two siloed playing fields.

Joining these teams hasn't been easy. There's been resistance in aligning efforts and daily communication between the two continues to be an issue. It has been a challenge for IT operations to interact with the development team so closely. DevOps has struggled to see the value of managing the production environment, as they often believe the task to be low-level and straightforward. In addition, the perspective that DevOps has on infrastructure is narrow-minded and they're typically only invested in direct projects that relate to them. What this logic fails to address is that fact that no application is completely isolated. Every application is living in an environment of shared resources that all influence each other. Unfortunately, because of these lack of understandings, DevOps and operations remain largely siloed. The collaboration that needs to happen hasn't yet happened.

So, what role does automation have in this struggling relationship? For starters, we know that in order for a new module or application to move from development environment to the real-world production environment, certain steps need to be taken. In the past, these steps have been completed manually. But, with today's automation, humans are taken completely out of the equation, presenting an opportunity for AIOps technologies to execute the process from development to production much faster, smarter, and more efficiently.

With the proper tools in place, algorithms can take data from the production environment, understand the disposition of resources within that environment, and ensure the new application or change being delivered has enough of the right resources to support itself, rather than pulling resources from other applications. This is feasible with automation.

There are two stages to the automation process.

The first stage is automating the path from development to production. This could include AIOps features like pattern discovery, anomaly detection, and causal analysis. In this case, however, AIOps features are applied when allocating resources and understanding when new will be delivered into the production environment.

The second stage of automation comes into play when there is a new element in the production environment. What started as three changes a week has now reached three thousand because of the number being delivered into the environment through automation. Additionally, automation causes an increase in the modularity, ephemeralness, and IT systems are more distributed, making it nearly impossible to predict what kind of impact a new change will have on a production environment. With the proper AIOps technology in place, it becomes easier to foresee these implications.

The amount of data in today's business landscape only continues to increase. Without an analytical or diagnostic tool, development and operations teams are finding it nearly impossible to comprehend the performance of the production environment and to action events. This is when the role of AIOps becomes incredibly important and can save teams from severe consequences. Without the proper automation tools and strategy, companies will collapse as they become increasingly blind to system performance.

Will Cappelli is Field CTO at Moogsoft

Hot Topics

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

DevOps and AIOps: Developing A New Culture

Will Cappelli
Moogsoft

In today's competitive landscape, businesses must have the ability and process in place to face new challenges and find ways to successfully tackle them in a proactive manner. For years, this has been placed on the shoulders of DevOps teams within IT departments. But, as automation takes over manual intervention to increase speed and efficiency, these teams are facing what we know as IT digitization. How has this changed the way companies function over the years, and what do we have to look forward to in the coming years?

While this all began with the introduction of the Internet in the late 90s, it took a turn after the economic crash in 2007. At this time, automation became the main driver of innovation and a key focus to support revenue. Now, in today's landscape, if automation is not a top concern for IT teams and doesn't sit at the heart of IT strategies, companies risk losing their competitive edge, ultimately resulting in failure.

There has also been an increase in demand over the last decade for IT to have more of a proactive approach to technological pivots, and the pressure to respond quickly has grown. Because of this, development teams have taken the lead to change the role of the IT department within the business by positioning IT as a strategic revenue driver. DevOps within IT departments has also come a long way. Specifically, there are three major changes within these teams worth spotlighting.

For starters, departments were adopting agile development practices to speed up the delivery of creation changes into the production environment. Then, DevOps introduced automation into change delivery.

The final step after accepting the two previous changes, is the alignment of development and operations teams. In the past, DevOps and operations have worked separately: DevOps managed the development, while operations handled the environment. But, as automation takes a more prominent role in companies, it becomes essential that these two teams align. It's no longer feasible to have them in two siloed playing fields.

Joining these teams hasn't been easy. There's been resistance in aligning efforts and daily communication between the two continues to be an issue. It has been a challenge for IT operations to interact with the development team so closely. DevOps has struggled to see the value of managing the production environment, as they often believe the task to be low-level and straightforward. In addition, the perspective that DevOps has on infrastructure is narrow-minded and they're typically only invested in direct projects that relate to them. What this logic fails to address is that fact that no application is completely isolated. Every application is living in an environment of shared resources that all influence each other. Unfortunately, because of these lack of understandings, DevOps and operations remain largely siloed. The collaboration that needs to happen hasn't yet happened.

So, what role does automation have in this struggling relationship? For starters, we know that in order for a new module or application to move from development environment to the real-world production environment, certain steps need to be taken. In the past, these steps have been completed manually. But, with today's automation, humans are taken completely out of the equation, presenting an opportunity for AIOps technologies to execute the process from development to production much faster, smarter, and more efficiently.

With the proper tools in place, algorithms can take data from the production environment, understand the disposition of resources within that environment, and ensure the new application or change being delivered has enough of the right resources to support itself, rather than pulling resources from other applications. This is feasible with automation.

There are two stages to the automation process.

The first stage is automating the path from development to production. This could include AIOps features like pattern discovery, anomaly detection, and causal analysis. In this case, however, AIOps features are applied when allocating resources and understanding when new will be delivered into the production environment.

The second stage of automation comes into play when there is a new element in the production environment. What started as three changes a week has now reached three thousand because of the number being delivered into the environment through automation. Additionally, automation causes an increase in the modularity, ephemeralness, and IT systems are more distributed, making it nearly impossible to predict what kind of impact a new change will have on a production environment. With the proper AIOps technology in place, it becomes easier to foresee these implications.

The amount of data in today's business landscape only continues to increase. Without an analytical or diagnostic tool, development and operations teams are finding it nearly impossible to comprehend the performance of the production environment and to action events. This is when the role of AIOps becomes incredibly important and can save teams from severe consequences. Without the proper automation tools and strategy, companies will collapse as they become increasingly blind to system performance.

Will Cappelli is Field CTO at Moogsoft

Hot Topics

The Latest

Automation often starts with the people closest to an immediate need. A developer may schedule a script with cron or Amazon EventBridge Scheduler; a business team may adopt an RPA bot, low-code platform, or agent. Many tools stay useful within one domain. Some become consequential across organizational boundaries because other systems and teams depend on them or business outcomes rely on their timing and recovery. Those cases may call for broader coordination ...

The conventional wisdom in our industry says that AI demands a new operating model and specific data tailored for it. I disagree. AI is changing the rules, but not in the way people think ...

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...