Skip to content

[ROB-1732] Holmes able to unzip logs from findings - #731

Merged
Avi-Robusta merged 4 commits into
masterfrom
pull-logs-from-evidence
Jul 29, 2025
Merged

Avi-Robusta merged 4 commits into
masterfrom
pull-logs-from-evidence

Conversation

@Avi-Robusta

@Avi-Robusta Avi-Robusta commented Jul 28, 2025 •

Copy link
Copy Markdown
Collaborator

Here we see holmes prints log data with only the logs from finding
Screenshot 2025-07-28 at 10 01 01
Here you can see the unzipped logs
Screenshot 2025-07-28 at 10 01 20

here is the PR where files were removed due to them being zipped
#106

@coderabbitai

coderabbitai Bot commented Jul 28, 2025 •

Copy link
Copy Markdown
Contributor

Walkthrough

Two new methods, unzip_evidence_file and extract_relevant_issues, are added to the SupabaseDal class in holmes/core/supabase_dal.py. Evidence filtering and decompression logic are centralized in these helpers, and related manual filtering in get_issue_data and get_workload_issues is refactored to use them.

Changes

Cohort / File(s) Change Summary
SupabaseDal Evidence Filtering & Decompression
holmes/core/supabase_dal.py
Added unzip_evidence_file and extract_relevant_issues methods; refactored get_issue_data and get_workload_issues to use new helpers for evidence filtering and decompression.

Sequence Diagram(s)

sequenceDiagram
    participant Caller
    participant SupabaseDal

    Caller->>SupabaseDal: get_issue_data(...)
    SupabaseDal->>SupabaseDal: extract_relevant_issues(evidence)
    alt enrichment_type == "text_file"
        SupabaseDal->>SupabaseDal: unzip_evidence_file(data)
    end
    SupabaseDal-->>Caller: filtered and decompressed evidence
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d83389f1fd6d123a7d8be9eedcaf6ce3be18c96d and 94ff124.

📒 Files selected for processing (1)
  • holmes/core/supabase_dal.py (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.py

📄 CodeRabbit Inference Engine (CLAUDE.md)

**/*.py: Use Ruff for formatting and linting (configured in pyproject.toml)
Type hints required (mypy configuration in pyproject.toml)

Files:

  • holmes/core/supabase_dal.py
🪛 Ruff (0.12.2)
holmes/core/supabase_dal.py

308-311: Combine if branches using logical or operator

Combine if branches

(SIM114)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)
  • GitHub Check: llm_evals
  • GitHub Check: Pre-commit checks
  • GitHub Check: Pre-commit checks
🔇 Additional comments (1)
holmes/core/supabase_dal.py (1)

370-370: LGTM! Good refactoring to centralize evidence filtering.

The replacement of manual filtering logic with extract_relevant_issues centralizes the evidence processing logic while maintaining the same functionality.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch pull-logs-from-evidence

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4ddda68 and 110b03d.

📒 Files selected for processing (1)
  • holmes/core/supabase_dal.py (4 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
**/*.py

📄 CodeRabbit Inference Engine (CLAUDE.md)

**/*.py: Use Ruff for formatting and linting (configured in pyproject.toml)
Type hints required (mypy configuration in pyproject.toml)

Files:

  • holmes/core/supabase_dal.py
🧠 Learnings (1)
📓 Common learnings
Learnt from: nherment
PR: robusta-dev/holmesgpt#408
File: holmes/plugins/toolsets/kubernetes_logs.py:90-97
Timestamp: 2025-05-15T05:13:43.169Z
Learning: In the Kubernetes logs toolset for Holmes, both current and previous logs are intentionally fetched and combined for each pod, even though this requires more API calls. This design ensures all logs are captured even when pods restart but retain their name, providing complete diagnostic information.
🪛 Ruff (0.12.2)
holmes/core/supabase_dal.py

308-311: Combine if branches using logical or operator

Combine if branches

(SIM114)

🪛 GitHub Actions: Build and test HolmesGPT
holmes/core/supabase_dal.py

[error] 311-311: ruff-format: File was reformatted due to code style issues (e.g., changed single quotes to double quotes). Run 'ruff --fix' to apply formatting.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: llm_evals
  • GitHub Check: Pre-commit checks
🔇 Additional comments (2)
holmes/core/supabase_dal.py (2)

10-10: LGTM!

The gzip import is correctly placed and necessary for the new decompression functionality.


371-371: LGTM!

Good refactoring that centralizes evidence filtering and decompression logic, improving code maintainability.

Comment thread holmes/core/supabase_dal.py
Comment thread holmes/core/supabase_dal.py
Comment thread holmes/core/supabase_dal.py
@Avi-Robusta
Avi-Robusta force-pushed the pull-logs-from-evidence branch from d83389f to 3d9d792 Compare July 28, 2025 07:11
@Avi-Robusta
Avi-Robusta enabled auto-merge (squash) July 29, 2025 05:59
@github-actions

Copy link
Copy Markdown
Contributor

Results of HolmesGPT evals

  • ask_holmes: 24/34 test cases were successful, 0 regressions, 1 skipped, 9 mock failures
Test suite Test case Status
ask 01_how_many_pods ✅
ask 02_what_is_wrong_with_pod 🔧
ask 03_what_is_the_command_to_port_forward 🔧
ask 04_related_k8s_events ↪️
ask 05_image_version 🔧
ask 09_crashpod ✅
ask 10_image_pull_backoff 🔧
ask 11_init_containers ✅
ask 13_pending_node_selector ✅
ask 14_pending_resources ✅
ask 15_failed_readiness_probe ✅
ask 17_oom_kill ✅
ask 18_crash_looping_v2 ✅
ask 19_detect_missing_app_details 🔧
ask 24_misconfigured_pvc 🔧
ask 28_permissions_error ✅
ask 29_events_from_alert_manager ✅
ask 39_failed_toolset 🔧
ask 41_setup_argo0 ✅
ask 41_setup_argo1 ✅
ask 42_dns_issues_steps_new_tools 🔧
ask 43_current_datetime_from_prompt ✅
ask 45_fetch_deployment_logs_simple ✅
ask 51_logs_summarize_errors 🔧
ask 53_logs_find_term ✅
ask 54_not_truncated_when_getting_pods 🔧
ask 59_label_based_counting ✅
ask 60_count_less_than 🔧
ask 61_exact_match_counting ✅
ask 63_fetch_error_logs_no_errors ✅
ask 79_configmap_mount_issue 🔧
ask 83_secret_not_found 🔧
ask 89_runbook_missing_cloudwatch 🔧
ask 90_runbook_basic_selection 🔧

Legend

  • ✅ the test was successful
  • ↪️ the test was skipped
  • ⚠️ the test failed but is known to be flaky or known to fail
  • 🔧 the test failed due to mock data issues (not a code regression)
  • ❌ the test failed and should be fixed before merging the PR

@Avi-Robusta
Avi-Robusta merged commit 0bef2f1 into master Jul 29, 2025
@Avi-Robusta
Avi-Robusta deleted the pull-logs-from-evidence branch July 29, 2025 06:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants