Essay:

You Don’t Need to Be “Modern” to Apply AI in IT Ops

By Vishnu Rajkumar

Jun 10, 20253 min read#ai#it-ops#operations#governance

Originally published on linkedin

You Don’t Need to Be “Modern” to Apply AI in IT Ops

There’s a myth echoing through boardrooms and “transformation” slide decks: - “We have to modernize the whole stack before we touch AI in operations.”

Sounds sensible. It isn’t. AI isn’t the garnish on a pristine, cloud‑native dessert. It’s the Zero‑to‑One hammer that smashes legacy bloat and rebuilds what actually matters.

Most firms think AI is Phase 2. Reality check: AI is the way you get to Phase  2.

Digital SRE: Reliability That Thrives in Chaos

“Digital SRE” puts an AI co‑pilot next to your ops team. No one waits for every service to be containerised or event‑driven; they work with the mess that’s already there:

Half‑documented cron jobs no one owns Monitoring tools from 2008 that flood inboxes at 3 a.m. Logs in seven formats (none of them friendly)

AI digs through that noise, stitches events into a story, and suggests; sometimes triggers fixes ranked by business impact. The people stay in charge; the machines supply context, speed, and muscle.

Resilience Isn’t Reserved for the Modern

We’ve heard “self‑healing” for years. The new twist? You don’t need to rebuild to get it—you could wrap it around what you’ve got.

Lightweight agents watch for degradation patterns and restart components before users notice. ML models flag failing dependencies and flip circuit breakers automatically.

No service mesh? No problem. You need:

Intent – decide which failures matter. Visibility – get the right telemetry. Permission – let the agent act.

That’s not aspirational architecture. That’s pragmatic ROI.

AI Ops Agents Don’t Need Fancy Infrastructure

Today’s AI Ops agents aren’t brittle, rigid, static scripts. They reason. They connect dots across fractured systems, surface meaningful patterns, and trigger actions; whether you run Kubernetes or not.

We've agents SSH into legacy VMs, parse logs, and restart hung services based on anomaly detection. It’s not cutting-edge on paper, but it’s transformative in practice.

All these agents need are APIs, logs, CLI access, and permission to help. They don’t care if your setup is cloud-native, hybrid, or duct-taped together. They’re designed to meet you where you are.

AI Ops Agents: Blue‑Collar Intelligence

Today’s agents are not brittle scripts; they reason.

Map failure domains across cloud, on‑prem, and “please‑don’t‑ask” legacy boxes. Recommend and, when you allow, execute remediations. Learn from each incident to get faster next time.

We’ve agents SSH into creaky VMs, parse syslogs, kill zombie processes, and restart services. Not flashy. Pure impact.

Give them logs, APIs, a CLI, and a green light. They’ll meet you where you are; Kubernetes or cobwebs.

If you’re waiting for your infrastructure to be “modern enough” to apply AI, you’re missing the point.

AI isn’t the reward at the end of a transformation. It’s the lever that drives it. It helps teams move faster, act smarter, and close the reliability gap without waiting for a perfect stack.

Stop chasing a clean slate. Start building an intelligent one.

Originally published on LinkedIn

WRITTEN BY

Vishnu Rajkumar

Vishnu leads AI engineering at Microland and writes about artificial intelligence, systems, judgment, work and technological change.

About the author →