Have EventBridge send an error message to Atlas to stop flow of Trigger data at the source
Currently, once a Mongo Trigger makes a successful hand-off to EventBridge, it doesn't have insight into EventBridge issues landing the data in its destination. Currently, you have to set up separate code to process failed EventBridge events using the DeadLetter queue. You also need to set up a process to integrate this data from the DeadLetter queue back into the EventBridge destination. If the requested functionality existed, you would only need the Trigger restart process to handle any failure in the data stream from Mongo to EventBridge destination. This will also enable a single place to monitor the data stream.
1
vote
James
shared this idea