borgmatic-collective/borgmatic
borgmatic-collective
/
borgmatic
15
57
Fork 40
Code Issues 54 Pull Requests 1 Actions Packages Releases 121 Activity

Limit log information to monitoring sites #282

New Issue
Closed
opened 2020-01-17 08:09:20 +00:00 by ritze · 3 comments
ritze commented 2020-01-17 08:09:20 +00:00
Copy Link

What I'm trying to do and why

Don't push file changes to Healthchecks.io. Filenames are a critical information.

Other notes / implementation ideas

Introduce multiple levels:

  1. Provide all information to monitoring sites (current state with Healthchecks.io)
  2. Provide limited information like the result, e.g.
------------------------------------------------------------------------------
Archive name: machine-1970-01-01_00:00
Archive fingerprint: 0000000000000000000000000000000000000000000000000000000000000000
Time (start): Mon, 1970-01-01 00:00:00
Time (end):   Mon, 1970-01-01 00:42:00
Duration: 42 minutes 0.00 seconds
Number of files: 42
Utilization of max. archive size: 0%
------------------------------------------------------------------------------
                           Original size      Compressed size    Deduplicated size
This archive:               42.00 GB             42.00 GB            420.00 MB
All archives:              420.00 GB            420.00 GB             42.00 GB
                           Unique chunks         Total chunks
Chunk index:                      43                 1337
------------------------------------------------------------------------------
  • Archive name
  • Archive fingerprint
  • time
  • if the checks were successful
  • ...
  1. Don't provide any log information to monitoring sites

Environment

borgmatic version: 1.4.21

borgmatic installation method: Arch Linux package: borgmatic

Borg version: borg 1.1.10

Python version: Python 3.8.1

Database version (if applicable): psql (PostgreSQL) 12.1

operating system and version: Arch Linux (Linux mars 5.4.11-arch1-1)

#### What I'm trying to do and why Don't push file changes to Healthchecks.io. Filenames are a critical information. #### Other notes / implementation ideas Introduce multiple levels: 1. Provide all information to monitoring sites (current state with Healthchecks.io) 1. Provide limited information like the result, e.g. ``` ------------------------------------------------------------------------------ Archive name: machine-1970-01-01_00:00 Archive fingerprint: 0000000000000000000000000000000000000000000000000000000000000000 Time (start): Mon, 1970-01-01 00:00:00 Time (end): Mon, 1970-01-01 00:42:00 Duration: 42 minutes 0.00 seconds Number of files: 42 Utilization of max. archive size: 0% ------------------------------------------------------------------------------ Original size Compressed size Deduplicated size This archive: 42.00 GB 42.00 GB 420.00 MB All archives: 420.00 GB 420.00 GB 42.00 GB Unique chunks Total chunks Chunk index: 43 1337 ------------------------------------------------------------------------------ ``` * Archive name * Archive fingerprint * time * if the checks were successful * ... 1. Don't provide any log information to monitoring sites #### Environment **borgmatic version:** 1.4.21 **borgmatic installation method:** Arch Linux package: [borgmatic](https://www.archlinux.org/packages/community/any/borgmatic) **Borg version:** borg 1.1.10 **Python version:** Python 3.8.1 **Database version (if applicable):** psql (PostgreSQL) 12.1 **operating system and version:** Arch Linux (Linux mars 5.4.11-arch1-1)
witten commented 2020-01-17 22:49:23 +00:00
Owner
Copy Link

Thank you for filing this! The good news is that I've got a ticket and pull request that I think might take care of this for you (once they're done...):

  • witten/borgmatic#277: A new verbosity flag to limit the borgmatic output sent to Healthchecks.
  • witten/borgmatic#272: More fine-grained control on whether file listings are sent to Healthchecks (or just better defaults).

Does that sound like it'll take care of your needs?

One other note is that in the meantime, if you reduce the global verbosity (and syslog verbosity, if using) to zero, then no filenames will be sent to Healthchecks. Not a great long-term solution, but at least a work-around for now.

Thank you for filing this! The good news is that I've got a ticket and pull request that I think might take care of this for you (once they're done...): * https://projects.torsion.org/witten/borgmatic/issues/277: A new verbosity flag to limit the borgmatic output sent to Healthchecks. * https://projects.torsion.org/witten/borgmatic/pulls/272: More fine-grained control on whether file listings are sent to Healthchecks (or just better defaults). Does that sound like it'll take care of your needs? One other note is that in the meantime, if you reduce the global verbosity (and syslog verbosity, if using) to zero, then no filenames will be sent to Healthchecks. Not a great long-term solution, but at least a work-around for now.
ritze commented 2020-01-18 09:32:50 +00:00
Author
Copy Link

That's exactly what I asked for. But unfortunately, couldn't found when I searched for those the tickets. :-/

Thank you very much.

Can I mark this ticket somehow as duplicated?

That's exactly what I asked for. But unfortunately, couldn't found when I searched for those the tickets. :-/ Thank you very much. Can I mark this ticket somehow as duplicated?
witten commented 2020-01-18 17:55:21 +00:00
Owner
Copy Link

I'll just add a comment to that ticket referencing this one, and mark this one closed. Please feel free to subscribe to witten/borgmatic#277 so you can find out when it's done!

I'll just add a comment to that ticket referencing this one, and mark this one closed. Please feel free to subscribe to https://projects.torsion.org/witten/borgmatic/issues/277 so you can find out when it's done!
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
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#282
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?