# Collect restic metrics when using resticker

[Restic](https://restic.net/) is a backup software, written in Go, that stands out for the method of backup that is using, called [Content Defined Chunking](https://restic.net/blog/2015-09-12/restic-foundation1-cdc) de-duplication.
It supports multiple backends and is really easy to use.

I am using [resticker](https://github.com/djmaze/resticker), a straight-forward [docker](https://hub.docker.com/r/mazzolino/restic/) container, to run restic in Production.

It allows to schedule the backups with its built-in cron support, and allows me to send notifications for successful/failed backups.

Resticker [currently does not support](https://github.com/djmaze/resticker/issues/26) [Prometheus metrics](https://prometheus.io/), in order to monitor the status of the backups.
So I took a manual approach to collect data using the output from official restic commands, and send them to a file, which is picked up by [Node Exporter](https://github.com/prometheus/node_exporter) and is send to Prometheus server.

- The script is using [jq](https://stedolan.github.io/jq/) to parse the json response from restic.
- The script is invoked by crontab.
- `docker-compose.override.yml` example is provided, on how to send the metric file to Prometheus via Node Exporter.