borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 54 Pull Requests 1 Actions Packages Releases 121 Activity

Healthchecks Pinging problems #828

New Issue
Closed
opened 2024-02-15 14:13:10 +00:00 by xLogiiCx · 2 comments
xLogiiCx commented 2024-02-15 14:13:10 +00:00
Copy Link

What I'm trying to do and why

Hi, i have a Problem with the Healthchecks pinging feature.
I have 7 *.yaml configs and one common.yaml.
I specified one Healthchecks pinging URL.
So when borgmatic is running it does following:

1.yaml: Pinging Healthchecks start
1.yaml: Pinging Healthchecks log
1.yaml: Pinging Healthchecks finish
2.yaml: Pinging Healthchecks start
2.yaml: Pinging Healthchecks log
2.yaml: Pinging Healthchecks finish
...

but for the last .yaml i get following problem:

last.yaml: Pinging Healthchecks start
last.yaml: Pinging Healthchecks log
last.yaml: Pinging Healthchecks finish
last.yaml: Using Healthchecks ping URL https://hc-ping.com/xxx/xxx
last.yaml: Healthchecks error: 429 Client Error: Too Many Requests for url: https://hc-ping.com/xxx/xxx

So i guess its a rate-limiting problem.
Healthchecks.io Docs:
429 rate limit exceeded Rate limit exceeded. Please do not ping a single check more than 5 times per minute.

So i guess i have following options:

  • One Ping URL for a *.config file
  • Remove one Ping feature (e.g. Log)

But is there also an option, that Borgmatic does not Ping for each *.yaml file when there is only one Ping-Url specified?
So i get one start, one Log and one Finish ping for all of my config files?

borgmatic version

1.8.8

Borg version

1.2.7

Python version

Python 3.11.5

Operating system and version

docker container ghcr.io/borgmatic-collective/borgmatic

### What I'm trying to do and why Hi, i have a Problem with the Healthchecks pinging feature. I have 7 `*.yaml` configs and one `common.yaml`. I specified one Healthchecks pinging URL. So when borgmatic is running it does following: ``` 1.yaml: Pinging Healthchecks start 1.yaml: Pinging Healthchecks log 1.yaml: Pinging Healthchecks finish 2.yaml: Pinging Healthchecks start 2.yaml: Pinging Healthchecks log 2.yaml: Pinging Healthchecks finish ... ``` but for the last `.yaml` i get following problem: ``` last.yaml: Pinging Healthchecks start last.yaml: Pinging Healthchecks log last.yaml: Pinging Healthchecks finish last.yaml: Using Healthchecks ping URL https://hc-ping.com/xxx/xxx last.yaml: Healthchecks error: 429 Client Error: Too Many Requests for url: https://hc-ping.com/xxx/xxx ``` So i guess its a rate-limiting problem. Healthchecks.io Docs: `429 rate limit exceeded Rate limit exceeded. Please do not ping a single check more than 5 times per minute.` So i guess i have following options: - One Ping URL for a `*.config` file - Remove one Ping feature (e.g. Log) But is there also an option, that Borgmatic does not Ping for each `*.yaml` file when there is only one Ping-Url specified? So i get one start, one Log and one Finish ping for all of my config files? ### borgmatic version 1.8.8 ### Borg version 1.2.7 ### Python version Python 3.11.5 ### Operating system and version docker container `ghcr.io/borgmatic-collective/borgmatic`
witten commented 2024-02-15 16:45:07 +00:00
Owner
Copy Link

Thanks for the clear explanation of the issue! My recommendation here is to go with the separate ping URL per config file approach, assuming that's not too onerous for you. borgmatic really treats each configuration file independently (as a distinct backup process) and currently doesn't do any coordination across config files.

An alternative might be to run a self-hosted Healthchecks instance, would might allow you to work around the rate limiting since you'd own the server. However with a cursory search I didn't see a Healthchecks configuration option for that.

Thanks for the clear explanation of the issue! My recommendation here is to go with the separate ping URL per config file approach, assuming that's not too onerous for you. borgmatic really treats each configuration file independently (as a distinct backup process) and currently doesn't do any coordination _across_ config files. An alternative might be to run a self-hosted Healthchecks instance, would might allow you to work around the rate limiting since you'd own the server. However with a cursory search I didn't see a Healthchecks configuration option for that.
xLogiiCx commented 2024-02-15 17:10:10 +00:00
Author
Copy Link

Thank you for your response.
Self-hosting seems like a good Idea.

Thank you for your response. Self-hosting seems like a good Idea.
👍 1
witten added the
question / support
 label 2024-02-15 17:10:46 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
spot-check
1.8.10
1.8.9
1.8.8
1.8.7
1.8.6
1.8.5
1.8.4
1.8.3
1.8.2
1.8.1
1.8.0
1.7.15
1.7.14
1.7.13
1.7.12
1.7.11
1.7.10
1.7.9
1.7.8
1.7.7
1.7.6
1.7.5
1.7.4
1.7.3
1.7.2
1.7.1
1.7.0
1.6.6
1.6.5
1.6.4
1.6.3
1.6.2
1.6.1
1.6.0
1.5.24
1.5.23
1.5.22
1.5.21
1.5.20
1.5.19
1.5.18
1.5.17
1.5.16
1.5.15
1.5.14
1.5.13
1.5.12
1.5.11
1.5.10
1.5.9
1.5.8
1.5.7
1.5.7.dev0
1.5.6
1.5.5
1.5.4
1.5.3
1.5.2
1.5.1
1.5.0
1.4.22
1.4.21
1.4.20
1.4.19
1.4.18
1.4.17
1.4.16
1.4.15
1.4.14
1.4.13
1.4.12
1.4.11
1.4.10
1.4.9
1.4.8
1.4.7
1.4.6
1.4.5
1.4.4
1.4.3
1.4.2
1.4.1
1.4.0
1.3.26
1.3.25
1.3.24
1.3.23
1.3.22
1.3.21
1.3.20
1.3.19
1.3.18
1.3.17
1.3.16
1.3.15
1.3.14
1.3.13
1.3.12
1.3.11
1.3.10
1.3.9
1.3.8
1.3.7
1.3.6
1.3.5
1.3.4
1.3.3
1.3.2
1.3.1
1.3.0
1.2.18
1.2.17
1.2.16
1.2.15
1.2.14
1.2.13
1.2.12
1.2.11
1.2.10
1.2.9
1.2.8
1.2.7
1.2.6
1.2.5
1.2.4
1.2.3
1.2.2
1.2.1
1.2.0
1.1.15
1.1.14
1.1.13
1.1.12
1.1.11
1.1.10
1.1.9
1.1.7
1.1.6
1.1.5
1.1.4
1.1.3
1.1.2
1.1.1
1.1.0
1.0.3
1.0.2
1.0.1
1.0.0
0.1.8
0.1.7
0.1.6
0.1.5
0.1.4
0.1.3
0.1.2
0.1.1
0.1.0
0.0.7
0.0.6
0.0.5
0.0.4
0.0.3
0.0.2
Labels
Clear labels   
bug

   
data loss

   
design finalized

   
good first issue

   
new feature area

   
question / support

   
security

   
waiting for response
No Label
bug
data loss
design finalized
good first issue
new feature area
question / support
security
waiting for response
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: borgmatic-collective/borgmatic#828
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?