Installing Airbyte (On-Prem) and Connecting Sources
Configure Airbyte on-premises to send data to a dedicated database.
Updated
by Deanna Smith
This document outlines how to configure your own Airbyte instance to send your data to a dedicated database for use with TargetBoard.
Before You Begin
- You will need an Airbyte Open-Source On-Prem instance deployed and accessible. See Airbyte's documentation for how to this if needed.
- A dedicated target database will need to be created using credentials provided by TargetBoard (host, port, database name, username, password), and then verified by the TargetBoard team.
- Verify that the Airbyte instance has network access to the database server.
- Open your Airbyte instance in a web browser and login with admin credentials.
- Navigate to Connections > New Connection.
- Choose a source connector (eg: Zendesk, Salesforce, Jira, GitHub etc.)
- Configure the source connector by entering the required API credentials, authentication tokens or other connection details as prompted. Refer to Airbyte documentation for specific guidance on each connector.
- Test the connection to ensure it is successful.
- Choose the destination connector as your dedicated database (PostgreSQL).
- Configure the destination with the credentials sent to you by TargetBoard (host, portm database name, username, password).
- Test the connection to verify that the destination is reachable.
- After configuring the source and destination connectors, create a connection.
- Define the sync settings:
- Streams: Select the data streams to sync (e.g., tickets, issues, events).
- Sync Mode: Choose between Full Refresh, Incremental, or Append.
- Destination Namespace: Define how the data will be organized in the destination (e.g., schema per stream or a single schema).
- Save the connection.
- Define the sync settings:
- Schedule the sync by setting frequency (Hourly or Daily), ensuring that this schedule aligns with your data refresh requirements.
- Save the configuration.
How did we do?
Self Hosted Database
Connecting Okta SSO