Source Control Tools Investigation

Overview

Klaudia's Source Control Tools enable intelligent investigation and troubleshooting by correlating Kubernetes deployment issues with code changes in your repositories. When applications experience failures after deployment, Klaudia can trace back to specific commits, pull requests, and code changes that may have introduced the problem, providing developers with actionable context for faster resolution.

Understanding what code changed is essential for effective incident response. Klaudia bridges the gap between "my deployment is broken" and "what code caused this" by automatically querying your source control platform during investigations. This correlation helps identify the specific changes, authors, and context that led to production issues.

Supported Tools

What Klaudia Can Do

General Capabilities

• Commit Correlation: Link deployed versions to specific commits
• Change Analysis: Identify files and code paths modified in deployments
• Author Attribution: Identify who made changes for faster communication
• PR/MR Context: Retrieve pull request descriptions, reviews, and discussions
• Diff Analysis: Examine specific code changes that may have caused issues

GitHub

• Retrieve commit details and file changes for deployed versions
• Access pull request descriptions, reviews, and comments
• Examine commit history between deployed versions
• Identify authors and reviewers for specific changes
• Correlate GitHub Actions workflow status with deployments

GitLab

• Retrieve commit information and merge request details
• Access MR descriptions, discussions, and approvals
• Identify contributors and code owners
• Correlate GitLab CI/CD status with deployments

When Klaudia Uses Source Control Tools - Usage Examples

Klaudia automatically engages source control investigation tools in the following scenarios:

Root Cause Analysis (RCA)

When deployment issues may trace back to code changes:

• Application errors appearing after new version deployment
• Performance regressions correlating with release dates
• Configuration changes in application code

Troubleshooting Unhealthy Resources

When investigating pods failing with application errors:

• Stack traces pointing to specific code files
• Behavior changes between versions
• New exceptions or error types after deployment

Chat Sessions

When you ask Klaudia questions about code changes:

• "What changed in the last deployment?"
• "Who made changes to the payment processing code?"
• "What was in the PR for this release?"