# How Red Hat OpenShift 5 simplifies incident diagnosis with supervised AI

DevFeed: [How Red Hat OpenShift 5 simplifies incident diagnosis with supervised AI](<https://devfeed.tech/articles/how-red-hat-openshift-5-simplifies-incident-diagnosis-with-supervised-ai-129635.md>)

Original publisher: [Read original article](<https://www.redhat.com/en/blog/how-red-hat-openshift-5-simplifies-incident-diagnosis-supervised-ai>)

Author: Vanessa Martini

Published: 2026-11-11T00:00:00Z

Content type: article

Language: en

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

Topics: [AIOps for Kubernetes](<https://devfeed.tech/topics/aiops-for-kubernetes.md>), [observability](<https://devfeed.tech/topics/observability.md>), [telemetry](<https://devfeed.tech/topics/telemetry.md>), [Artificial Intelligence](<https://devfeed.tech/topics/ai.md>), [human-in-the-loop UX](<https://devfeed.tech/topics/human-in-the-loop-ux.md>), [Prometheus](<https://devfeed.tech/topics/prometheus.md>), [OpenTelemetry](<https://devfeed.tech/topics/opentelemetry.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [alert](<https://devfeed.tech/tags/alert.md>), [alert-fatigue](<https://devfeed.tech/tags/alert-fatigue.md>), [cluster](<https://devfeed.tech/tags/cluster.md>), [data](<https://devfeed.tech/tags/data.md>), [diagnosis](<https://devfeed.tech/tags/diagnosis.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [incident](<https://devfeed.tech/tags/incident.md>), [language](<https://devfeed.tech/tags/language.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [openshift](<https://devfeed.tech/tags/openshift.md>), [openshift-5](<https://devfeed.tech/tags/openshift-5.md>), [platform](<https://devfeed.tech/tags/platform.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [red-hat-openshift](<https://devfeed.tech/tags/red-hat-openshift.md>), [security-governance](<https://devfeed.tech/tags/security-governance.md>), [telemetry](<https://devfeed.tech/tags/telemetry.md>), [traces](<https://devfeed.tech/tags/traces.md>)

## AI overview

OpenShift Lightspeed turns alert response into structured, human-reviewed investigation: it can correlate Prometheus metrics, pod logs, and installed OpenTelemetry traces into evidence, signals, and draft findings. On OpenShift 4.22+ with Lightspeed operator 1.1.5+, teams can also request Perses metric panels in natural language; with cluster observability operator 1.6, panels are marked AI-assisted and expose PromQL, time range, and source metrics for review. OpenShift 5 adds an opt-in technology preview that watches existing Alertmanager receivers, runs standard oc/kubectl diagnostics, and stages remediation for approval. It requires Lightspeed operator 2 and a configured tool-calling LLM; no default model ships. Changes require administrator approval, run in ephemeral RBAC-sandboxed environments, and are audited, with failed remediation halted and escalated. Model endpoint choice determines where data is processed; locally hosted models can support air-gapped use.

## Source excerpt

Prometheus metrics, traces, and logs are rarely missing in modern enterprise environments. Most platform teams already have plenty of telemetry at their disposal. The real bottleneck is the sheer volume of data a human must parse before taking meaningful action during an incident.On a busy cluster, this creates a familiar and exhausting pattern: an alert fires, an engineer opens 3 different consoles, brings up a Prometheus Query Language (PromQL) scratchpad, executes a log query, and spends 20 minutes debating whether the signal represents a genuine emergency or background noise. Alert fatigue