> 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/monitoring-with-duplicati-console.md).

# Monitoring with Duplicati Console

This page describes how to set up monitoring with Duplicati consoel

The Duplicati console is a [paid option](https://duplicati.com/pricing) for handling monitoring of Duplicati backups, but has a free usage tier. To get started with the console, head over to the [Duplicati Console](https://app.duplicati.com/app/getting-started/connection-key) page and sign up or log in.

If you connect your local instance to the Duplicati Console, this will automatically enable reporting to be sent from the Duplicati client to the console. Within the console, visit the [Alert Center](https://app.duplicati.com/app/alert-center/settings) to configure what notifications you want to received.

<figure><img src="https://2363712449-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7cMJiGuXy340g9NzpxLY%2Fuploads%2Fgit-blob-df5179fd624d6abcc8ed7d63cd783ff6c0ce2e8b%2FSe4cvDSJRp9MNtNW5bV0YIIBsCM.webp.avif?alt=media" alt=""><figcaption><p>Duplicati Console screenshot</p></figcaption></figure>


---

# 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/monitoring-with-duplicati-console.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.
