https://505-merge.resticprofile.pages.dev/monitoring/index.htmlStatus file PrometheusHugoen-gbhttps://505-merge.resticprofile.pages.dev/monitoring/status/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/monitoring/status/index.htmlIf you need to send your backup results to a monitoring system, use the run-after and run-after-fail scripts. For simpler needs, resticprofile can generate a JSON file with details of the latest backup, forget, or check command. For example, I use a Zabbix agent to check this file daily. Any monitoring system that reads JSON files can be integrated. To enable this, add the status file location as a parameter in your profile.https://505-merge.resticprofile.pages.dev/monitoring/prometheus/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://505-merge.resticprofile.pages.dev/monitoring/prometheus/index.htmlResticprofile can generate a Prometheus file or send the report to a Pushgateway. Currently, only the backup command generates a report. Below is a configuration example for generating a file and sending it to a Pushgateway: ​ 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 Set extended-status to true to access all available metrics. For details, see Extended status.