Environement variable that indicates borgmatic's logfile #413

New Issue

Closed

opened 2021-04-30 14:20:32 +00:00 by Matows · 3 comments

Matows commented 2021-04-30 14:20:32 +00:00

Copy Link

What I'm trying to do and why

I'd like a way to get logs of borg and/or borgmatic output.

I'm using pushover to notify me about backup starting/ending/error but I'd like to join the log when starting/ending.

Other notes / implementation ideas

It would be great to have a environment variable reachable from after_backup, after_everything... that indicate the log file borgmatic is writting to (--log-file ?).

So it could be used like this :

...
hooks:
    after_backup:
        - mail -s "Backup completed!" admin@example.com < "${BORGMATIC_LOGFILE}"
    

Environment

borgmatic version: 1.5.13

borgmatic installation method: pip (debian package outdated)

Borg version: 1.1.9

Python version: 3.7.3

operating system and version: Debian GNU/Linux 10 (buster)

#### What I'm trying to do and why I'd like a way to get logs of borg and/or borgmatic output. I'm using [pushover](https://pushover.net) to notify me about backup starting/ending/error but I'd like to join the log when starting/ending. #### Other notes / implementation ideas It would be great to have a environment variable reachable from `after_backup`, `after_everything`... that indicate the log file borgmatic is writting to (--log-file ?). So it could be used like this : ``` ... hooks: after_backup: - mail -s "Backup completed!" admin@example.com < "${BORGMATIC_LOGFILE}" ``` #### Environment **borgmatic version:** 1.5.13 **borgmatic installation method:** pip (debian package outdated) **Borg version:** 1.1.9 **Python version:** 3.7.3 **operating system and version:** Debian GNU/Linux 10 (buster)

👍 1

witten commented 2023-03-27 19:03:54 +00:00

Owner

Copy Link

I apologize for the lengthy delay in responding to this. This seems reasonable to me—as long it's clear it'll only work if borgmatic is actually logging to a file via --log-file!

I apologize for the lengthy delay in responding to this. This seems reasonable to me—as long it's clear it'll only work if borgmatic is actually logging to a file via `--log-file`!

witten added the

good first issue

label 2023-03-27 19:04:03 +00:00

witten referenced this issue from a commit 2023-04-06 20:59:09 +00:00

Add "log_file" command hook context to NEWS and docs (#413).

witten commented 2023-04-06 21:03:06 +00:00

Owner

Copy Link

Implemented by @diivi in https://github.com/borgmatic-collective/borgmatic/pull/68. The documentation will be here shortly: https://torsion.org/borgmatic/docs/how-to/add-preparation-and-cleanup-steps-to-backups/#variable-interpolation

The summary though is that there's a new log_file hook variable you can use in your command hooks. E.g.:

...
hooks:
    after_backup:
        - mail -s "Backup completed!" admin@example.com < "${log_file}"

Implemented by @diivi in https://github.com/borgmatic-collective/borgmatic/pull/68. The documentation will be here shortly: https://torsion.org/borgmatic/docs/how-to/add-preparation-and-cleanup-steps-to-backups/#variable-interpolation The summary though is that there's a new `log_file` hook variable you can use in your command hooks. E.g.: ```yaml ... hooks: after_backup: - mail -s "Backup completed!" admin@example.com < "${log_file}" ```

witten closed this issue 2023-04-06 21:03:07 +00:00

witten referenced this issue from a commit 2023-04-06 21:12:34 +00:00

Clarify "log_file" NEWS (#413).

witten commented 2023-04-13 22:17:44 +00:00

Owner

Copy Link

This has been released in borgmatic 1.7.12! Thanks for the suggestion.

This has been released in borgmatic 1.7.12! Thanks for the suggestion.

Sign in to join this conversation.

No Branch/Tag Specified

Branches Tags

main

spot-check

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   

bug

  

data loss

  

design finalized

  

good first issue

  

new feature area

  

question / support

  

security

  

waiting for response

No Label

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

No description provided.