Overview
KlaudiaAI is now available across all of Komodor's investigation capabilities. You can now share investigations with colleagues as well as ask Klaudia follow up questions that you may have, including across other services!
Prerequisites
- KlaudiaAI needs to be enabled for the account by the
account-admin
in the features page. - For more complex cases, Klaudia may provide further details around the investigation being run as well as showing a delay banner.
Workload Based Assistance
Detection & Analysis:
- Identifies workflow and pod failures (e.g., CrashLoopBackOff state).
- Correlates logs and events to pinpoint root causes.
AI-Driven Root Cause Analysis:
- Highlights specific misconfigurations (e.g., YAML syntax errors).
- Points out incorrect settings in Kubernetes resources.
Suggested Remediation:
- Provides precise fixes (e.g., correcting YAML indentation).
- Links to affected resources for quick troubleshooting.
Automated Insights & Evidence Collection:
- Extracts logs, configurations, and errors automatically.
- Displays YAML errors directly within the investigation panel.
Interactive Troubleshooting:
- Enables real-time investigations with options to restart analysis.
Failed Deploy & Workflow Assistance

Detects Deployment Failures
- Identifies failed deployments and flags them in the Komodor UI.
- Tracks deployment events and failure points.
Provides Timeline & Event Breakdown
- Displays a timeline of deployment events, including pod states like:
- Pending
- Running (not ready)
- Running (ready)
- Shows key failure points (e.g., image update failure).
Correlates Events with Changes
- Links failures to configuration changes (e.g., image updates, annotations).
- Helps identify what changed before the failure occurred.
Suggests Remediation Steps
- Highlights potential causes like:
- Incorrect image tags
- Missing dependencies
- Misconfigured environment variables
- Provides recommendations to fix issues.
Enables Quick Investigation & Fixes
- Offers direct actions like:
- Restarting the deployment.
- Editing YAML configurations.
- Detecting configuration drift.
KlaudiaChat - BETA
Now Komodor's own KlaudiaAI has the ability to have a chat about their findings' from the investigation as well as assist your understanding of other issues on your cluster.
⭐️ Motivation
Troubleshooting efforts require more than the initial RCA information. For example, after receiving the initial root cause analysis from Klaudia, it's important to understand:
- Clarifications on RCA results (e.g., "What does this finding mean?").
- Insights into resolution steps and prevention methods.
- Contextual connections and impact analysis of the issue.
- A way to investigate related resources, or changes easily.
With KlaudiaChat, we’ve redefined how problems are addressed. This feature provides you:
- 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.
Detection & Analysis:
- Identifies issues and correlations across the cluster.
- Correlates logs and events to pinpoint root causes as well as any extra context you provide to them.
Ask follow up questions by using free-text queries to explore additional dimensions of the issue, including:
- Clarifications (e.g., “Why do you think this happened?”).
- Resolution Steps (e.g., “How do I fix this?”).
- Historical Analysis (e.g., “Has this issue occurred before?”).
- Impact Assessment (e.g., “How does this affect users or environments?”)
Want to share the entire conversation with a teammate? Click the “Share link” button next to the RCA results.
Comments
0 comments
Please sign in to leave a comment.