Overview

Send LaunchDarkly feature flag changes to Callgoose SQIBS. A LaunchDarkly webhook posts every flag change in production to your SQIBS API endpoint. A common use: when someone turns off a kill-switch flag during an outage, SQIBS opens an incident so the on-call team knows, and resolves it when the flag is turned back on.

You need
LaunchDarkly with permission to manage integrations, and a SQIBS API token
Setup time
About 10 minutes
Result
Production flag changes open and resolve SQIBS incidents

How it works

LaunchDarkly
Alert fires
A flag is turned off in production.
LaunchDarkly
Sends a webhook
Through a webhook, as the change history entry.
SQIBS
API filter matches
The filter decides whether to open or resolve, and the priority.
SQIBS
Incident opens
turned off the flag opens it, turned on the flag closes it.

Want SQIBS to fix known issues before anyone is paged? See Fix known issues automatically.

Step 1: Add the API filter in SQIBS

  1. In SQIBS, open Services, choose the service that should receive these incidents, and click Add Or Update API Integration.
  2. Add a filter with these values (there is no built-in LaunchDarkly template yet, so enter them by hand):
Part Payload JSON key Key value contains What it does
Trigger "titleVerb" turned off the flag Opens an incident.
Resolve "titleVerb" turned on the flag Resolves the open incident.
Match "name" One incident per flag.
Title from "title" Becomes the incident title, for example who turned off which flag.
  1. Choose the Priority for these incidents and click Save.

The webhook sends every change, but only these two match the filter. Use the webhook's policy filter (step 2) to limit it to the flags and environments you care about.

Not sure of a key? Send one test message first (step below), then build the filter from the real payload.

Find the right key with the JSON key creator
In the API Integration window, click the round {} button at the bottom right. Paste a payload that SQIBS received (copy it from the API log). SQIBS lists every key with its value, each with a copy button. Copy the key into Payload JSON key and the value into Key value contains. No need to read the JSON by hand.

Step 2: Add the webhook in LaunchDarkly

  1. In LaunchDarkly, click the gear icon to open Organization settings, then Integrations. Find Webhooks and click Add integration.
  2. Give it a Name, for example Callgoose SQIBS, and enter your SQIBS endpoint as the URL:
https://<your-endpoint>/sqibs-api/v1/process?from=launchdarkly&token=<your-token>

Replace <your-endpoint> and <your-token> with the values from your SQIBS account. See how to get the endpoint URL and API tokens.

  1. Optionally add a policy to send only some flags, for example only flags tagged kill-switch in production. Without a policy, LaunchDarkly sends all flag changes in production.
  2. Tick the confirmation and click Save settings.

Step 3: Test it

The API log saves payloads only while API Tracking is on for the token. Turn it on under API Tokens before you test; it switches itself off after 48 hours.

  1. Turn off a test flag in production (or in the environment your policy covers).
  2. In SQIBS, a new incident opens. LaunchDarkly's payload looks like this (shortened):
{
  "_id": "6741a2b3c4d5e6f708192a3b",
  "kind": "flag",
  "name": "checkout-new-payment-flow",
  "titleVerb": "turned off the flag",
  "title": "Sam Lee turned off the flag checkout-new-payment-flow in Production",
  "member": {
    "email": "sam.lee@example.com",
    "firstName": "Sam",
    "lastName": "Lee"
  },
  "date": 1763806500000
}
  1. Turn the flag back on. LaunchDarkly sends turned on the flag for the same flag, and SQIBS resolves the incident.

No incident? Open the API log (with API Tracking on). If the payload is there, the filter did not match it: paste it into the JSON key creator and check the keys. If it is not there, check the URL and token in the LaunchDarkly webhook.

Fix known issues automatically

Many alerts have a known fix: restart a service, clear a full disk, run a health check. SQIBS can run that fix for you the moment the incident opens. This is event-driven auto remediation. For example, when a kill switch is turned off, SQIBS can run a workflow that collects the error rates of the affected service for the incident record.

Incident opens
Workflow starts
SQIBS runs the automation workflow linked to the filter.
Fixed
Incident resolved
The issue is fixed before anyone has to step in.
Not fixed
Escalated to the engineer
After the waiting time you set, the escalation policy pages on-call as usual.

Safe by design. SQIBS runs only workflows your own engineers wrote and approved for your environment. Nothing is guessed or generated: the same steps an engineer would run by hand, run sooner. If the workflow does not fix the issue, the engineer is paged as usual.

To set it up, in the same API filter:

  1. Select Workflow: choose the automation workflow to run when this filter opens an incident.
  2. If success then make incident resolved: turn on to resolve the incident when the workflow succeeds.
  3. Waiting time for escalate to escalation policies: how many minutes to give the workflow before paging the on-call engineer.

Start with low-risk workflows, such as a health check, and add fixes as you come to trust them.

Learn more: