Other: Improve Connector Sync Logging & Visibility in the Fivetran UI
AnsweredAs a data engineer:
I want detailed, real-time/manually refreshed sync logs in the Fivetran UI (e.g. current table being processed, last successful step, and specific error context) So that I can quickly understand where a sync is failing or stalled, debug issues myself, and take corrective action without relying on customer support tickets. Today I feel pretty helpless.
Problem:
Today, the UI provides minimal visibility into sync execution. Engineers can only see that a sync has started or failed, with no insight into:
-
Which table or object is currently being processed
-
What table caused an exception
-
Whether a sync is stuck in a retry or circular failure loop
This results in wasted time, unnecessary manual cancellations, and delays while waiting for support to diagnose issues that users could resolve themselves with better logs.
Acceptance Criteria:
-
UI displays the current sync stage and table/object being processed
-
Clear error messages tied to the specific table and operation that failed
-
Visibility into retries or repeated failures (e.g. detection of looping behavior)
-
Logs accessible directly in the UI without requiring a support ticket
Value
Improved logs would significantly reduce time-to-debug, empower engineers to self-serve, and lower support load for Fivetran while improving customer trust and operational efficiency.
-
Official comment
Hi Michael,
Thanks for your feedback. Currently we allow users to export detailed logs to external logging partners (e.g. Datadog, Splunk), and you can also access logs via the Fivetran Platform connector. Have you explored those options?
At the moment we don't have plans to add logs into the dashboard, but we are exploring ways to bring more detail about ongoing syncs. Keep an eye out for more to come.
Thanks!
Amy
-
Heard. In my opinion, those options aren’t sufficient and this is still a gap in the product. They either introduce latency and/or require additional tooling and steps just to navigate the logs, putting the burden on the user (me). You clearly have logs, so hoping this request get's a good amount of upvotes to change the internal opinion at Fivetran.
This is a fairly standard feature that most EL tools already provide, even legacy tooling like Stitch.
Please sign in to leave a comment.
Comments
2 comments