LaunchDarkly Integration

Connecting LaunchDarkly lets Koalr detect emergency flag rollbacks — a near-certain indicator that a recent deployment introduced a regression. This is one of the highest-confidence signals in Koalr's deploy risk model.

What Koalr syncs

• Flag rollback events — feature flags turned off, archived, or targeting-disabled within 30 minutes of a deployment
• Correlation window — time between deployment and flag toggle
• Triggering engineer — who made the rollback change
• Flag key and environment — which flag and environment were affected

How the signal works

When an engineer deploys to production and then turns off a feature flag within 30 minutes, that's a strong signal that the deployment caused a regression. No competitor surfaces this at deploy time — it requires joining deployment timestamps with the LaunchDarkly audit log.

This unlocks insights like: "3 of your last 5 deploys triggered emergency flag rollbacks."

Flag rollback events appear in:

• The Deploy Risk dashboard — correlated with the triggering deployment
• The Deployment detail view — timeline of events including flag changes
• Automations — you can trigger a Slack alert when a flag rollback is detected post-deploy

Prerequisites

• LaunchDarkly account on the Pro plan or higher (API access required)
• LaunchDarkly Admin role to generate an access token
• Your LaunchDarkly project key and default environment (e.g., production)

Setup

1. In Koalr, go to Settings → Integrations.
2. Click Connect next to LaunchDarkly.
3. Paste your LaunchDarkly API access token.
   • Generate one at app.launchdarkly.com → Account Settings → Authorization.
   • Required scopes: reader role is sufficient.
4. Enter your project key and default environment (usually production).
5. Click Save. Koalr begins monitoring the audit log for rollback events.

Troubleshooting

No rollback events appearing: Ensure the environment you configured matches the environment where your production deployments are tracked. Flag changes in staging or development won't correlate with production deployments.

Missing deployments: LaunchDarkly correlation requires that deployments are tracked in Koalr (via GitHub, Railway, Vercel, or another deploy platform integration). Connect a deployment integration first.