Connector Improvement: Add ability to check Cursor date values
It would be very helpful if we, as customers, could monitor the cursor dates for a connection - similar to the values below.
"backwardCursor": "2021-05-03",
"backwardSyncLimit": "2020-08-26",
"forwardCursor": "2022-10-31"
Knowing those cursor values helps us estimate how much longer an Initial Sync may take - as well as whether the sync is up-to-date on recent data.
Support is able to check these cursor values and provide them on request - but it would be better if we could self-serve.
-
Hi Daniel, thanks for the feedback!
We have just started looking at providing more visibility into the progress of syncs, so hopefully we will be able to provide something like this in the future.
A couple of questions:
- Are the cursor values the best way for estimating the length of a sync in your opinion?
- Is there any information / data that you would want access to alongside this?
- Where would you want to be able to view this information? Possibly in the logs?
-
Thank you, Lyndsey! Ideally, a "XX% Complete" indicator would be best - but I expect that would be difficult, if not impossible, to implement since it would require Fivetran to know, or assess, how much data exists in the source system.
I latched onto the cursor values because that's what Fivetran Support are able to see. That at least gives us a sense of how far back in time the sync has gotten to. We could then compare that to the depth of the dates in the source data, to get a rough estimate. So having the cursor values appear in the UI, rather than needing a Support case to get, would be good.
If it's possible to show which tables are already done, that would be useful as well. Maybe something in the UI that shows the historical sync is complete in the following tables. That would help us know what to focus on when trying to estimate the remaining load time.
While putting such progress indicators into the logs would be OK, I would rather see them on the Connector Status page - even if it is only a rough estimate; e.g. "Estimate 24-39% Complete".
-
This is especially needed for platform use cases.
Please sign in to leave a comment.
Comments
3 comments