# Why ITOps needs a governed automation foundation for AI

DevFeed: [Why ITOps needs a governed automation foundation for AI](<https://devfeed.tech/articles/why-itops-needs-a-governed-automation-foundation-for-ai-107423.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/why-itops-needs-governed-automation-foundation-ai>)

Author: Chad Zammar

Published: 2026-10-29T00:00:00Z

Content type: opinion

Language: en

Sources: [Red Hat Blog](<https://devfeed.tech/sources/red-hat-blog.md>)

Topics: [Automation](<https://devfeed.tech/topics/automation.md>), [AI in IT operations](<https://devfeed.tech/topics/ai-in-it-operations.md>), [Production Engineering](<https://devfeed.tech/topics/production-engineering.md>), [redhat](<https://devfeed.tech/topics/redhat.md>)

Tags: [access-control](<https://devfeed.tech/tags/access-control.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-ai](<https://devfeed.tech/tags/agentic-ai.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-assisted](<https://devfeed.tech/tags/ai-assisted.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-model](<https://devfeed.tech/tags/ai-model.md>), [ai-model-selection](<https://devfeed.tech/tags/ai-model-selection.md>), [ai-stack](<https://devfeed.tech/tags/ai-stack.md>), [aiops](<https://devfeed.tech/tags/aiops.md>), [analytics](<https://devfeed.tech/tags/analytics.md>), [automation](<https://devfeed.tech/tags/automation.md>), [copilot](<https://devfeed.tech/tags/copilot.md>), [correlation](<https://devfeed.tech/tags/correlation.md>), [itops](<https://devfeed.tech/tags/itops.md>), [red-hat](<https://devfeed.tech/tags/red-hat.md>), [tools](<https://devfeed.tech/tags/tools.md>), [upstream](<https://devfeed.tech/tags/upstream.md>)

## AI overview

The article argues that AI assistance does not by itself complete production work: copilots, AIOps, and agents can classify or recommend while existing handoffs and approvals remain. It proposes connecting upstream signals to governed downstream execution. In its example, Event-Driven Ansible rulebooks route observability signals to reviewed job templates and workflows that gather facts, enrich tickets, apply known fixes, or escalate; limits on parallel runs and approval gates help control uncertain signals. The same approved automation can be triggered by people, Event-Driven Ansible, or agents, with review and promotion before production use. For agents, the Ansible Automation Platform MCP server provides inspect-and-launch tools under a user's token and RBAC, avoiding direct infrastructure credentials. The author recommends measuring completed production work through job success, ticket updates, and auditable records; the text offers this as a pattern, not evidence of measured outcome improvements.

## Source excerpt

Lately I hear many customers saying the same thing in different words--they added an AI layer to their environment, expected everything to get better, but haven't really noticed anything different yet.In practice, the addition I see first usually sits upstream, whether that's a copilot, an AIOps correlation layer, or an agent able to reason across tools. That part helps people draft, classify, and recommend faster. Getting that work into production still exists on a different layer, and it usually looks the same as before the AI addition, with the same handoffs, queues, and approvals. Red Hat