> For the complete documentation index, see [llms.txt](https://docs.duplicati.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplicati.com/monitoring-and-notifications/sending-reports-via-email.md).

# Sending reports

Describes how to send reports with Duplicati

Duplicati strives to make it as easy as possible to [set up backups](/getting-started/set-up-a-backup-in-the-ui.md), and using the built-in scheduler makes it easy to ensure that backups are running regularly. Because it is easy to set up a backup and forget about, it is possible to have a backup running with little interaction.

Despite all efforts to make Duplicati as robust as possible against failures, it is not possible to handle every possible problem that may arise after the initial setup. Common failure causes is revoked credentials, filled storage, missing provider updates, etc.

If you use the [TrayIcon](/duplicati-programs/trayicon.md), errors and warnings are also shown as desktop notifications. To avoid discovering too late that the backup had stopped working for some reason, it is highly recommended to set up automated monitoring of backups. Duplicati has a number of ways that you can use to send reports into a monitoring solution:

* [Duplicati Console](/monitoring-and-notifications/sending-reports-via-email/monitoring-with-duplicati-console.md)
* [Send emails](/monitoring-and-notifications/sending-reports-via-email/sending-reports-with-email.md)
* [Send Jabber/XMPP](/monitoring-and-notifications/sending-reports-via-email/sending-jabber-xmpp-notifications.md)
* [Send HTTP message](/monitoring-and-notifications/sending-reports-via-email/sending-http-notifications.md)
* [Send Telegram message](/monitoring-and-notifications/sending-reports-via-email/sending-telegram-notifications.md)
* [Send live status reports](/monitoring-and-notifications/sending-reports-via-email/sending-live-status-reports.md) (progress of running operations)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplicati.com/monitoring-and-notifications/sending-reports-via-email.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.