Other: Add UUIDs to notifications so we can link creation and resolution notifications
Answered
Currently, we have notifications set up for our connectors, which trigger alerts, e.g. when a sync is delayed.
For example, we would typically get these 2 notifications sent via email:
- Subject: [Fivetran] Sync Delayed - <connector name>; Sent at 2025-05-01 01:00 UTC; Content: Your Sync is Delayed
...
Your connection's sync is delayed in sending data to your destination. We will let you know once we’ve caught up! - Subject: [Fivetran] Delay Resolved - <connector name>; Sent at 2025-05-01 01:30 UTC; Content: Delay Resolved
...
The source data in your destination is up to date.
Both these email will be related to the same sync delay but there is no way of programmatically correlating them, e.g. if they had the sync UUID.
It would be great if we could match these alerts to each other using the notification content. We use 3rd party applications to handle our alerting and monitoring, e.g. PagerDuty. If we could programmatically close incidents if we receive the Delay Resolved notification, it would mean less manual effort is spent tracking the sync.
-
Official comment
Hi Fabio,
This is a great suggestion! The request has been added to our feature improvements backlog.
To clarify your needs further—could you share more details about how you currently match notifications, and what specific notification formats or delivery channels you use most with third-party applications? Are there other types of notifications or workflows where this correlation would help?
Updates will be posted to this thread as progress is made.
Thanks,
Amy
Please sign in to leave a comment.
Comments
1 comment