Skip to main content

How ITOps Can Adapt to the New Normal - Part 5

APMdigest posed the following question to the IT Operations community: How should ITOps adapt to the new normal? In response, industry experts offered their best recommendations for how ITOps can adapt to this new remote work environment. Part 5, the final installment in the series, covers open source and emerging technologies.

Start with: How ITOps Can Adapt to the New Normal - Part 1

Start with: How ITOps Can Adapt to the New Normal - Part 2

Start with: How ITOps Can Adapt to the New Normal - Part 3

Start with: How ITOps Can Adapt to the New Normal - Part 4

OPEN SOURCE

Although 2020 has been a year of change, ITOps teams have been building for scale for quite some time, and our teams have become more distributed than ever. By utilizing new capabilities in cloud native architectures, where observability is embedded in our open source stacks teams have more options than ever. Open source is the new normal.
Jonah Kowall
CTO, Logz.io

EMERGING TECHNOLOGIES

We should ensure the teams are up to date with new emerging technologies. While the new norm influences our physical presence, technology continues to progress and we want our team to have the ability to learn, develop and find ways to advance the organization (and themselves) by leveraging new technologies and solutions. The organization should assist the Ops engineers in being up to date from this perspective as well.
Ziv Oren
Chief Delivery Officer, Aqua Security

SAAS

The new normal already has large parts of the workforce WFH and away from the office. ITOps teams will continue to focus on organizational solutions that provide stability and easy integration into pre-existing environments. This gives an advantage to SaaS solutions, which can be updated remotely, typically with high uptimes.
Russell Rothstein
Founder and CEO, IT Central Station

PUBLIC CLOUD IAAS

COVID-19 has dramatically amplified several existing trends and needs across teams. For ITOps, I think it has shown the importance of the move to Public Cloud IaaS — which means a reduction in their role, but it's the only route to scale/reliability. Where ITOps do still run systems, the mass migration to remote working has forever changed the infrastructure needs and cadence of evolution. Although most of what the team does can be done remotely, as everyone has moved to WFH, there is a considerable impact on the SREs and ITOps teams that manage the infrastructure data centers. They need to work in capsules to not to infect each other and maintain a working force that physically administers the data center. All clouds are basically physical servers that need maintenance at the end of the day.
Avishai Sharlin
Division President, Amdocs Technology

SDWAN

