:: INFO :: GUI: npbackup 3.1.0-beta7-windows-gui-x64-public-3.14-i 2026033101
W11 Enterprise 64bit
I entered a healthchecks.io URL and that works!
Still some questions.
- what is Timeout, the Grace Time or the timeout as per https://healthchecks.io/docs/reliability_tips/ ??
- related, what is the Timeout unit? minutes/seconds/hours?
- username/password and SSl certificate are optional?
Then I notice that when configured npbackup sends a lot of pings:
This is one example with two backup runs that failed due to VSS error, and some snapshot/ls/stats operations. Healthchecks.io keeps 100 pings history and only the last one is displayed. So when I get for example an email or Signal push then I would see two fails but also seven OK and UP after that, so basically the incidental fail get burried with pass operations.
My cronscript works with two calls, one start ping and one end ping with the exit-code of the operation. This allows me to monitor duration as well as success/error. This skips pings for all standard operations as ls or snapshots or stats.
I will use it a while and see if it can work.
:: INFO :: GUI: npbackup 3.1.0-beta7-windows-gui-x64-public-3.14-i 2026033101
W11 Enterprise 64bit
I entered a healthchecks.io URL and that works!
Still some questions.
Then I notice that when configured npbackup sends a lot of pings:
This is one example with two backup runs that failed due to VSS error, and some snapshot/ls/stats operations. Healthchecks.io keeps 100 pings history and only the last one is displayed. So when I get for example an email or Signal push then I would see two fails but also seven OK and UP after that, so basically the incidental fail get burried with pass operations.
My cronscript works with two calls, one start ping and one end ping with the exit-code of the operation. This allows me to monitor duration as well as success/error. This skips pings for all standard operations as ls or snapshots or stats.
I will use it a while and see if it can work.