Connector Improvement: Surfacing problems more clearly in the fivetran UI
AnsweredHey team,
I wanted to check if there's any possibility of surfacing more hidden issues in the Fivetran UI, especially those related to sync health over time.
We’ve encountered several situations where critical issues - like rate limits or API restrictions - only became visible in logs after a data integrity issue was reported later on by downstream users, meaning they are losing confidence in the quality of their data via Fivetran. Some specific examples include:
-
Rate limits being hit (e.g., GitHub connector exceeding 15k requests)
-
API limits silently dropping/skipping data (e.g., the SonarQube connector only returning 10,000 records and silently failing when trying to fetch more data)
While not strictly 'errors' that break the connector, there are a lot of issues being reported in the logs that should be surfaced in the UI earlier on.
Thanks
-
Official comment
Hi Jacob,
Thank you for this feedback. This is something we can communicate more clearly in our UI, and it's in our backlog, but there are no timelines yet as of now.
But I would love to learn more about the two use cases you pointed out and what information you would like to be notified of and how. Would you be open to a quick 15 minute call?
Kristina
Please sign in to leave a comment.
Comments
1 comment