One key to navigating these challenging times is for ITOps to look at underlying network infrastructure to make sure it can handle the evolving demands of the business, and then plan a network upgrade in a way that's not disruptive to the business. Many organizations have turned to SD-WAN as the answer — and rightly so, because it provides a way to control application performance while centralizing and simplifying network and resource management. However, pretty much all SD-WAN vendors require an overhaul of the network infrastructure in order to implement, which is time-consuming, costly, disruptive, and slow to deliver results. Our recommendation is that ITOps consider a solution that doesn't require re-engineering of the network. Take advantage of transparent hybrid technologies in order to gain the application performance and network management benefits of SD-WAN immediately (rather than the typical 6-18+ months you'd be looking at with most solutions), without having to re-architect the network. The ideal SD-WAN solution enables a « hands-free » migration, which involves placing a device that is essentially invisible to the network and delivers instant end-to-end application visibility and control. Meanwhile, the business can migrate to a complete SD-WAN at their own pace, avoiding the risk, disruption, and delayed ROI associated with a complex network project. Additionally, the enterprise should consider whether an SD-WAN solution offers multi-cloud capabilities and supports work from home scenarios, because in the long term ,the network edge is expanding beyond the physical boundaries of the corporate perimeter. Lastly, cost flexibility is essential; the enterprise should insist on consumption-based pricing models in order to control costs and maintain flexibility as they grow or shift workloads and sites up or down. Ultimately, ITOps needs a network that can grow and scale with the business, as they adapt to unpredictable circumstances facing their business today and beyond.
Zabrina Doerck
Director of Product Marketing, Infovista

FULL-STACK SCALABILITY

The move to 100% remote ITOps underscores the importance of reliable, scalable, automatable infrastructure up and down the stack. Every part of your application stack, particularly the oft-overlooked foundational parts (think: servers, load balancers, VPNs, DNS), need to be just as agile and easy to deploy, update, and scale as your core application. This will enable you to react to changing business needs rapidly. The ability to scale your internal back-office application by 10x in 10 minutes is fantastic, but if none of your employees can access the system because your VPNs are overloaded, you've got a problem. Take the opportunity to look at every piece of software and hardware that powers your business and ask: "How agile and fragile is this?" "How does it scale?" "How can it be automated?" Because when it comes time to deliver on new goals and KPIs in the future, companies that have invested in making their entire stack more reliable and scalable will have a massive advantage.
Jonathan Sullivan
CTO, NS1

The Latest

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...

How ITOps Can Adapt to the New Normal - Part 5

APMdigest posed the following question to the IT Operations community: How should ITOps adapt to the new normal? In response, industry experts offered their best recommendations for how ITOps can adapt to this new remote work environment. Part 5, the final installment in the series, covers open source and emerging technologies.

Start with: How ITOps Can Adapt to the New Normal - Part 1

Start with: How ITOps Can Adapt to the New Normal - Part 2

Start with: How ITOps Can Adapt to the New Normal - Part 3

Start with: How ITOps Can Adapt to the New Normal - Part 4

OPEN SOURCE

Although 2020 has been a year of change, ITOps teams have been building for scale for quite some time, and our teams have become more distributed than ever. By utilizing new capabilities in cloud native architectures, where observability is embedded in our open source stacks teams have more options than ever. Open source is the new normal.
Jonah Kowall
CTO, Logz.io

EMERGING TECHNOLOGIES

We should ensure the teams are up to date with new emerging technologies. While the new norm influences our physical presence, technology continues to progress and we want our team to have the ability to learn, develop and find ways to advance the organization (and themselves) by leveraging new technologies and solutions. The organization should assist the Ops engineers in being up to date from this perspective as well.
Ziv Oren
Chief Delivery Officer, Aqua Security

SAAS

The new normal already has large parts of the workforce WFH and away from the office. ITOps teams will continue to focus on organizational solutions that provide stability and easy integration into pre-existing environments. This gives an advantage to SaaS solutions, which can be updated remotely, typically with high uptimes.
Russell Rothstein
Founder and CEO, IT Central Station

PUBLIC CLOUD IAAS

COVID-19 has dramatically amplified several existing trends and needs across teams. For ITOps, I think it has shown the importance of the move to Public Cloud IaaS — which means a reduction in their role, but it's the only route to scale/reliability. Where ITOps do still run systems, the mass migration to remote working has forever changed the infrastructure needs and cadence of evolution. Although most of what the team does can be done remotely, as everyone has moved to WFH, there is a considerable impact on the SREs and ITOps teams that manage the infrastructure data centers. They need to work in capsules to not to infect each other and maintain a working force that physically administers the data center. All clouds are basically physical servers that need maintenance at the end of the day.
Avishai Sharlin
Division President, Amdocs Technology

SDWAN

One key to navigating these challenging times is for ITOps to look at underlying network infrastructure to make sure it can handle the evolving demands of the business, and then plan a network upgrade in a way that's not disruptive to the business. Many organizations have turned to SD-WAN as the answer — and rightly so, because it provides a way to control application performance while centralizing and simplifying network and resource management. However, pretty much all SD-WAN vendors require an overhaul of the network infrastructure in order to implement, which is time-consuming, costly, disruptive, and slow to deliver results. Our recommendation is that ITOps consider a solution that doesn't require re-engineering of the network. Take advantage of transparent hybrid technologies in order to gain the application performance and network management benefits of SD-WAN immediately (rather than the typical 6-18+ months you'd be looking at with most solutions), without having to re-architect the network. The ideal SD-WAN solution enables a « hands-free » migration, which involves placing a device that is essentially invisible to the network and delivers instant end-to-end application visibility and control. Meanwhile, the business can migrate to a complete SD-WAN at their own pace, avoiding the risk, disruption, and delayed ROI associated with a complex network project. Additionally, the enterprise should consider whether an SD-WAN solution offers multi-cloud capabilities and supports work from home scenarios, because in the long term ,the network edge is expanding beyond the physical boundaries of the corporate perimeter. Lastly, cost flexibility is essential; the enterprise should insist on consumption-based pricing models in order to control costs and maintain flexibility as they grow or shift workloads and sites up or down. Ultimately, ITOps needs a network that can grow and scale with the business, as they adapt to unpredictable circumstances facing their business today and beyond.
Zabrina Doerck
Director of Product Marketing, Infovista

FULL-STACK SCALABILITY

The move to 100% remote ITOps underscores the importance of reliable, scalable, automatable infrastructure up and down the stack. Every part of your application stack, particularly the oft-overlooked foundational parts (think: servers, load balancers, VPNs, DNS), need to be just as agile and easy to deploy, update, and scale as your core application. This will enable you to react to changing business needs rapidly. The ability to scale your internal back-office application by 10x in 10 minutes is fantastic, but if none of your employees can access the system because your VPNs are overloaded, you've got a problem. Take the opportunity to look at every piece of software and hardware that powers your business and ask: "How agile and fragile is this?" "How does it scale?" "How can it be automated?" Because when it comes time to deliver on new goals and KPIs in the future, companies that have invested in making their entire stack more reliable and scalable will have a massive advantage.
Jonathan Sullivan
CTO, NS1

The Latest

Most organizations approach OpenTelemetry as a collection of individual tools they need to assemble from scratch. This view misses the bigger picture. OpenTelemetry is a complete telemetry framework with composable components that address specific problems at different stages of organizational maturity. You start with what you need today and adopt additional pieces as your observability practices evolve ...

One of the earliest lessons I learned from architecting throughput-heavy services is that simplicity wins repeatedly: fewer moving parts, loosely coupled execution (fewer synchronous calls), and precise timing metering. You want data and decisions to travel the shortest possible path. The goal is to build a system where every strategy and each line of code (contention is the key metric) complements the decision trees ...

As discussions around AI "autonomous coworkers" accelerate, many industry projections assume that agents will soon operate alongside human staff in making decisions, taking actions, and managing tasks with minimal oversight. But a growing number of critics (including some of the developers building these systems) argue that the industry still has a long way to go to be able to treat AI agents like fully trusted teammates ...

Enterprise AI has entered a transformational phase where, according to Digitate's recently released survey, Agentic AI and the Future of Enterprise IT, companies are moving beyond traditional automation toward Agentic AI systems designed to reason, adapt, and collaborate alongside human teams ...

The numbers back this urgency up. A recent Zapier survey shows that 92% of enterprises now treat AI as a top priority. Leaders want it, and teams are clamoring for it. But if you look closer at the operations of these companies, you see a different picture. The rollout is slow. The results are often delayed. There's a disconnect between what leaders want and what their technical infrastructure can handle ...

Kyndryl's 2025 Readiness Report revealed that 61% of global business and technology leaders report increasing pressure from boards and regulators to prove AI's ROI. As the technology evolves and expectations continue to rise, leaders are compelled to generate and prove impact before scaling further. This will lead to a decisive turning point in 2026 ...

Cloudflare's disruption illustrates how quickly a single provider's issue cascades into widespread exposure. Many organizations don't fully realize how tightly their systems are coupled to thirdparty services, or how quickly availability and security concerns align when those services falter ... You can't avoid these dependencies, but you can understand them ...

If you work with AI, you know this story. A model performs during testing, looks great in early reviews, works perfectly in production and then slowly loses relevance after operating for a while. Everything on the surface looks perfect — pipelines are running, predictions or recommendations are error-free, data quality checks show green; yet outcomes don't meet the ground reality. This pattern often repeats across enterprise AI programs. Take for example, a mid-sized retail banking and wealth-management firm with heavy investments in AI-powered risk analytics, fraud detection and personalized credit-decisioning systems. The model worked well for a while, but transactions increased, so did false positives by 18% ...

Basic uptime is no longer the gold standard. By 2026, network monitoring must do more than report status, it must explain performance in a hybrid-first world. Networks are no longer just static support systems; they are agile, distributed architectures that sit at the very heart of the customer experience and the business outcomes ... The following five trends represent the new standard for network health, providing a blueprint for teams to move from reactive troubleshooting to a proactive, integrated future ...

APMdigest's Predictions Series concludes with 2026 AI Predictions — industry experts offer predictions on how AI and related technologies will evolve and impact business in 2026. Part 5, the final installment, covers AI's impacts on IT teams ...