Skip to content

Conversation

@Avi-Robusta
Copy link
Contributor

No description provided.

@coderabbitai
Copy link

coderabbitai bot commented Oct 21, 2025

Walkthrough

Adds a new LaunchDarkly webhook integration documentation and updates several documentation index pages to include and reorder LaunchDarkly (and related integrations) among alert sources and custom ingestion entries.

Changes

Cohort / File(s) Summary
New LaunchDarkly integration doc
docs/configuration/alertmanager-integration/launchdarkly.rst
New comprehensive documentation describing LaunchDarkly webhook setup to forward feature-flag changes to Robusta, prerequisites, webhook headers/alternative method, tracked event details, validation/troubleshooting, and Holmes integration via Helm generated_values.yaml.
Documentation index & navigation updates
docs/configuration/index.rst, docs/index.rst, docs/configuration/exporting/robusta-pro-features.rst
Adds a LaunchDarkly card to the configuration index and updates the alert integrations list (adds LaunchDarkly and New Relic, reorders/reintroduces Nagios and other entries); documentation-only reordering and content edits.

Sequence Diagram(s)

sequenceDiagram
    participant LaunchDarkly as LaunchDarkly
    participant RobustaWebhook as Robusta Webhook (Alertmanager)
    participant Robusta as Robusta Processor / Holmes

    Note over LaunchDarkly, RobustaWebhook: New/changed feature flag event
    LaunchDarkly->>RobustaWebhook: POST webhook (payload + optional headers)
    alt Header-based auth
        RobustaWebhook->>Robusta: Validate headers (account_id / api_key)
    else Payload-based auth (default)
        RobustaWebhook->>Robusta: Validate body (account_id / api_key in payload)
    end
    Robusta->>Robusta: Normalize event -> create alert
    Robusta->>Holmes: Enqueue for analysis / notify users
    Robusta-->LaunchDarkly: 200 OK (ack)
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Suggested reviewers

  • pavangudiwada
  • RoiGlinik

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Description Check ⚠️ Warning No pull request description was provided by the author. The description check is lenient and should pass if the description is related to the changeset in any way; however, an empty description does not satisfy this criterion. Without any descriptive text from the author, there is nothing to relate to the changeset, which means the pull request fails to meet the basic requirement of having a description related to its changes. Please add a pull request description that provides context for the LaunchDarkly integration documentation changes. This can be brief and doesn't need to be exhaustive, but it should explain the purpose or scope of the documentation updates being made.
✅ Passed checks (2 passed)
Check name Status Explanation
Title Check ✅ Passed The pull request title "[ROB-2343] Launchdarkly docs" clearly and specifically identifies the main change in the changeset. The raw summary confirms that the pull request adds new LaunchDarkly integration documentation across multiple documentation files (a new launchdarkly.rst file, updates to robusta-pro-features.rst, configuration index.rst, and docs index.rst). The title is concise, avoids noise, and accurately summarizes the primary change from the developer's perspective.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch launchdarkly

📜 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 4b06cf9 and bfe9ae6.

📒 Files selected for processing (1)
  • docs/configuration/alertmanager-integration/launchdarkly.rst (1 hunks)
✅ Files skipped from review due to trivial changes (1)
  • docs/configuration/alertmanager-integration/launchdarkly.rst
⏰ 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: run_tests
  • GitHub Check: run_tests
  • GitHub Check: Deploy docs

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

Comment @coderabbitai help to get the list of available commands and usage tips.

arikalon1
arikalon1 previously approved these changes Oct 21, 2025
Copy link
Contributor

@arikalon1 arikalon1 left a comment

Choose a reason for hiding this comment

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

looks good, left one comment

@arikalon1 arikalon1 merged commit 471f567 into master Oct 21, 2025
6 checks passed
@arikalon1 arikalon1 deleted the launchdarkly branch October 21, 2025 14:49
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.

3 participants