Restic-exporter multi-repo?

Hello everyone,
I want to use “restic-exporter” with multiple repositories.
I have the same password for all these repositories, is it possible, or do I need to modify the code accordingly for it to work?

The goal: I am using Prometheus and Grafana on an external server, and I would like to have my repositories monitored on it.

My example configuration file with multiple users: RESTIC_REPOSITORY=rest:https://login:password@url:port/path/users/

ps: I manage to start restic-exporter with a single repository.

Thank you for your help.

Welcome to the restic forums :slight_smile:
This seems like a question that would be better asked to the restic-exporter author(s).

It’s probably worth raising an issue in their github and asking nicely there?

That said, maybe there’s another restic-exporter user on the forums here who might know!

Thank you for your response.
Indeed, I will ask them the question. There might be another restic-exporter user on the forums here who might know! It’s quite likely.

If you do not mind using rustic (generally competible with restic), I am currently starting the rustic-exporter for my homelab dashboard.

In fact, I’m more like to use restic, however we all knew the restic library issue… It would be easier to maintain a project by using a libary instead of external command. Thus, finally I choose rustic.

Could you write the instructions for launching your project as well? I’m just planning to use a rest-server with multiple repositories. And I wanted to track their status.

You have the keys to launch rustic-exporter, but I couldn’t find the file itself.

P.S. English is not my native language, so the text is an automatic translation.

I was quite unhappy with the existing solutions, so I built an exporter for my own needs. It supports multiple repositories in subdirectories, even with different passwords for each repository. I made it smart by only redoing resource-intensive tasks if something has changed in a repository. I use it for over 1,000 repositories, some of which are over 30 TB in size.

There is still room for improvement, such as the ability to set the ‘group-by’ flag, which is currently hardcoded to ‘host, tags’ because I needed it for my setup.

If anyone finds this useful or needs more metrics or features, just open an issue. For me it’s perfect at the moment.

It is available as prebuilt binaries or as a docker image.