Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Open in new tab

This page will walkthrough the setup of Fivetran in K using the Direct Connect method

Step 1) Create an API Key

  • Log into your Fivetran account and go to Settings. Go to the API Config section to find the API Key and Secret

  • Copy the API Key and Secret for the next step

Step 2) Add Fivetran as a New Source

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Integrations click on Sources

  • Click Add Source and select Fivetran

  • Select Direct Connect and add your Fivetran details and click Next

  • Fill in the Source Settings and click Save & Next

    • Name: Give the Fivetran source a name in K

    • Host: Can be any unique value. For example add fivetran.com/[fivetran account name]

    • Update the Host / Database mapping - see Host / Database Mapping for each project

  • Add your Key (client ID) and Secret (client Secret) copied from Step 1 and click Save

  • Test your connection and click Save

  • Click Finish Setup

Step 3) Schedule Fivetran source load

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Integrations click on Sources

  • Locate your new Fivetran source and click on the Schedule Settings (clock) icon to set the schedule

Note that scheduling a source can take up to 15 minutes to propagate the change.

Step 4) Manually run an ad hoc load to test DBT Cloud setup

  • Select Platform Settings in the side bar

  • In the pop-out side panel, under Platform Settings click on Batch Manager

  • In Source Load click Run

  • Select the name of the Source you created in Step 2 and click Run

  • After the source is triggered, the screen will change to the Monitor tab where you can see the progress of the job.

A manual source load will also require a manual run of

  • DAILY

  • GATHER_METRICS_AND_STATS

To load all metrics and indexes with the manually loaded metadata. These can be found in the Batch Manager page

 

Troubleshooting failed loads

  • If the job failed at the extraction step

    • Check the error. Contact KADA Support if required.

    • Rerun the source job

  • If the job failed at the load step, the landing folder failed directory will contain the file with issues.

    • Find the bad record and fix the file

    • Rerun the source job

  • No labels