DumbMonit
IntegrationsStorage and backups
Monitor Kopia with DumbMonit
BetaA Kopia server through its REST API: the last snapshot of each source (age, errors, size, files), sources that missed their schedule, and the repository connection.
DocumentationOfficial website: Kopia
Product descriptions are in English, as in the product. The page labels follow your language.
What DumbMonit watches
Built from the Kopia server's source and API behaviour, not yet tested against a real server. Tell us what your server answers differently. A Kopia server through its REST API: the last snapshot of each source (age, errors, size, files), sources that missed their schedule, and the repository connection.
Examples
- Kopia server
- KopiaUI
- Kopia in Docker
How it connects
What you need
- Server user name and passwordThe user name and password the Kopia server was started with.
No account needed.
Network ports to open
51515/TCPServer API (HTTPS, default)
Setup steps: Start the Kopia server with its own user name and password
On the machine that runs the backups, start the Kopia server with a generated certificate and its own user name and password.
kopia server start --address=0.0.0.0:51515 --tls-generate-cert --server-username=dumbmonit --server-password=PASTE-A-LONG-RANDOM-PASSWORDCheck that the repository is connected to that server and that the DumbMonit server can reach port 51515.
In DumbMonit, enter the server address (for example nas.lan) with that user name and password.
Tick Accept an unverifiable certificate: the generated certificate is self-signed. If the server runs with --insecure, choose the http protocol instead.
Heads-up. Kopia's API has no read-only account: the server password also lets its holder start and delete snapshots. DumbMonit only reads, but keep port 51515 on your local network.