We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hey @chronark
Since there have been two tinybird ingest outages within the last month. (Feb 10 and March 9)
Any thoughts how you are currently handling failed tinybird requests?
Was thinking to add error handling and retries to my implementation along the lines of this here: https://www.tinybird.co/docs/guides/ingest-from-the-events-api.html#error-handling-and-retries
How are you doing it at unkey?
The text was updated successfully, but these errors were encountered:
It retries once already, but only on 429 errors. We can improve that, but I don't see a good solution for buffering long outages within this lib.
We're going to buffer and batch all messages in a cloudflare queue soon (similar to what we do for axiom logs already)
Sorry, something went wrong.
Nice! Would love to learn more about this when you release it for unkey
No branches or pull requests
Hey @chronark
Since there have been two tinybird ingest outages within the last month. (Feb 10 and March 9)
Any thoughts how you are currently handling failed tinybird requests?
Was thinking to add error handling and retries to my implementation along the lines of this here:
https://www.tinybird.co/docs/guides/ingest-from-the-events-api.html#error-handling-and-retries
How are you doing it at unkey?
The text was updated successfully, but these errors were encountered: