Rollbar (Edge)

Configure Rollbar as a Source in your Pipeline

Perform the following steps to configure your Rollbar 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 Rollbar.

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, Rollbar Source.

   • In the Connect to Rollbar section, specify the following:

     • Account Access Token: The account access token that you created in Rollbar.

6. Click Test & Continue to test the connection to your Rollbar Source. Hevo checks the connection by reading the list of projects in your Rollbar account. The test fails if Rollbar rejects the access token. Once the test is successful, you can proceed to set up your Destination.

---

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. To ingest a child object, you must also select its parent object.

Hevo ingests the following types of data from your Source objects:

• Historical Data: The first run of the Pipeline ingests all the data of the selected objects.

• Incremental Data: Once the historical load is complete, Hevo ingests the entire data of all the objects in each run, as per the sync frequency.

You can resync only the Project, Team, and Users objects. To resync a child object, resync its parent object.

Rollbar limits the number of API requests that each access token can make. Read Rate Limits. If a limit is reached, Hevo waits and retries the request.

Note: You can create a Pipeline with this Source only using the Merge load mode. The Append mode is not supported for this Source.

---

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.

The primary key of most objects is id. The following objects use other primary keys:

• Project: project_id.

• Project Global: index and project_id.

• Project Setting Data Custom: project_id.

• Project Version: project_id and version.

• Query Language Job: job_id.

• Team Project: project_id and team_id.

• Team User: team_id and user_id.

• User Project: project_id and user_id.

---

Data Model

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

---