-
How-to guides
- π₯ Set up backups
- ποΈ Make per-application backups
- π Provide your passwords
- βοΈ Make backups redundant
- π Deal with very large backups
- π Inspect your backups
- π¨ Monitor your backups
- π€ Extract a backup
- ποΈ Backup your databases
- πΈ Snapshot your filesystems
- π§Ή Add preparation and cleanup steps
- πΎ Backup to a removable drive/server
- π§ Run arbitrary Borg commands
- π₯ Customize warnings/errors
- π¦ Upgrade borgmatic/Borg
- ποΈ Develop on borgmatic
-
Reference guides
- βοΈ Configuration
- π» Command-line
- π Source code
New in version 1.9.7 Sentry is an application monitoring service that includes cron-style monitoring (either cloud-hosted or self-hosted).
To get started, create a Sentry cron
monitor in the Sentry UI. Under
"Instrument your monitor," select "Sentry CLI" and copy the URL value for the
displayed
SENTRY_DSN
environment variable into borgmatic's Sentry data_source_name_url
configuration option. For example:
sentry:
data_source_name_url: https://5f80ec@o294220.ingest.us.sentry.io/203069
monitor_slug: mymonitor
The monitor_slug value comes from the "Monitor Slug" under "Cron Details" on
the same Sentry monitor page.
The environment value optionally specifies the environment that is used in
Sentry.
With this configuration, borgmatic pings Sentry whenever borgmatic starts,
finishes, or fails, but only when any of the create, prune, compact, or
check actions are run. You can optionally override the start/finish/fail
behavior with the states configuration option. For instance, to only ping
Sentry on failure:
sentry:
data_source_name_url: https://5f80ec@o294220.ingest.us.sentry.io/203069
monitor_slug: mymonitor
environment: myenvironment
states:
- fail
Improve this documentation
Have an idea on how to make this documentation even better? Use our issue tracker to send your feedback!