@gchen, I got this reply from the devolpers of https://www.duplicati-monitoring.com
I donāt know how this fits in your plans for the GUI/CLI, but I imagine it could be possible to use this to provide backup monitoring and some statistics which some users might want.
This would be one way to achieve this without users having to script too much.
(And if CLI could have an option to write a JSON report, CLI users could also use it)
akvarius
From: support@mittelstandsoptimierer.de
Sent: 22. august 2019 12:42
Subject: About Monitoring service for Duplicati - Will it allow other backup products?
Hi,
thank you for your email.
1. Do Mittelstandsoptimierer have plans to create a similar site for Duplicacy? (and would it be free for personal use?)
There is no definitive plan but we may do so. Of course we would appreciate if you could help us. Do you know any options in Duplicacy to get the backup reports? HTTP? Mails?
I guess a monitoring service for Duplicacy would also be donation-based.
2. If not, could it be allowed for Duplicacy users to use Duplicati-Monitoring?
(I could possibly write a script to deliver Duplicacy data in Duplicati-like
format)
Yes, you can use our service with any backup software or script that is compatible. We see that some people already use other software and we have no intentions to stop them. For example, somebody seems to be using Arq backup (https://www.arqbackup.com/) with our service.
But of course we cannot guarantuee that our service will keep working with other software that we donāt officially support.
3. If this is something you are considering, I could request the Duplicacy developer to add a feature for sending a http report for Duplicacy much like Duplicati does. (The format would be different but well defined)
That would be perfect, then it would be not a big deal to adjust or service.
[ā¦]
If Duplicacy does not implement something that is Duplicati-compatible, I would prefer if it would export the data as JSON over HTTP. What Duplicati does looks like JSON, but is not exactly JSON, and thus is not that parser-friendly. Also, I would prefer if time-values would be UNIX timestamps.
Greetings,
Christopher