Logs
Fivetran writes major operations performed on each of your connectors as structured log events. The logs provide an internal view of the operations happening on each of your connectors. You can connect your logging service in the Dashboard by navigating to Logs and Fivetran will write logs the specified logging service. You can build subsequent workflows off the structured logs.
Supported log services
Fivetran supports the following logging services:
You can connect one logging service per destination. Fivetran would write log events for all connectors in the destination group to the connected service. If there is a logging service that you would like but that is not yet supported, please let us know.
Log events
The log events are in a standardized JSON format:
{
"event": <Event name>,
"created": <Event creation timestamp in UTC>,
"connector_type": <Connector type>,
"connector_id": <Connector Id>
"data": {
// Event specific data. This section varies for each event
},
"exception_id": <Fivetran Error Identifier>
}
The field exception_id will only be present if Fivetran encountered an unexpected problem.
Events
Fivetran generates the following events:
| Event Name | Description |
|---|---|
| api_call | API calls made to a source service |
| sql_query | SQL query executed on a source database |
| create_schema | Schema created in destination |
| change_schema_config | Updated schema sync configuration |
| create_table | Table created in destination |
| drop_table | Table dropped from destination |
| alter_table | Add / Modify / Drop column(s) in table |
| connection_successful | Successfully established connection with source system |
| connection_failure | Failed to establish connection with source system |
| sync_start | Connector started syncing data |
| sync_end | Data syncing completed |
| import_progress | Rough estimate of import progress |
| processed_records | Number of records read from source system |
| write_to_table_start | Started writing records to destination table |
| write_to_table_end | Finished writing records to destination table |
| records_modified | Number of records modified during sync |
| status | Sync update status e.g. success, fail, rescheduled etc. |
| json_value_too_long | A JSON value was too long for your destination and had to be truncated |
| info | Info during data syncing |
| warning | Warning during data syncing |
| error | Error during data syncing |
| forced_resync_table | Forced re-sync of a table |
| forced_resync_connector | Forced re-sync of a connector |
Dashboard activity generates the following events:
| Event Name | Description |
|---|---|
| connect_bi_tool | BI tool is connected |
| update_bi_tool | BI tool configuration is updated |
| disconnect_bi_tool | BI tool is disconnected |
| create_connector | New Connection is created |
| edit_connector | Connection's credential, sync period or delay notification period is edited |
| delete_connector | Connection is deleted |
| pause_connector | Connection is paused |
| resume_connector | Connection is resumed |
| resync_connector | Connection's re-sync is triggered |
| resync_table | Connection's table re-sync is triggered |
| force_update_connector | Trigger manual update for connection |
| dismiss_warning | Warning(s) is dismissed |
| update_logger | Logging service credential is updated |
| pause_logger | Logging service is paused |
| resume_logger | Logging service is resumed |
| disconnect_logger | Logging service is disconnected |
| signin_warehouse | Sign in to destination |
| signout_warehouse | Sign out from destination |
| update_warehouse | Destination configuration is updated |
| delete_warehouse | Destination is deleted |
| test_connection | Perform connection test(s) |
| upload_file | File is uploaded |
| create_file_upload_table | Table created to load records from uploaded file |
| remove_file_upload_table | Table dropped for previously uploaded file |
| add_user | User is added to group |
| remove_user | User is removed from group |
| update_user | User details are updated |
| create_transformation | New transformation is added |
| update_transformation | Transformation is updated |
| delete_transformation | Transformation is deleted |