Skip to content

Conversation

@jeankhawand
Copy link

This change adds the ENABLE_JSON_LOGGING option to export restic metadata in JSON format. The goal is to improve accessibility by allowing users to utilize tools like jq to process the metadata. This enables users to create external scripts for extracting metadata and sending notifications using run_commands.

update doc and include notify script as sample to send backup metadata via apprise

Export LOG_FILE and create docker-compose for contributing

  • export LOG_FILE so it will be available for subprocess executed via run_commands
  • Add docker-compose.contribute.yml facilitate contributing process
  • make notify executable and copy it to /usr/local/bin
  • notify: update content to only include summary and errors for now. jq was complaining on payload too large when using verbose mode.
  • update doc

This change adds the `ENABLE_JSON_LOGGING` option to export restic metadata in JSON format. The goal is to improve accessibility by allowing users to utilize tools like `jq` to process the metadata. This enables users to create external scripts for extracting metadata and sending notifications using `run_commands`.

update doc and include notify script as sample to send backup metadata via apprise

Export `LOG_FILE` and create docker-compose for contributing

- export `LOG_FILE` so it will be available for subprocess executed via `run_commands`
- Add docker-compose.contribute.yml facilitate contributing process
- make `notify` executable and copy it to /usr/local/bin
- notify: update content to only include summary and errors for now. jq was complaining on payload too large when using verbose mode.
- update doc
@nprime496
Copy link

Hi @jeankhawand please any idea why it is still not deployed ?

@jeankhawand
Copy link
Author

@djmaze that's will also make it easy to restore snapshots in the futur
image

Copy link
Owner

@djmaze djmaze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry for the late reply.. This looks good to me! But will need a test, see below.

- `SKIP_INIT` - Skip initialization of the restic repository, even if it can not be accessed.
- `SKIP_INIT_CHECK`- Do not fail, if initialization of the restic repository fails for whatever reason.

- `ENABLE_JSON_LOGGING` = Converts Restic's standard output to JSON format. This allows users to leverage tools like `jq` to extract specific fields from the metadata. Additionally, it supports calling external scripts for further processing, such as [executing commands after a backup](#execute-commands-after-backup). For example:
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this should also document that the LOG_FILE env variable is set for the commands to be used.

@@ -0,0 +1,72 @@
version: "3.3"
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure why you added this file and what the name is exactly about? IMO we can just remove this.

@@ -0,0 +1,83 @@
#!/bin/bash
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This functionality should also be tested. I will add a test.

@goremykin
Copy link

@jeankhawand, Hi! I'm also thinking about visualization and notifications now. What your setup is in the end? Did you switch to another wrapper or do you use your fork?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants