Network Management Megatrends 2022

Shamus McGillicuddy

Network operations teams are trying to establish partnerships with DevOps teams, but the process isn't easy.

The DevOps team tends to focus on the deployment and quality of applications while the network operations team focuses on network monitoring and management. While the two groups have different priorities, they see opportunities to help each other.

In its recently published Network Management Megatrends 2022 research report, Enterprise Management Associates (EMA) found that 93% of companies with a DevOps group have aligned or plan to align it closely with their network operations group. In fact, 38% expect these two groups to merge into a single unit. Another 55% expect them to establish formalized partnerships with deep collaboration.

"Our network monitoring team has team members who attend all DevOps meetings," said an IT operations manager for one of the world's largest government agencies. "It's going okay. The network monitoring team is always hammering the DevOps team, telling them they need to set up more monitoring. It goes over to varying degrees of success. DevOps always says, ‘We have customers to deal with. This can wait.' It's not at the top of their list."

Collaboration Opportunities for NetOps and DevOps

EMA's Megatrends report, based on a survey of 409 IT professionals, found three important areas of collaboration for network and DevOps groups.

1. Security policy design/implementation (51%). Network operations professionals have often told EMA that they find DevOps and CloudOps professionals to be less sophisticated with security policies. This leads to vulnerabilities and compliance violations that undermine application rollouts. A strong partnership allows the network operations team to bring its security expertise to the table and set up DevOps for success.

2. Application optimization/fail-fast iteration (42%). DevOps teams often optimize applications through a fail-fast approach, which encourages rapid iterations of application deployments where failure is expected and used as an opportunity to improve overall application design. This process requires good observability capabilities. It can also have significant impact on the network. One network engineer once told me that his DevOps team rolled out an application that was initially so inefficient in how it maintained a cache of directory information that it brought down the network every morning. He had to use packet analysis to get to the root of the problem. On the bright side, his discovery of the problem helped the DevOps team to optimize the application.

3. Network capacity planning (41%). Network operations teams need to know how the network will be used in the future to optimize network capacity. They usually do this by analyzing trends in their network monitoring tools. However, a closer relationship with DevOps could provide them more insight into how a company's application portfolio is going to evolve over time.

EMA's research found secondary interest in collaboration around application planning and design (36%) and operational monitoring (36%). Members of DevOps teams in EMA's survey were especially interested in monitoring collaboration, suggesting that the network monitoring toolset can improve overall observability for the DevOps team.

Roadblocks to Partnerships

Nothing is ever easy. And building network operations and DevOps partnerships is no exception. The Megatrends research identify five key challenges to bringing these two groups together.

1. Cross-team skills gaps (41%). These groups work with different technologies and use different tools to manage those technologies. In many cases, they is very little overlap in specialized skills. As a network security architect with a large bank told me: "They only come together when it's a proven need, and it's out of necessity due to there not being a ton of cross-training. The traditional network guys don't know a lot about the cloud."

2. Lack of tool integration (37%). Tool integrations are essential to breaking down silos. By sharing data and reports across tools, DevOps and network operations can start to understand each other's worlds and make decisions together.

3. Budget limitations (34%). Money makes the world go around. It takes money to train people, integrate tools, and devote time to building out processes for collaboration.

4. Lack of best practices and policies (33%). Many IT organizations rely on industry standard best practices to establish policies, procedures, and tooling. Such best practices are slow to establish standards in new territory, such as collaboration between these two groups. It's unknown territory for many industry experts.

5. Divided technology leadership (33%). This last issue is a tricky one. Basically, a third of research respondents told us that the DevOps team does not report up to a traditional CIO's office like network operations does. It is difficult to steer a ship with two captains. Collaboration between these silos will require collaboration at the executive level, too.

Build These Partnerships Today

Some naysayers may be unconvinced about the value of this collaboration. EMA research disagrees. In our analysis of survey data, we found that successful network operations teams are the most likely to completely erase silos between DevOps and network operations. Unsuccessful teams tend to keep more daylight between these groups. EMA believes that deep partnerships between these groups is a potential best practice moving forward.

Related Links

Hot Topics

The Latest

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...

Network Management Megatrends 2022

Shamus McGillicuddy

Network operations teams are trying to establish partnerships with DevOps teams, but the process isn't easy.

The DevOps team tends to focus on the deployment and quality of applications while the network operations team focuses on network monitoring and management. While the two groups have different priorities, they see opportunities to help each other.

In its recently published Network Management Megatrends 2022 research report, Enterprise Management Associates (EMA) found that 93% of companies with a DevOps group have aligned or plan to align it closely with their network operations group. In fact, 38% expect these two groups to merge into a single unit. Another 55% expect them to establish formalized partnerships with deep collaboration.

