Connector Improvement: Include sync_id in Functions connectors
CompletedFivetran supports some serverless-function based custom connectors, e.g. the Google Cloud Functions connector. Would it be possible to include the Fivetran sync_id as a field in the request body? This would make it easier for us to track connector runs in our metrics.
-
Official comment
Hi Jillian,
Thank you for submitting this improvement request. Can you share a little more about how you are envisaging this would work?
Are you referring to the sync_id that is included in any user visible Log message eg: the last line of this message:
{ "event" : "sync_end",
"data" : {
"status" : "SUCCESSFUL"
},
"created" : "2022-10-18T20:16:50.165Z",
"connector_type" : "azure_function",
"connector_id" : "foobar",
"connector_name" : "azure_function_aws",
"sync_id" : "fa203754-546d-4e64-81f5-eaa814c1c401" }Are you requesting we include that in the request that gets sent to your function to trigger its execution?
eg this message:{ "agent" : "<function_connector_name>/<external_id>/<schema>", "state": { "cursor": "2018-01-01T00:00:00Z" }, "secrets": { "apiToken": "abcdefghijklmnopqrstuvwxyz_0123456789" } }Thank you so muchÂ
Alison
-
Alison yes, that's exactly it. This would allow us to link our logs about the connector run with fivetran's.
Please sign in to leave a comment.
Comments
2 comments