PagerDuty, et al.: Add actual error message on failed backup #409

New issue

Closed

opened 2021-04-09 14:15:19 +00:00 by Ghost · 3 comments

Ghost commented 2021-04-09 14:15:19 +00:00

Copy link

When a backup fails, the PagerDuty incident only includes configuration filename, hostname and server time. For debugging, it would be really helpful to have the actual error message as well.

Environment

borgmatic version: 1.5.13

borgmatic installation method: Homebrew

Borg version: borg 1.1.16

Python version: Python 3.9.4

operating system and version: macOS

When a backup fails, the PagerDuty incident only includes configuration filename, hostname and server time. For debugging, it would be really helpful to have the actual error message as well. #### Environment **borgmatic version:** 1.5.13 **borgmatic installation method:** Homebrew **Borg version:** borg 1.1.16 **Python version:** Python 3.9.4 **operating system and version:** macOS

witten commented 2022-05-23 22:42:51 +00:00

Owner

Copy link

I apologize for the lengthy delay here. Yes, this would be helpful. One of the other monitoring hooks does something similar by slurping up any borgmatic logs (including the error message) and passing everything on to the monitoring service. So in theory that code could be repurposed for the PagerDuty hook.

I apologize for the lengthy delay here. Yes, this would be helpful. One of the other monitoring hooks does something similar by slurping up any borgmatic logs (including the error message) and passing everything on to the monitoring service. So in theory that code could be repurposed for the PagerDuty hook.

witten added the

good first issue

label 2023-02-04 21:22:53 +00:00

witten referenced this issue 2023-05-04 03:11:48 +00:00

Add option to disable syslog output #675

witten referenced this issue from a commit 2025-03-04 16:55:33 +00:00

With the PagerDuty monitoring hook, send borgmatic logs to PagerDuty so they show up in the incident UI (#409).

witten commented 2025-03-04 16:57:47 +00:00

Owner

Copy link

This is implemented in main and will be part of the next release! I only implemented this for PagerDuty for now, although it'd be possible to expand it to other monitoring hooks as needed.

Documentation will be online here shortly: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pagerduty-hook

The summary is that sending (truncated) logs to PagerDuty is enabled by default and can be disabled via a new send_logs option.

This is implemented in main and will be part of the next release! I only implemented this for PagerDuty for now, although it'd be possible to expand it to other monitoring hooks as needed. Documentation will be online here shortly: https://torsion.org/borgmatic/docs/how-to/monitor-your-backups/#pagerduty-hook The summary is that sending (truncated) logs to PagerDuty is enabled by default and can be disabled via a new `send_logs` option.

witten closed this issue 2025-03-04 16:57:47 +00:00

witten commented 2025-03-10 17:30:41 +00:00

Owner

Copy link

Released in borgmatic 1.9.14!

Released in borgmatic 1.9.14!

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

main

parallel-borgmatic

command-hook-steps

2.1.7

2.1.6

2.1.5

2.1.4

2.1.3

2.1.2

2.1.1

2.1.0

2.0.13

2.0.12

2.0.11

2.0.10

2.0.9

2.0.8

2.0.7

2.0.6

2.0.5

2.0.4

2.0.3

2.0.2

2.0.1

2.0.0

1.9.14

1.9.13

1.9.12

1.9.11

1.9.10

1.9.9

1.9.8

1.9.7

1.9.6

1.9.5

1.9.4

1.9.3

1.9.2

1.9.1

1.9.0

1.8.14

1.8.13

1.8.12

1.8.11

1.8.10

1.8.9

1.8.8

1.8.7

1.8.6

1.8.5

1.8.4

1.8.3

1.8.2

1.8.1

1.8.0

1.7.15

1.7.14

1.7.13

1.7.12

1.7.11

1.7.10

1.7.9

1.7.8

1.7.7

1.7.6

1.7.5

1.7.4

1.7.3

1.7.2

1.7.1

1.7.0

1.6.6

1.6.5

1.6.4

1.6.3

1.6.2

1.6.1

1.6.0

1.5.24

1.5.23

1.5.22

1.5.21

1.5.20

1.5.19

1.5.18

1.5.17

1.5.16

1.5.15

1.5.14

1.5.13

1.5.12

1.5.11

1.5.10

1.5.9

1.5.8

1.5.7

1.5.7.dev0

1.5.6

1.5.5

1.5.4

1.5.3

1.5.2

1.5.1

1.5.0

1.4.22

1.4.21

1.4.20

1.4.19

1.4.18

1.4.17

1.4.16

1.4.15

1.4.14

1.4.13

1.4.12

1.4.11

1.4.10

1.4.9

1.4.8

1.4.7

1.4.6

1.4.5

1.4.4

1.4.3

1.4.2

1.4.1

1.4.0

1.3.26

1.3.25

1.3.24

1.3.23

1.3.22

1.3.21

1.3.20

1.3.19

1.3.18

1.3.17

1.3.16

1.3.15

1.3.14

1.3.13

1.3.12

1.3.11

1.3.10

1.3.9

1.3.8

1.3.7

1.3.6

1.3.5

1.3.4

1.3.3

1.3.2

1.3.1

1.3.0

1.2.18

1.2.17

1.2.16

1.2.15

1.2.14

1.2.13

1.2.12

1.2.11

1.2.10

1.2.9

1.2.8

1.2.7

1.2.6

1.2.5

1.2.4

1.2.3

1.2.2

1.2.1

1.2.0

1.1.15

1.1.14

1.1.13

1.1.12

1.1.11

1.1.10

1.1.9

1.1.7

1.1.6

1.1.5

1.1.4

1.1.3

1.1.2

1.1.1

1.1.0

1.0.3

1.0.2

1.0.1

1.0.0

0.1.8

0.1.7

0.1.6

0.1.5

0.1.4

0.1.3

0.1.2

0.1.1

0.1.0

0.0.7

0.0.6

0.0.5

0.0.4

0.0.3

0.0.2

Labels

Clear labels   

blocked

  

breaking

  

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No labels

blocked

breaking

bug

data loss

design finalized

good first issue

new feature area

question / support

security

waiting for response

Milestone

Clear milestone

No items

No milestone

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

borgmatic-collective/borgmatic#409

No description provided.