マルチクラウド・オブザーバビリティのご紹介

Watch on-demand now

マルチクラウド・オブザーバビリティのご紹介

Watch on-demand now

On this page

Reliability Is the Test Agentic NetOps Has to Pass

It is 2:14 a.m. An agent has correlated a latency spike to an asymmetric routing condition and is ready to reroute traffic away from the affected path. The plan looks right. The only question that matters to the on-call SRE is whether to let it run, and that question is not really about the agent. It is about whether the picture the agent reasoned from is complete enough to trust at 2 a.m. with production on the line.

That instinct is the whole point. Site reliability engineers are paid to keep systems up, and that mandate shapes how they judge any new tool. An agent that drafts a plan is interesting. An agent whose actions can be trusted in production, with verification and a way to roll back, is the only version that belongs near a system an SRE answers for. Gartner® states in the Hype Cycle™ for Site Reliability Engineering, 2026: “As organizations navigate the dual pressure of maintaining mission-critical core systems while scaling AI-native infrastructure, site reliability engineering (SRE) has evolved into an essential discipline for sustaining resilience across these diverse environments.” Agentic approaches show up across this year’s Hype Cycle as part of that resilience story, and they are early. The reliability lens is what keeps the early enthusiasm honest.

Where Selector lands on the Hype Cycle

Selector is named as a Sample Vendor in the Agentic NetOps profile of the Gartner Hype Cycle for Site Reliability Engineering, 2026.

We believe what makes agentic operations safe enough for a reliability team to trust comes down to the data beneath them: a correlated picture of the network the agent can both plan against and verify against. Getting that picture trustworthy is the question Selector exists to answer.

The production bar

The honest read on this category is that it is new and largely unproven at scale. Gartner says: “Most agentic NetOps vendors have limited proven production-ready capabilities.”

For an SRE, that is not a reason to wait. It is a reason to be precise about what production-ready means, because the bar for acting on a live system is far above the bar for narrating what already happened on one.

Most of that bar is a data question. An agent acting on the network is only as reliable as its model of the network, and in most environments that model is fragmented across separate tools, formats, and teams. Gartner points: “There is also no standard for telemetry data, which means some data will be vendor-specific and not available to stand-alone vendors.”

An agent reasoning from a partial, vendor-locked model will act decisively on conditions it could not actually see. In reliability work, a confident wrong action costs more than no action, because you now have an incident plus a change to unwind.

Correlating and normalizing telemetry across domains is what turns scattered signals into one model an agent can reason over safely. It is also why vendor and infrastructure independence matter to a reliability team: a model that ends at one vendor’s coverage carries gaps into every plan, and gaps are where reliability fails.

Before you hand over the pager

If you want to be ready for agent-mediated operations without staking reliability on hype, the groundwork is unglamorous. Get cross-domain telemetry into one normalized, correlated model before evaluating any agent; that work pays off no matter which agent you adopt. Pilot where the payoff is clear and the blast radius is small. Gartner says, “Start with areas where traditional automation struggles: multisource (cross-signal) diagnostics and root cause analysis (RCA), drift and variance remediation, and change-plan generation.”

And require production evidence before autonomy: ask any vendor to show an agent planning, acting, and verifying against real conditions, with rationale you can audit and rollback you can rely on. Trust is earned by a track record, not granted by a label.

Back at 2:14 a.m., the SRE who can say yes is the one whose data was already in shape to be acted on. That preparation is reliability work in its own right, and it is worth doing before the agent ever pages you.

Stay Connected

Selector is helping organizations move beyond legacy complexity toward clarity, intelligence, and control. Stay ahead of what’s next in observability and AI for network operations:

Required disclosures

Gartner, Hype Cycle for Site Reliability Engineering, 2026, Hassan Ennaciri, Daniel Betts, Chris Saunderson, Paul Wang, 26 May 2026.

Gartner and Hype Cycle are trademarks of Gartner Inc. and/or its affiliates

Gartner does not endorse any company, vendor, product or service depicted in its publications, and does not advise technology users to select only those vendors with the highest ratings or other designation. Gartner publications consist of the opinions of Gartner’s business and technology insights organization and should not be construed as statements of fact. Gartner disclaims all warranties, expressed or implied, with respect to this publication, including any warranties of merchantability or fitness for a particular purpose.

More on our blog

On a Network, an Agent Acts Where the Blast Radius Is Largest

On a network, one change can cascade across campus, data center, WAN, and cloud. That is the stakes profile any agent inherits the moment it is allowed to act.

Reliability Is the Test Agentic NetOps Has to Pass

Agentic operations are arriving in the SRE toolkit while the category is still early. For reliability teams, the question is what makes an agent safe to trust in production.

Inside the Gartner® Market Guide for CSP Service and Network Assurance Solutions: Agentic AI and the Foundation It Runs On

Agentic AI is moving into service assurance. How far it gets depends on the data layer it runs on, which is the part most roadmaps leave underspecified.
このサイトは開発サイトとして wpml.org に登録されています。本番サイトキーに切り替えて remove this banner を実行してください。