In Flashduty On-call
You can get the integration Push URL in either of the following two ways.Use a dedicated integration
- In the Flashduty console, select Channels and open a channel
- Select Settings → Integrations → Dedicated integrations, then click Add integration
- Select Duplicati and click Save
- Open the generated integration card and copy the Push URL
Use a shared integration
- In the Flashduty console, go to Integration Center → Alert Events
- Select Duplicati and enter an integration name
- Configure the default route and select a channel. You can add more rules under Routing after creation
- Click Save and copy the generated Push URL
Configure Duplicati
The--send-http-json-urls option is available in Duplicati 2.0.9.106 and later. This integration was verified with 2.4.0.0.
1
Add an advanced option to the backup job
Where: Duplicati web UI › Edit backup job › Options › Advanced options › Add advanced optionFor a new job, Options is step 5.
To send for every backup job, add the same option under Settings → Default options. When running from the command line, add the argument
--send-http-json-urls="{integration_url}".2
Keep the default send level
Where: Duplicati web UI › Edit backup job › Options › Advanced options
The default of
--send-http-level is All, so a report is sent for every backup, including successful ones. A successful report is the recovery signal, so do not change it to Warning, Error or Fatal; otherwise alerts never recover.3
Verify the lifecycle
- Run a backup manually and confirm the request is accepted (no HTTP error in the Duplicati log). There is no open alert to recover yet, so Flashduty creates no alert; this is expected
- Make the backup fail temporarily, for example by renaming one backup source folder, and run it again. Confirm a Critical alert appears in Flashduty
- Undo the change and run the backup again. Confirm the alert recovers
Alert key
Flashduty builds the Alert Key fromExtra.machine-id and Extra.backup-id in the Duplicati report. The Duplicati documentation defines %machine-id% as the unique random identifier assigned to the machine and %backup-id% as the identifier assigned to the backup. We verified on a real Duplicati 2.4.0.0 that both fields stay the same when one backup job fails and then succeeds.
backup-idis a sequence number such asDB-1orDB-2on one machine and repeats across machines, so it is always combined withmachine-id- When Duplicati runs from the command line without the Duplicati server,
machine-idis empty andbackup-idis a hash of the destination, so onlybackup-idtells jobs apart - Changes to the backup name, result, time, or log lines never change the Alert Key
- A request without
backup-idis rejected because later recoveries could not be correlated
backup-id; close any open alert of the old job manually.
Status and severity
An empty or any other value, including
Unknown, is rejected. Duplicati only sends a report when a backup runs: if a job is disabled or stops running, its open alert does not recover and must be closed manually.
Troubleshooting
- Flashduty receives no events: confirm the option is
send-http-json-urlsand the Push URL is complete withintegration_key - Flashduty returns a parameter error: confirm you did not use
--send-http-urlor the form format; the report must be JSON and containExtra.backup-id - The alert does not recover: confirm
--send-http-levelis not set, or that its value includesSuccess - A warning-only run created an alert: a
Warningresult also triggers a Warning alert, for example when some source folders do not exist; after you fix the cause, the next successful run recovers it