Fivetran wants to provide more information about how your connectors are running so you can diagnose your own issues. Fivetran Log Connector syncs the logs to a table. It also syncs metadata about your connectors.
|dbt Package||check||Get the package|
Follow our step-by-step setup guide to set up your Fivetran Log Connector.
Fivetran Log Connector syncs the latest logs generated from your connectors to your destination. It syncs additional information about the account, destination, connectors, users, and membership present in your Fivetran account. We sync all these details at a destination level.
If you are an account owner, you can also choose to sync all the connector logs for all the destinations in your account. By limiting this option to account owners, we ensure that Powered By Fivetran (PBF) customers cannot access logs that belong to other PBF customers on the same account.
This schema applies to all Fivetran Log Connectors.
Schema notes - Important tableslink
ACTIVE_VOLUME table provides details of the monthly active rows (MAR) for each destination schema, the associated tables, and the time when the MAR is calculated.
||The ID of the connector for which the MAR is calculated.|
||The number of distinct primary keys synced for the connector.|
||The timestamp when the MAR is calculated.|
||The destination schema name for which the MAR is calculated.|
||The table name associated with the MAR.|
LOG table provides a record of events that have occurred for a particular connector along with the event details.
||The ID of the connector for which the event is logged.|
||The event type. Events can be classified as a warning, an error, or just an information log.|
||The routine involved in the log.|
||The details of the event in JSON format.|
CREDITS_USED table provides information about the monthly credit usage summary.
||The ID of the destination for which the credits are used.|
||The month in which the credits are used.|
||The number of credits used during the month.|
These logs contain information about errors that connectors encounter. You can track events, such as a failure or an authentication error from the logs.
The following table lists the errors with a
SEVERE severity level:
|SEVERE||error||type||dynamically obtained from response|