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

Add emailing capacities #139

Open
deajan opened this issue Feb 25, 2025 · 4 comments
Open

Add emailing capacities #139

deajan opened this issue Feb 25, 2025 · 4 comments
Labels
enhancement New feature or request
Milestone

Comments

@deajan
Copy link
Contributor

deajan commented Feb 25, 2025

For those who don't want to play with prometheus, add emailing capacities:

  • On success
  • On failure
  • On too old backups

Those emails should contain the last let's say 1000 lines of logs in case of failure.

@deajan deajan added the enhancement New feature or request label Feb 25, 2025
@deajan deajan modified the milestones: 3.0, 3.x Feb 25, 2025
@lcswillems
Copy link

Possible to be able to ping an URL (e.g. healthchecks.io) with "/success" added at the end of the URL in case of success and "/failure" added in case of failure?

@deajan
Copy link
Contributor Author

deajan commented Mar 4, 2025

Sure, that would be fairly easy to do.
Actually, healthechecks.io has been (quickly) discussed here #140

I don't really know that service. Does it take some POST data ? How do you identify which asset pings /success or /failure ?

@lcswillems
Copy link

I would say I could provide 2 URLs, one for success and one for failure, and npbackup calls the success one when there is success and the failure one when there is failure.

https://healthchecks.io/docs/signaling_failures/

@deajan
Copy link
Contributor Author

deajan commented Mar 5, 2025

@lcswillems Okay, I see, you just need to set an arbitrary UUID given by healthchecks in the URI.
Looks straightforward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants