Skip to content
New issue

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

solution for send failures and/or retries #2

Open
problame opened this issue Feb 6, 2024 · 0 comments
Open

solution for send failures and/or retries #2

problame opened this issue Feb 6, 2024 · 0 comments

Comments

@problame
Copy link
Owner

problame commented Feb 6, 2024

Ideas

  • keep the last panic in a file in /var/lib/*; when sending the next message, try to send that panic first (but don't catch that panic)
  • implement a local queue
    • sendmail mode is a special case that saves to /var/lib/ before entering common mode which...
    • ... for each file in /var/lib/, does one transmission attempt and deletes the file on successful transmission (opening a small window for duplicate transmission, that's ok)
    • main problem with a queue: what to do to avoid it overflowing
  • fallback notification mechanism => healthchecks.io allows pinging on failures
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant