Configure Statuspage as a Source in your Pipeline

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

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

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

     • API Key: The API key that you created in Statuspage.

     • Organization ID: The ID of your Statuspage organization, which you copied from the URL of the API info page.

6. Click Test & Continue to test the connection to your Statuspage Source. 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.

Hevo ingests the entire data of all the selected objects during each Pipeline run, as per the sync frequency.

You can resync only the parent objects, Page and Users. When you resync a parent object, Hevo also resyncs its child objects.

Statuspage limits API requests to 1 request per second per API key. If Statuspage rejects a request because of this limit, Hevo waits for the time that Statuspage specifies, and then retries the request once. To understand how Hevo handles such scenarios, read Handling Rate Limit Exceptions.

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.

Click to view ERD

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

• The objects that link two records, such as Incident Component and Subscriber Component, use the IDs of both records, for example, component_id and incident_id.

• Component Uptime: id and page_id.

• Incident Update and Incident Subscriber: id and incident_id.

• Incident Postmortem: incident_id.

• Page Status Embed Config: page_id.

• User Permission: page_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: