Release Notes

---

December 2022

We now generate the CANCELED sync status for the sync_end log event in .

---

January 2022

We have added the sync_id field as a common field of the .

---

December 2021

We now generate the sync_end log event in for every possible sync status:

• SUCCESSFUL
• FAILURE
• FAILURE_WITH_TASK
• RESCHEDULED

Previously, we generated the sync_end log event only for successful syncs.

---

September 2021

We now generate the change_schema_config_via_api log event in our logs when you change a schema sync configuration using our . See our for details.

---

August 2021

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 .

---

December 2020

Fivetran now supports flushing 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 Monitor Log	{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 .

Fivetran now supports flushing 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 Monitor Log	{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 .

---

November 2020

We have added a new log event, diagnostic_access_granted. Read our for more information.

---

September 2020

We have added a new log event, change_schema_config_via_sync. See our for more information.

---

October 2018

Fivetran now supports flushing 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 Monitor Log	{ACCOUNT_NAME}_{GROUP_NAME}_dashboard_all_CL
Google Cloud Logging	{ACCOUNT_NAME}-{GROUP_NAME}-dashboard-all

---

June 2018

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 2018

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
• Email
• 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 2018

We have renamed the MessageEvent to InfoEvent.

We have added two new log events:

• json_value_too_long
• skip_column

For more information, see our .

We have added support for logs for the following applications:

• Braintree
• Apple App Store (formerly iTunes Connect)
• Mavenlink