https://470-merge.resticprofile.pages.dev/status/index.htmlIf you need to escalate the result of your backup to a monitoring system, you can definitely use the run-after and run-after-fail scripting. But sometimes we just need something simple that a monitoring system can regularly check. For that matter, resticprofile can generate a simple JSON file with the details of the latest backup/forget/check command. For example I have a Zabbix agent checking this file once a day, and so you can hook up any monitoring system that can interpret a JSON file.Hugoen-gbhttps://470-merge.resticprofile.pages.dev/status/prometheus/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://470-merge.resticprofile.pages.dev/status/prometheus/index.htmlresticprofile can generate a prometheus file, or send the report to a push gateway. For now, only a backup command will generate a report. Here’s a configuration example with both options to generate a file and send to a push gateway: ​ toml yaml hcl json version = "1" [root] prometheus-save-to-file = "root.prom" prometheus-push = "http://localhost:9091/" [root.backup] extended-status = true no-error-on-warning = true source = [ "/" ] version: "1" root: prometheus-save-to-file: "root.prom" prometheus-push: "http://localhost:9091/" backup: extended-status: true no-error-on-warning: true source: - / "root" = { "prometheus-save-to-file" = "root.prom" "prometheus-push" = "http://localhost:9091/" "backup" = { "extended-status" = true "no-error-on-warning" = true "source" = ["/"] } } { "version": "1", "root": { "prometheus-save-to-file": "root.prom", "prometheus-push": "http://localhost:9091/", "backup": { "extended-status": true, "no-error-on-warning": true, "source": [ "/" ] } } } Note Please note you need to set extended-status to true if you want all the available metrics. See Extended status for more information.