Skip to content

Disable streaming output when calling robusta AI (tools streaming sti… #503

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

arikalon1
Copy link
Contributor

…ll working), and enabled structured output (response format)

In addition, there was a bug if the prometheus_url doesn't have trailing '/' Fixed it to support mimir

…ll working), and enabled structured output (response format)

In addition, there was a bug if the prometheus_url doesn't have trailing '/'
Fixed it to support mimir
@arikalon1 arikalon1 requested review from nherment and RoiGlinik June 9, 2025 08:31
Copy link
Contributor

coderabbitai bot commented Jun 9, 2025

Walkthrough

The changes introduce a Pydantic validator to ensure the Prometheus URL always ends with a trailing slash and adjust URL construction to prevent double slashes. In the server logic, conditional handling for the "Robusta" model in the /api/stream/investigate endpoint is disabled, enforcing structured output and disabling the Robusta-specific flag.

Changes

File(s) Change Summary
holmes/plugins/toolsets/prometheus/prometheus.py Added a Pydantic field validator to ensure prometheus_url ends with a slash; adjusted URL joining to prevent double slashes.
server.py Disabled conditional logic for the "Robusta" model in the /api/stream/investigate endpoint; forced structured output and robusta flag values.

Sequence Diagram(s)

sequenceDiagram
    participant Client
    participant Server
    participant Investigation
    participant AI

    Client->>Server: POST /api/stream/investigate
    Server->>Investigation: get_investigation_context(..., structured_output=True)
    Server->>AI: call_stream(..., robusta_ai=False)
    AI-->>Server: Streamed response
    Server-->>Client: Streamed response
Loading
sequenceDiagram
    participant User
    participant PrometheusConfig

    User->>PrometheusConfig: Set prometheus_url
    PrometheusConfig->>PrometheusConfig: ensure_trailing_slash (validator)
    Note right of PrometheusConfig: Appends '/' if missing
Loading
✨ Finishing Touches
  • 📝 Generate Docstrings

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 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (1)
server.py (1)

151-153: Consider a more maintainable approach than commenting out code.

While commenting out code achieves the immediate goal of disabling Robusta-specific logic, consider either removing the commented code entirely or implementing a feature flag if this behavior might need to be toggled in the future.

Apply this diff to clean up the commented code:

-        # Disabled the logic for streaming & structured output with robusta AI
-        # robusta_ai = req.model == "Robusta"
-        # is_structured_output = not robusta_ai
-
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 88a6b95 and d6968d9.

📒 Files selected for processing (2)
  • holmes/plugins/toolsets/prometheus/prometheus.py (3 hunks)
  • server.py (1 hunks)
🧰 Additional context used
🪛 Pylint (3.3.7)
holmes/plugins/toolsets/prometheus/prometheus.py

[error] 53-53: Method 'ensure_trailing_slash' should have "self" as first argument

(E0213)

⏰ Context from checks skipped due to timeout of 90000ms (2)
  • GitHub Check: build (3.12)
  • GitHub Check: Pre-commit checks
🔇 Additional comments (5)
holmes/plugins/toolsets/prometheus/prometheus.py (3)

11-11: LGTM: Required import for field validator.

The import addition is necessary for the new Pydantic field validator.


52-56: LGTM: Proper URL normalization implementation.

The field validator correctly ensures the prometheus_url always has a trailing slash, which addresses the bug mentioned in the PR objectives regarding mimir compatibility.

Note: The pylint warning about method signature is a false positive - Pydantic v2 field validators correctly use cls as the first parameter for class methods.

🧰 Tools
🪛 Pylint (3.3.7)

[error] 53-53: Method 'ensure_trailing_slash' should have "self" as first argument

(E0213)


314-314: LGTM: Proper urljoin usage with validator.

Removing the leading slash from the relative path works correctly with urljoin and the new trailing slash validator, preventing double slashes in the constructed URL.

server.py (2)

156-156: LGTM: Structured output always enabled.

Hardcoding True for structured output aligns with the PR objective to enable structured output. The change is clear and straightforward.


160-160: LGTM: Robusta streaming disabled.

Hardcoding False for the robusta_ai parameter effectively disables streaming when calling Robusta AI, which aligns with the PR objective while maintaining tools streaming functionality.

Copy link
Contributor

github-actions bot commented Jun 9, 2025

Results of HolmesGPT evals

Test suite Test case Status
ask_holmes 01_how_many_pods ⚠️
ask_holmes 02_what_is_wrong_with_pod
ask_holmes 02_what_is_wrong_with_pod_LOKI
ask_holmes 03_what_is_the_command_to_port_forward
ask_holmes 04_related_k8s_events
ask_holmes 05_image_version
ask_holmes 06_explain_issue
ask_holmes 07_high_latency
ask_holmes 07_high_latency_LOKI
ask_holmes 08_sock_shop_frontend
ask_holmes 09_crashpod
ask_holmes 10_image_pull_backoff
ask_holmes 11_init_containers
ask_holmes 12_job_crashing
ask_holmes 12_job_crashing_CORALOGIX
ask_holmes 12_job_crashing_LOKI
ask_holmes 13_pending_node_selector
ask_holmes 14_pending_resources
ask_holmes 15_failed_readiness_probe
ask_holmes 16_failed_no_toolset_found
ask_holmes 17_oom_kill
ask_holmes 18_crash_looping_v2
ask_holmes 19_detect_missing_app_details
ask_holmes 20_long_log_file_search
ask_holmes 20_long_log_file_search_LOKI
ask_holmes 21_job_fail_curl_no_svc_account
ask_holmes 22_high_latency_dbi_down
ask_holmes 23_app_error_in_current_logs
ask_holmes 23_app_error_in_current_logs_LOKI ⚠️
ask_holmes 24_misconfigured_pvc
ask_holmes 25_misconfigured_ingress_class ⚠️
ask_holmes 26_multi_container_logs ⚠️
ask_holmes 27_permissions_error_no_helm_tools
ask_holmes 28_permissions_error_helm_tools_enabled
ask_holmes 29_events_from_alert_manager
ask_holmes 30_basic_promql_graph_cluster_memory
ask_holmes 31_basic_promql_graph_pod_memory
ask_holmes 32_basic_promql_graph_pod_cpu
ask_holmes 33_http_latency_graph
ask_holmes 34_memory_graph
ask_holmes 35_tempo
ask_holmes 36_argocd_find_resource
ask_holmes 37_argocd_wrong_namespace ⚠️
ask_holmes 38_rabbitmq_split_head
ask_holmes 39_failed_toolset
ask_holmes 40_disabled_toolset
ask_holmes 41_setup_argo
investigate 01_oom_kill
investigate 02_crashloop_backoff
investigate 03_cpu_throttling
investigate 04_image_pull_backoff
investigate 05_crashpod
investigate 05_crashpod_LOKI
investigate 06_job_failure
investigate 07_job_syntax_error
investigate 08_memory_pressure
investigate 09_high_latency
investigate 10_KubeDeploymentReplicasMismatch
investigate 11_KubePodCrashLooping
investigate 12_KubePodNotReady
investigate 13_Watchdog
investigate 14_tempo

Legend

  • ✅ the test was successful
  • ⚠️ the test failed but is known to be flakky or known to fail
  • ❌ the test failed and should be fixed before merging the PR

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