Duplicati Monitoring

w3bservice · August 8, 2020, 10:15am

Is there a possibility to monitor duplicati via prometheus? The log file Duplicati writes contains a lot of information, what is missing are simple statements, backup successful, backup failed. We have a multisystem environment, Mac Linux and Windows. We want to find out centrally if a backup has been written and the status. How do we get the logs that are written in the database? In the webui I can view the logs.
Thanks

handyguy · August 8, 2020, 1:45pm

Welcome to the Duplicati Forum, @w3bservice. Glad you’re here!

There are a couple of different options for you to get central reporting of Duplicati backup jobs. The first is dupReport, which is a Python system that grabs your result emails from Duplicati jobs and creates status reports from them. The second is duplicati-monitoring.com, which is a hosted web service that collects http status reports from your backup jobs and formats them into nice reports. Either one of those should be able to give you what you’re looking for.

ts678 · August 8, 2020, 4:42pm

I don’t think capability exists now. Can you do integration? Duplicati offers reporting options to pass basic information. JSON is a machine-friendly option. After that, the third-party reporting systems extend ability.

dupReport can actually feed Apprise that does push notifications into a lot of other systems. Prometheus seems to prefer pull, but there’s seemingly an option for push. Duplicati scripting options may help there.

github.com

duplicati/duplicati/blob/9380bbba60b2adfd90f211f412204f4e59256e09/Duplicati/Library/Modules/Builtin/run-script-example.sh#L115-L117


      
          # DUPLICATI__PARSED_RESULT
          # This is a value indicating how well the operation was performed.
          # It can take the values: Unknown, Success, Warning, Error, Fatal.

github.com

duplicati/duplicati/blob/9380bbba60b2adfd90f211f412204f4e59256e09/Duplicati/Library/Modules/Builtin/run-script-example.sh#L100-L103


      
          # DUPLICATI__RESULTFILE
          # If invoked as --run-script-after this will contain the name of the 
          # file where result data is placed. This value cannot be changed by 
          # writing it back!

w3bservice · August 9, 2020, 7:28am

how can I read the parameter %PARSEDRESULT% via shell?

ts678 · August 9, 2020, 10:17am

What OS is this? You show what looks like Windows batch file syntax but wrong exact variable name.

github.com

duplicati/duplicati/blob/082a14fc22efdef226c1bee956f85009f7104fb3/Duplicati/Library/Modules/Builtin/run-script-example.bat#L116-L118


      
          REM DUPLICATI__PARSED_RESULT

          REM This is a value indicating how well the operation was performed.

          REM It can take the values: Unknown, Success, Warning, Error, Fatal.

If Windows, try %DUPLICATI_PARSED_RESULT%. If Linux, maybe $DUPLICATI_PARSED_RESULT.
Other syntaxes are possible. It’s just an environment variable, so read the docs for whatever shell it is.

Kahomono · August 10, 2020, 9:34am

Two underscores after DUPLICATI

%DUPLICATI__PARSED_RESULT%

or $DUPLICATI__PARSED_RESULT

I am using the latter successfully

lucas.aleixo · May 23, 2024, 6:43pm

Hello everyone, I was searching some days ago prometheus exporter for duplicati and also did not found, so i’m developing an exporter, so if you are interested you can check GitHub - AleixoLucas42/duplicati-promethes-exporter: A simple prometheus exporter for Duplicati backup

DCinME · June 7, 2024, 5:19am

The last couple of days I have been getting emails from Duplicati Monitoring indicating that there has been a problem with one of my backups.

However upon investigating I am not able to determine what it means by abnormality. As far as I can tell nothing went wrong with the backup. The Duplicati UI itself shows nothing. The Duplicati Monitoring UI doesn’t show anything either. No errors, no warnings. Unqualified success.

The version of Duplicati running the job is 2.0.8.1.

Is there a way I can tell why this message is being emitted?

Edit: I’ve just had a thought, though I’m not sure if there’s truth to it. The machine in question is a laptop. The backup is scheduled to run at 1:00PM, but often the machine is not powered on and the backup is delayed until later in the afternoon/evening. Could this “lateness” be the cause of the message?

kenkendk · June 7, 2024, 11:20am

The message was developed very early in the development phase where we did not have much information to report, so the message is fairly empty.

We will update the message with more information (like the machine/backup id + name) and the reason for the message.

But yes, it could certainly be the delay that triggers it. We will add some adjustment values to the abnormality detector so you can adjust if you expect more fluctuation than we estimate.

DCinME · June 7, 2024, 7:01pm

I made sure I had the laptop powered on today so it could run “on schedule” and I didn’t receive the abnormality report when the job ran. It appears that indeed could have been the issue.