LaunchDarkly (Edge)

Configure LaunchDarkly as a Source in your Pipeline

Perform the following steps to configure your LaunchDarkly Source:

1. Click Pipelines in the Navigation Bar.

2. Click + Create Pipeline in the Pipelines List View.

3. On the Select Source Type page, select LaunchDarkly.

4. On the Select Destination Type page, select the type of Destination you want to use.

5. In the Configure Source screen, specify the following:

   

   • Source Name: A unique name for your Source, not exceeding 255 characters. For example, LaunchDarkly Source.

   • In the Connect to LaunchDarkly section:

     • Access Token: The API access token that you created in LaunchDarkly.

6. Click Test & Continue to test the connection to your LaunchDarkly Source. Once the test is successful, you can proceed to set up your Destination.

   When you click this button, Hevo checks that LaunchDarkly accepts the access token.

---

Data Replication

Hevo replicates data for all the objects selected on the Configure Objects page during Pipeline creation. By default, all supported objects and their available fields are selected. However, you can modify this selection while creating or editing the Pipeline. The Data Model lists the child objects of each parent object. If you select a child object without its parent object, Hevo reads the parent object to ingest the child object, but does not load the parent object to the Destination.

In the first run of the Pipeline, Hevo ingests all the data available for the selected objects in your LaunchDarkly account, including all the entries of the audit log that LaunchDarkly retains. In the subsequent runs, as per the sync frequency, Hevo ingests data as follows:

Hevo ingests the child objects of a parent object along with it.

Hevo reads the environments, feature flags, flag defaults, metrics, and segments of each project in your account, and the maintainers and roles of each team.

LaunchDarkly limits the number of API requests that an access token can make. Read Rate limiting. If LaunchDarkly returns a rate limit error, Hevo waits and retries the request up to three times. If the limit persists, Hevo ingests the data in the next run. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

---

Schema and Primary Keys

Hevo uses the following schema to upload the records in the Destination. For a detailed view of the objects, fields, and relationships, click the ERD.

---

Data Model

The following is the list of tables (objects) that are created at the Destination when you run the Pipeline:

---