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.
The Latest
Generative AI may be a great tool for the enterprise to help drive further innovation and meaningful work, but it also runs the risk of generating massive amounts of spam that will counteract its intended benefits. From increased AI spam bots to data maintenance due to large volumes of outputs, enterprise AI applications can create a cascade of issues that end up detracting from productivity gains ...
A long-running study of DevOps practices ... suggests that any historical gains in MTTR reduction have now plateaued. For years now, the time it takes to restore services has stayed about the same: less than a day for high performers but up to a week for middle-tier teams and up to a month for laggards. The fact that progress is flat despite big investments in people, tools and automation is a cause for concern ...
Companies implementing observability benefit from increased operational efficiency, faster innovation, and better business outcomes overall, according to 2023 IT Trends Report: Lessons From Observability Leaders, a report from SolarWinds ...
Customer loyalty is changing as retailers get increasingly competitive. More than 75% of consumers say they would end business with a company after a single bad customer experience. This means that just one price discrepancy, inventory mishap or checkout issue in a physical or digital store, could have customers running out to the next store that can provide them with better service. Retailers must be able to predict business outages in advance, and act proactively before an incident occurs, impacting customer experience ...
Earlier this year, New Relic conducted a study on observability ... The 2023 Observability Forecast reveals observability's impact on the lives of technical professionals and businesses' bottom lines. Here are 10 key takeaways from the forecast ...
Only 33% of executives are "very confident" in their ability to operate in a public cloud environment, according to the 2023 State of CloudOps report from NetApp. This represents an increase from 2022 when only 21% reported feeling very confident ...
The majority of organizations across Australia and New Zealand (A/NZ) breached over the last year had personally identifiable information (PII) compromised, but most have not yet modified their data management policies, according to the Cybersecurity and PII Report from ManageEngine ...