Chat & Interactive Troubleshooting

Klaudia is Komodor's AI SRE — available across all investigation surfaces in the platform. This page covers how each capability works in practice: workload and deployment investigation, full-stack RCA across Kubernetes core, compute, networking, GitOps, data services, and ML workloads, chat-based troubleshooting, autonomous remediation, organizational context, and external integrations.

Klaudia Chat

Troubleshooting doesn’t stop at the first RCA. Often, you need to:

• Clarify what a finding means
• Understand resolution steps and prevention
• Investigate related resources
• Assess the broader impact of a change or failure

And sometimes, you just want to understand how a healthy resource behaves or fits into your environment. With Klaudia Chat, you now have a virtual SRE available on demand—whether you’re working on a live issue or exploring infrastructure.

Klaudia Chat enables ongoing, context-aware conversation at any point in an investigation — and from any resource in the platform, even healthy ones.

Ask natural-language questions to investigate any resource - get context, understand issues, assess impact, and explore solutions effortlessly. Restore or share historical chats.

What Klaudia Chat enables:

• Reduced Mean Time to Resolution (MTTR): Faster insights lead to quicker resolutions.
• Interactive Problem Exploration: A back-and-forth conversation simplifies troubleshooting.
• Deeper Insights: Leverage Klaudia’s expansive knowledge base for comprehensive answers.
• Adaptable Investigation Paths: Branch into related issues that the initial RCA doesn’t immediately cover.

Automated Correlation

Leverage AI with multi-source data, history & deep K8s knowledge in Komodor to correlate issues to recent changes, related resources, cross-cluster info, infra issues and more for a profound investigation experience.

Cross cluster chat support

Klaudia reasons across your entire fleet in a single conversation. Ask questions that span multiple clusters without pre-selecting one — she resolves scope dynamically, enabling fleet-wide investigations that would otherwise require multiple fragmented sessions. No need to pick a specific cluster upfront.

When opening Klaudia without a cluster context, users can either select a specific cluster for a focused deep-dive, or start a Cross-Cluster chat to explore issues, compare state, or ask broad questions across their entire environment
(e.g. "Which clusters had the most deployment failures today?").

For the most precise investigations, selecting a specific cluster is still recommended -
but cross-cluster chat is a great way to get a quick read across your environment.

Granular chat permissions

• Users with partial cluster access can now use cluster/cross cluster chats in Klaudia without needing full cluster permissions.
• With the new granular chat permissions model, we are tackling a very common use case where the user has scoped permissions within cluster/s.
• Clusters where the Komodor user has partial permissions are marked 'limited access' in the cluster selector within the chat.
• Users with partial cluster permissions can start a chat, ask questions and trigger actions only on their scooped resources.
• If a user asks Klaudia to act on a resource they can't access, Klaudia blocks it with an explanation and suggests an alternative when one exists.

AI Driven RCA

From day-one, and without requiring extensive setup, Komodor’s internal AI models leverage this existing knowledge base and conduct independent investigations to automatically highlight the root cause (RCA) and suggest actionable next steps.

RCA Chat

Troubleshooting doesn't stop when the RCA ends. Chat keeps the investigation moving — from diagnosis to full resolution — without switching tools.

When viewing any Klaudia Root Cause Analysis, continue the investigation through conversation:

• Ask follow-up questions: "What does this finding mean?", "How do I prevent this from happening again?"
• Get step-by-step resolution guidance
• Investigate related logs, events, or recent changes
• Branch into adjacent issues the initial RCA didn't cover

Share your chat outputs

Want to share the entire conversation with a teammate? Click the “Share link” button next to the RCA results.

Chat from Any Resource

Open Ask Klaudia from any resource in the platform — Pods, Deployments, ConfigMaps, Secrets, Nodes, and more — regardless of whether an issue is active. 

Klaudia uses Komodor’s event intelligence and investigation engine to:

• Identify issues and correlations across the cluster
• Connect logs, events, and configurations to uncover root causes
• Leverage user prompts to refine answers with context

Klaudia scopes the conversation to the selected resource and provides contextual answers, suggested questions, and explanations of metrics, recent changes, and dependencies.

Questions you can ask from any resource:

• "Why did this happen?"
• "How do I fix it?"
• "What changed recently?"
• "Which services are related to this?"
• "Has this occurred before?"
• "What does this config mean?"