Monitor Integrations
Monitor Integrations shows whether an integration is running and where records sit in the data pipeline. Open it from Tools > Monitoring > Integrations.
Setup versus Monitoring
Section titled “Setup versus Monitoring”| Configure Integrations | Monitor Integrations | |
|---|---|---|
| Sidebar | Tools > Data Setup > Configure Integrations | Tools > Monitoring > Integrations |
| Purpose | Create the integration, pick type and station, edit settings (keys, tables, time fields) | Select a running integration; inspect configuration, activity, pipeline stages, checkpoints, and messages |
| When you use it | Onboarding and changing how data is connected | Confirming ingest, debugging failures, restarting, or changing mode/enabled |
Operation Mode and Enabled
Section titled “Operation Mode and Enabled”You set these on the integration config page or change them from the monitor quick-edit menu.
| Setting | Choices | Effect |
|---|---|---|
| Operation mode | Test, Live, or Use Parent (when the config has a parent) | Test keeps records on the test branch for inspection. Live loads into production tables. Use Parent inherits the parent’s mode. |
| Enabled for use | On or off (chips show Enabled / Disabled) | Off means the integration does not ingest. Enabled still requires mode Test or Live (or a parent that resolves to one of those). |
For production tables, set the parent to Live and Enabled, then set the child to Enabled with Use Parent or Live. A Test or Disabled parent blocks that. The monitor page shows tips when those cases apply.
Select an Integration
Section titled “Select an Integration”- Confirm the correct organization in the org picker.
- Open the integration combobox (
Select an integration) and pick a config. - Review the Configuration card (name, Operation mode and Enabled chips, related integrations if any) and the Activity Log (runtime phase and recent log lines).
From the configuration card you can open the quick-edit menu to change Operation mode or Enabled for use, or open the full config editor in a new window.
After you select an integration that has a pipeline tree, three tabs appear.
Data Pipeline
Section titled “Data Pipeline”Shows the stage tree for that integration type. For a Station Webhook, the path is roughly:
Ingest (Inbound HTTP POST) → Decode → Prepare → Load / Database
Each branch splits into Live: Success / Live: Error and Test: Success / Test: Error, with message counts where available. Use View Messages on a node to jump to the Messages tab for that subject.
Actions on this tab:
- Restart Integration: restarts the orchestrated pipeline.
- Re-apply changes (e.g. after deleting checkpoints): clears the applied fingerprint before restart so settings and checkpoint edits take effect.
Checkpoints
Section titled “Checkpoints”Key/value resume state the integration uses to remember progress (extract cursors and related values). Filter the list if needed, select rows, then Delete Selected when you intentionally want the job to forget those markers. After deleting checkpoints, restart with Re-apply changes checked if the pipeline should pick up the new state.
Messages
Section titled “Messages”Lists recent pipeline messages for the subject you chose from the Data Pipeline tree (up to the most recent 50). Pick a timestamp to inspect the JSON body. Refresh as new messages arrive.
Typical Workflow
Section titled “Typical Workflow”- Create and enable the integration under Configure Integrations. Start in Test if you want to inspect payloads before loading.
- Open
Monitor Integrations, select the config, and confirm the activity log shows a healthy runtime phase (for example Running or Idle). - On Data Pipeline, follow Test: Success (or Live: Success) and open Messages to verify records.
- When ready for production tables, set Operation mode to Live and keep Enabled for use on.
- If ingest stalls after a settings or checkpoint change, delete the relevant checkpoints if needed, then Restart Integration with Re-apply changes checked.