I want to have embedded pagerduty notifications (the same as healthchecks etc.)
As a work around I have implemented a bash script for my setup atm. See the source on the Github: https://github.com/earthquakesan/borg-lab/blob/master/playbooks/roles/borgmatic/templates/pagerduty-notification.sh.j2
When there is an error, borgmatic should automatically send incident to pagerduty on that routing_key.
Pagerduty can only create triggers or incidents (it is incident responding tool). routing_key is a unique key to send notifications to a Service (internal pagerduty object).
I’m certainly not opposed to this, but are you aware that Healthchecks, Cronitor, and Cronhub all have PagerDuty integration? So today, you could configure borgmatic to ping one of Healthchecks/Cronitor/Cronhub, and then configure that to notify you of failures via PagerDuty.
Is the problem that you don’t want to use a service like Healthchecks/Cronitor/Cronhub, and just want to get PagerDuty notifications directly? Thanks!
Those are all additional services --> management overhead + need to pay for them. While I just need simply notifications by PagerDuty if a backup has failed.
I could potentially run healthchecks inside our data center and ping PagerDuty from there. But I don’t have to deploy it just for this purpose. Sounds like an overkill for me.
Got it, understood. Thanks for the explanation. This looks like it may be the place to start: https://v2.developer.pagerduty.com/docs/events-api-v2
ok, thx, I will implement when I have time. Also will look into Healthchecks in parallel as it still might be useful.
I put that API link there for whomever picks up the ticket.. wasn’t suggesting that had to be you! But PRs of course are more than welcome.
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?