Overview
Klaudia's CI Tool enables intelligent investigation and troubleshooting of deployment-related issues by correlating Kubernetes events with CI/CD pipeline data. When applications experience issues following deployments, Klaudia can trace back to the specific build, code changes, and pipeline execution that produced the problematic artifact, providing comprehensive root cause analysis.
Understanding what changed is critical to effective troubleshooting. Klaudia bridges the gap between "what's broken in production" and "what changed in the last deployment" by automatically querying your CI system during investigations. This correlation helps identify whether issues stem from code changes, build configuration problems, or deployment process failures.
Supported Tools
| Tool | Description |
| Jenkins | Open-source automation server for building, testing, and deploying software |
What Klaudia Can Do
General Capabilities
- Build Correlation: Link Kubernetes deployments to specific CI builds
- Change Tracking: Identify code commits included in problematic releases
- Build Log Analysis: Examine build logs for warnings and configuration issues
- Artifact Verification: Validate deployed artifacts match build outputs
- Pipeline Investigation: Analyze pipeline stage failures and timing
Jenkins
- Retrieve build details for deployments causing issues
- Analyze console output for build warnings and errors
- Identify code changes (commits, authors) in specific builds
- Examine build parameters and environment variables
- Correlate test results with production failures
- Investigate failed builds and their impact on deployments
When Klaudia Uses CI Tool - Usage Examples
Klaudia automatically engages CI investigation tools in the following scenarios:
Root Cause Analysis (RCA)
When deployment-related issues may trace back to build problems:
- Application failures starting immediately after deployment
- Configuration mismatches between environments
- Missing dependencies or incorrect artifact versions
Troubleshooting Unhealthy Resources
When investigating pods that fail after deployment:
- Pods in CrashLoopBackOff with new image versions
- Container image pull errors or invalid manifests
- Runtime errors suggesting build misconfiguration
Chat Sessions
When you ask Klaudia questions about deployments and builds:
- "What changed in the last deployment?"
- "What commits were included in build #147?"
- "Did the Jenkins build show any warnings?"
Comments
0 comments
Please sign in to leave a comment.