Enterprise network operations teams are caught between two powerful forces: an expanding set of observability and management tools, and a rapid push to apply artificial intelligence to complex IT environments. A recent survey of 356 enterprise IT professionals found that organizations typically use six to eight observability tools, creating integration burdens, staffing demands, and visibility gaps even as AI adoption accelerates. The findings challenge the hope that AI will collapse fragmented monitoring and management platforms into a single, seamless view. Instead, the research suggests that AI can help correlate data and automate selected tasks, but it cannot by itself repair poor data quality, weak processes, or unclear tool ownership.

The survey examined how enterprises are pursuing observability unification and how AI fits into those efforts. It found that tool sprawl is not a minor inconvenience. It consumes engineering time, slows incident investigations, increases manual work, and contributes to higher total cost of ownership. At the same time, many organizations are already using AI for alert correlation, anomaly detection, incident summaries, capacity forecasting, and root-cause analysis. The most confident organizations tend to be those with centralized tool governance and mature operational practices, not necessarily those with the most advanced AI models.

Tool sprawl strains IT operations

Observability has become more complicated as applications move to hybrid cloud and multi-cloud environments, networks become more distributed, and security teams demand deeper telemetry. In response, many enterprises have adopted best-of-breed tools for different domains: network performance monitoring, application performance monitoring, cloud infrastructure monitoring, log analytics, digital experience monitoring, and security analytics. Each tool may serve a legitimate purpose, but the combined environment can become difficult to operate.

The survey found that 51% of respondents had tool unification efforts under way, while 32% were still planning or evaluating that approach and 17% had completed unification. Larger organizations reported using more observability tools across their environments. That pattern is unsurprising: larger enterprises tend to have more technology domains, more teams, more acquisitions, and more regulatory requirements. Each factor can add tools, data silos, and handoff points.

Respondents cited several ways tool sprawl affects IT teams. Forty-five percent pointed to skills and staffing burdens from operating multiple tools. Forty-four percent said integration and API complexity consume engineering time. Forty-one percent said context switching among tools slows investigations and response. Forty percent reported increased manual effort. Thirty-four percent said alert noise creates toil and cognitive overload. These are not isolated complaints. They reinforce one another: more tools mean more integrations, more integrations mean more maintenance, more maintenance means more manual work, and more manual work means less time for strategic improvement.

Tool sprawl also contributes to higher total cost of ownership, slow incident detection and resolution, inconsistent data quality, coverage gaps, and poor end-to-end visibility across technology domains. A network operations team can have tools showing that connectivity is healthy, while cloud and application teams have their own tools indicating those environments are operating normally. Yet end users may still experience a problem. Each team sees a green dashboard, but no one can correlate the signals quickly enough to recognize the anomaly behind the incident. The result is a familiar paradox: all tools report that everything is fine while the business experiences disruption.

The survey also undercuts the idea that unification means reducing the environment to one platform. One researcher summarized the reality bluntly: no one gets a single pane of glass. Enterprises may aspire to a unified experience, but the operational reality is usually a governed portfolio of tools connected by shared data, workflows, and ownership. The goal is not necessarily to eliminate every specialized tool. The goal is to make the portfolio coherent enough that teams can investigate, decide, and act without losing time to fragmentation.

Why tool sprawl persists

Tool sprawl persists for rational reasons. Specialized teams often choose tools that fit their specific workflows, data sources, and compliance needs. Cloud teams may favor native monitoring services, network teams may rely on packet-level visibility, security teams may require specialized analytics, and application teams may adopt observability platforms designed for distributed tracing. Mergers and acquisitions add another layer, bringing duplicate tools and inconsistent processes. Departmental budgets can also encourage local purchasing decisions that make sense in isolation but create integration debt at the enterprise level.

The problem is that observability data is only useful when it can be interpreted in context. A metric, log, or trace has limited value if it sits in a silo. Incidents rarely respect organizational boundaries. A user experience problem may originate in a network path, an application dependency, a cloud service, or a configuration change. If each domain has its own tool and its own data model, correlating those signals becomes a manual exercise. That is where AI is supposed to help, but AI depends on consistent, accessible, and well-governed data.

