How to not lose incoming events during incidents/deploy #1777
Unanswered
Horbatenko
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I’ve been wondering how we can ensure stable event processing when WAHA instances or services that read their data are down.
In the case of deployments, we can use a strategy that keeps at least one active WebSocket connection at all times. But how can we cover the pipeline in the event of an incident and fetch all the affected data?
After reading the docs and reviewing the available APIs, I came up with an idea for a “backfill” process, which would:
/api/{session}/chats/overviewby comparing last message timestamps/api/{session}/chats/{chatId}/messagesHowever, this approach sounds quite complicated, so I was wondering if there’s an easier solution.
Ideally – all “unread” data would be pushed into an existing WebSocket connection so that the gap is resolved automatically.
Thanks in advance for any suggestions 🙏
Beta Was this translation helpful? Give feedback.
All reactions