January 2022link
We have added the sync_id field as a common field of the log events.
December 2021link
We now generate the sync_end log event in our logs for every possible sync status:
SUCCESSFULFAILUREFAILURE_WITH_TASKRESCHEDULED
Previously, we generated the sync_end log event only for successful syncs.
September 2021link
We now generate the change_schema_config_via_api log event in our logs when you change a schema sync configuration using our REST API.
See our Log events documentation for details.
August 2021link
We have updated the value of the log event’s connector_id property. Previously, the connector_id and connector_name properties both contained the connector name. Now, connector_id contains the connector ID, while connector_name still contains the connector name.
Learn more in our Log events documentation.
December 2020link
Fivetran now supports flushing basic SQL transformation event data to supported log services.
Each log service has a unique path for this data:
| Log Service | Path Pattern |
|---|---|
| AWS CloudWatch | {ACCOUNT_NAME}/{GROUP_NAME}/transformation/{TRANSFORMATION_NAME} |
| Azure Log Analytics | {ACCOUNT_NAME}_{GROUP_NAME}_transformation_{TRANSFORMATION_NAME}_CL |
| Google Cloud Logging | {ACCOUNT_NAME}-{GROUP_NAME}-transformation-{TRANSFORMATION_NAME} |
| Splunk Log | channel.account="{ACCOUNT_NAME}"channel.group="{GROUP_NAME}"channel.service="transformation"channel.schema="{TRANSFORMATION_NAME}" |
Learn more in our Log events documentation.
Fivetran now supports flushing dbt transformations event data to supported log services.
Each log service has a unique path for this data:
| Log Service | Path Pattern |
|---|---|
| AWS CloudWatch | {ACCOUNT_NAME}/{GROUP_NAME}/dbt/{DBT_JOB_NAME} |
| Azure Log Analytics | {ACCOUNT_NAME}_{GROUP_NAME}_dbt_{DBT_JOB_NAME}_CL |
| Google Cloud Logging | {ACCOUNT_NAME}-{GROUP_NAME}-dbt-{DBT_JOB_NAME} |
| Splunk Log | channel.account="{ACCOUNT_NAME}"channel.group="{GROUP_NAME}"channel.service="dbt"channel.schema="{DBT_JOB_NAME}" |
Learn more in our Log events documentation.
November 2020link
We have added a new log event, diagnostic_access_granted. Read our Log events documentation for more information.
September 2020link
We have added a new log event, change_schema_config_via_sync. See our Log events documentation for more information.
October 2018link
Fivetran now supports flushing dashboard activity event data to supported log services.
Each log service has a unique path for this data:
| Log Service | Path Pattern |
|---|---|
| AWS CloudWatch | {ACCOUNT_NAME}/{GROUP_NAME}/dashboard/all |
| Azure Log Analytics | {ACCOUNT_NAME}_{GROUP_NAME}_dashboard_all_CL |
| Google Cloud Logging | {ACCOUNT_NAME}-{GROUP_NAME}-dashboard-all |
June 2018link
We no longer support read_start and read_end log event values.
We can now load all of your log event data into a single column (packing).
We have added logs for the following applications:
- Adwords
- DoubleClick Campaign Manager
- DoubleClick for Publishers
- DynamoDB
- Facebook Ad Insights
- Front
- Google Analytics
- Google Sheets
- HubSpot
- LinkedIn Ad Analytics
- Mandrill
- Marketo
- Optimizely
- Quickbooks
- ReCharge
- Sailthru
- Segment
- Stripe
- Xero
- Zendesk Support
- Zendesk Chat
- Jira
- Github
May 2018link
You can now navigate directly to your log service from the Connection Details page of your Fivetran dashboard.
We have added logs for the following applications:
- AdRoll
- Apple Search Ads
- Bing Ads Reports
- CloudFront
- Desk
- Dropbox
- Eloqua
- Facebook Ad Account
- Freshdesk
- FTP
- Google Cloud Storage
- HelpScout
- Intercom
- Klaviyo
- Mailchimp
- Marin Software
- Microsoft Azure Blob Storage
- Mixpanel
- MySQL
- Pardot
- Recurly
- S3
- SendGrid
- SFTP
- Yahoo Gemini
- Zuora
April 2018link
We have renamed the MessageEvent to InfoEvent.
We have added two new log events:
json_value_too_longskip_column
For more information, see our Log events documentation.
We have added support for logs for the following applications:
- Braintree
- Apple App Store (formerly iTunes Connect)
- Mavenlink