AI takes on more of the workload

Enterprises are now applying AI to operational data. In the survey, 32% of respondents said they use AI extensively across observability tools, 51% use it in selected areas, and 13% are still piloting it. Reported use cases include incident summaries and explanations, alert correlation and noise reduction, capacity forecasting, anomaly detection, predictive analytics, and root-cause analytics. These are practical applications. They focus on reducing manual analysis and helping teams prioritize what matters.

AI can help overcome data fragmentation across tools by correlating signals, summarizing incidents, and surfacing patterns that would be difficult for humans to detect at scale. But it is not a substitute for operational discipline. As one researcher noted, AI can overcome data fragmentation across tools, but it will not overcome bad data and bad operations in general. If the underlying data is incomplete, inconsistent, or poorly governed, AI may produce confident but misleading outputs. That risk grows as organizations give AI systems more autonomy.

The survey found that organizations reporting extensive AI use also expressed greater confidence in their observability unification strategies. That correlation does not prove that AI causes confidence. It may be that organizations with stronger data foundations and governance are better positioned to use AI effectively. Fragmented or inconsistent data can limit AI effectiveness, and organizations also cited concerns about inaccurate outputs and security and compliance risks. Those concerns are especially relevant when AI systems are used for incident response, capacity planning, or infrastructure changes.

Governance before unification

The research points to tool governance as a prerequisite for simplification. Problems associated with tool sprawl can compound one another, so strong governance is needed before organizations try to streamline their observability environments. Governance includes clear ownership, documented standards, procurement controls, integration requirements, and processes for retiring redundant tools. Without governance, unification efforts can become another layer of complexity rather than a remedy.

About one-quarter of organizations reported fully centralized observability tool governance, and 48% said ownership was centralized for the most part with some domain-specific exceptions. Those with centralized ownership reported greater confidence in their unification strategies, deeper integration between observability and IT service management, more effective incident-impact analysis, and more mature use of AI-powered observability. The pattern suggests that centralization helps when it creates accountability and consistency, not when it simply moves decision-making to a different group.

Centralization also means more than putting one group in charge. Understaffed tool governance and engineering teams had less success with unification strategies. A centralized group needs resources to implement standards, manage integrations, support domain teams, and deliver on its mandate. Authority without capacity can slow decisions and frustrate teams. Effective governance balances enterprise standards with domain expertise, allowing specialized teams to retain the visibility they need while reducing unnecessary duplication.

When AI starts acting on infrastructure

AI governance becomes more important when AI systems begin taking actions across network infrastructure. As enterprises give AI more autonomy, they also need to govern those systems appropriately. Agentic AI systems are probabilistic, meaning their responses and actions are not always predictable. Many traditional cybersecurity controls are designed to operate deterministically, following predefined rules. That mismatch creates new risks for network operations teams.

Consider a firewall rule that appears unnecessary to an AI system. The rule allows a particular IP address to access a database process for one day each quarter. An AI system might identify the rule as unnecessary and remove it without knowing that the rule supports a legitimate business process. To the model, it looks like a mistake or an obsolete configuration. To the business, it may be a critical exception tied to a quarterly financial process or a regulatory requirement. The example illustrates why human review remains necessary for unusual exceptions, business-critical rules, and potentially harmful or inaccurate outputs.

AI governance requires controls tailored specifically to an organization’s risk profile. Network teams need to define what AI systems can and cannot do, which actions require approval, how changes are logged, and how anomalies are escalated. Human oversight should be built into workflows, not added as an afterthought. For network operations teams, the increasing use of AI and automation requires integration of observability data and workflows, stronger tool governance, and controls over autonomous actions. The operational challenge is shifting from collecting more data to governing how that data is interpreted and acted upon.

AI is yet another tool in the operations tool chest. It is not going away, and it will continue to evolve. The organizations that benefit most will be those that treat AI as part of a broader operating model: unified data where possible, governed tools across domains, clear ownership, and human oversight where risk demands it. Tool sprawl and AI complexity are not separate problems. They meet in the same operational environment, and they require the same underlying discipline.

Source:Network World News