Log output doesn't contain config filename anymore #1051

New issue

Closed

opened 2025-04-02 15:13:13 +00:00 by arjan-s · 5 comments

arjan-s commented 2025-04-02 15:13:13 +00:00

Copy link

What I'm trying to do and why

On my setup, borgmatic runs 6 different configuration files. In the past, the borgmatic output would contain 6 lines like this one:

INFO Successfully ran configuration file /etc/borgmatic.d/docs.yml

This helped my inform my monitoring system that a certain backup job was successful.
A recent version of borgmatic has changed this output to 6 times this line:

INFO Successfully ran configuration file

I couldn't find why this change was made, but it has made monitoring my backups more difficult.

This is why I'm requesting to re-add the configuration filename to borgmatic's output.

Steps to reproduce

Run borgmatic with multiple configuration files.

Actual behavior

Backup job filename is not included in the output anymore.

Expected behavior

Backup job filename should still be included in the output.

Other notes / implementation ideas

No response

borgmatic version

1.9.14

borgmatic installation method

NixOS module

Borg version

1.4.0

Python version

3.12.9

Database version (if applicable)

No response

Operating system and version

NixOS 25.05 (Warbler) (unstable)

### What I'm trying to do and why On my setup, borgmatic runs 6 different configuration files. In the past, the borgmatic output would contain 6 lines like this one: ``` INFO Successfully ran configuration file /etc/borgmatic.d/docs.yml ``` This helped my inform my monitoring system that a certain backup job was successful. A recent version of borgmatic has changed this output to 6 times this line: ``` INFO Successfully ran configuration file ``` I couldn't find why this change was made, but it has made monitoring my backups more difficult. This is why I'm requesting to re-add the configuration filename to borgmatic's output. ### Steps to reproduce Run borgmatic with multiple configuration files. ### Actual behavior Backup job filename is not included in the output anymore. ### Expected behavior Backup job filename should still be included in the output. ### Other notes / implementation ideas _No response_ ### borgmatic version 1.9.14 ### borgmatic installation method NixOS module ### Borg version 1.4.0 ### Python version 3.12.9 ### Database version (if applicable) _No response_ ### Operating system and version NixOS 25.05 (Warbler) (unstable)

witten referenced this issue from a commit 2025-04-02 16:50:51 +00:00

Add configuration filename to "Successfully ran configuration file" log message (#1051).

witten commented 2025-04-02 16:55:03 +00:00

Owner

Copy link

Thanks for filing this! I generally don't recommend parsing borgmatic's log output (except for --json output), but I agree that this is a regression that should be fixed even just for uses cases like reading logs.

So I've fixed it in main, and it'll be part of the next release! Note however that the filename is now at the start of the log message instead of the end, which is more consistent with other log messages.

Also: If there's anything borgmatic can do to make your monitoring use cases easier or more officially supported, please let me know! (Ideally on a separate ticket.) Maybe something like #617 would be useful.

Thanks for filing this! I generally don't recommend parsing borgmatic's log output (except for `--json` output), but I agree that this is a regression that should be fixed even just for uses cases like reading logs. So I've fixed it in main, and it'll be part of the next release! Note however that the filename is now at the start of the log message instead of the end, which is more consistent with other log messages. Also: If there's anything borgmatic can do to make your monitoring use cases easier or more officially supported, please let me know! (Ideally on a separate ticket.) Maybe something like #617 would be useful.

witten closed this issue 2025-04-02 16:55:03 +00:00

arjan-s commented 2025-04-02 19:50:35 +00:00

Author

Copy link

Thank you for the quick answer and resolution! I'm already using borgmatic rinfo --json for getting repository info for my monitoring.
What I wanted to accomplish here (and had accomplished before it changed) was a simple verification that the last backup run was successful for each config file (taken from journalctl).
The JSON output from #617 would indeed be very helpful as well. Possibly configured the same way as the third party monitoring integrations or like the hooks.
But I'm already happy with what I have now, so please don't sink any time into it for my sake. :)

Thank you for the quick answer and resolution! I'm already using `borgmatic rinfo --json` for getting repository info for my monitoring. What I wanted to accomplish here (and had accomplished before it changed) was a simple verification that the last backup run was successful for each config file (taken from journalctl). The JSON output from https://projects.torsion.org/borgmatic-collective/borgmatic/issues/617 would indeed be very helpful as well. Possibly configured the same way as the third party monitoring integrations or like the hooks. But I'm already happy with what I have now, so please don't sink any time into it for my sake. :)

witten commented 2025-04-02 21:44:04 +00:00

Owner

Copy link

Sounds good! Thanks for the additional context.

Sounds good! Thanks for the additional context.

witten commented 2025-04-06 15:42:44 +00:00

Owner

Copy link

Released in borgmatic 2.0.0!

Released in borgmatic 2.0.0!

arjan-s commented 2025-04-06 20:17:39 +00:00

Author

Copy link

Awesome, thank you!

Awesome, thank you!

👍 1

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#1051

No description provided.