"Our network monitoring team has team members who attend all DevOps meetings," said an IT operations manager for one of the world's largest government agencies. "It's going okay. The network monitoring team is always hammering the DevOps team, telling them they need to set up more monitoring. It goes over to varying degrees of success. DevOps always says, ‘We have customers to deal with. This can wait.' It's not at the top of their list."

Collaboration Opportunities for NetOps and DevOps

EMA's Megatrends report, based on a survey of 409 IT professionals, found three important areas of collaboration for network and DevOps groups.

1. Security policy design/implementation (51%). Network operations professionals have often told EMA that they find DevOps and CloudOps professionals to be less sophisticated with security policies. This leads to vulnerabilities and compliance violations that undermine application rollouts. A strong partnership allows the network operations team to bring its security expertise to the table and set up DevOps for success.

2. Application optimization/fail-fast iteration (42%). DevOps teams often optimize applications through a fail-fast approach, which encourages rapid iterations of application deployments where failure is expected and used as an opportunity to improve overall application design. This process requires good observability capabilities. It can also have significant impact on the network. One network engineer once told me that his DevOps team rolled out an application that was initially so inefficient in how it maintained a cache of directory information that it brought down the network every morning. He had to use packet analysis to get to the root of the problem. On the bright side, his discovery of the problem helped the DevOps team to optimize the application.

3. Network capacity planning (41%). Network operations teams need to know how the network will be used in the future to optimize network capacity. They usually do this by analyzing trends in their network monitoring tools. However, a closer relationship with DevOps could provide them more insight into how a company's application portfolio is going to evolve over time.

EMA's research found secondary interest in collaboration around application planning and design (36%) and operational monitoring (36%). Members of DevOps teams in EMA's survey were especially interested in monitoring collaboration, suggesting that the network monitoring toolset can improve overall observability for the DevOps team.

Roadblocks to Partnerships

Nothing is ever easy. And building network operations and DevOps partnerships is no exception. The Megatrends research identify five key challenges to bringing these two groups together.

1. Cross-team skills gaps (41%). These groups work with different technologies and use different tools to manage those technologies. In many cases, they is very little overlap in specialized skills. As a network security architect with a large bank told me: "They only come together when it's a proven need, and it's out of necessity due to there not being a ton of cross-training. The traditional network guys don't know a lot about the cloud."

2. Lack of tool integration (37%). Tool integrations are essential to breaking down silos. By sharing data and reports across tools, DevOps and network operations can start to understand each other's worlds and make decisions together.

3. Budget limitations (34%). Money makes the world go around. It takes money to train people, integrate tools, and devote time to building out processes for collaboration.

4. Lack of best practices and policies (33%). Many IT organizations rely on industry standard best practices to establish policies, procedures, and tooling. Such best practices are slow to establish standards in new territory, such as collaboration between these two groups. It's unknown territory for many industry experts.

5. Divided technology leadership (33%). This last issue is a tricky one. Basically, a third of research respondents told us that the DevOps team does not report up to a traditional CIO's office like network operations does. It is difficult to steer a ship with two captains. Collaboration between these silos will require collaboration at the executive level, too.

Build These Partnerships Today

Some naysayers may be unconvinced about the value of this collaboration. EMA research disagrees. In our analysis of survey data, we found that successful network operations teams are the most likely to completely erase silos between DevOps and network operations. Unsuccessful teams tend to keep more daylight between these groups. EMA believes that deep partnerships between these groups is a potential best practice moving forward.

Related Links

Hot Topics

The Latest

How AI Agents Are Reshaping DataOps for the Always-On Enterprise

Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...

AI Deepfakes: Rethinking Trust in the Workplace

For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...

Nine in Ten Enterprises Plan Cloud Data Repatriation amid Rising Cloud Costs and Data Sovereignty Mandates

Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...

Why ITOps Need Right-Sized AI, Not Bigger Models

Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...

The End of Reactive DevOps: AI-Driven Observability for Zero-Defect Digital Systems

For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...

5 Takeaways from the Observability Forecast for Media and Entertainment

New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...

Why Moving Off the Cloud Is the Easy Part and What Comes Next Is Where Things Get Hard

Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...

MEAN TIME TO INSIGHT Podcast - Episode 24: Network Observability Tool Sprawl

In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ... 

Capacity Isn't a Guess: Observability-Driven Sizing for On-Prem Databases

In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...

5 Security Principles Every Entrepreneur Should Apply to Leadership

When most people think about cybersecurity, they picture firewalls, encryption, and access controls — technical tools designed to protect systems and data. But beneath the technology lies a deeper set of principles about trust, decision-making, and resilience ... The best leaders don't eliminate risk. They manage it intelligently. And in many ways, cybersecurity offers a surprisingly useful playbook for doing exactly that ...