palto42
/
borgmatic
forked from borgmatic-collective/borgmatic
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

per/post task log output at WARINING level #3

New Issue
Closed
opened 2020-01-05 13:07:52 +00:00 by palto42 · 0 comments
palto42 commented 2020-01-05 13:07:52 +00:00
Owner
Copy Link

What I'm trying to do and why

Currently the stdout output from pre/post taks commands is logged at WARINING level, but at least in my case the command output is just an information for the user and nothing to worry about.

Example logs at verbosity=0 from pre/post tasks using curl command to trigger an action via a web interface which returns a simple message like "Power on port 4" as a result.

Jan 05 14:02:13 myserver systemd[1]: Started bormatic backup.
Jan 05 14:02:14 myserver borgmatic[8566]: Power on port 4
Jan 05 14:02:14 myserver borgmatic[8566]: WARNING Power on port 4
Jan 05 14:02:53 myserver borgmatic[8566]: Released port 4
Jan 05 14:02:53 myserver borgmatic[8566]: WARNING Released port 4

It would be useful if this could be changed to INFO level so that it only appears at verbosity >= 1.

Maybe an extra option can be added for the loglevel of stdout from tasks.

#### What I'm trying to do and why Currently the `stdout` output from pre/post taks commands is logged at WARINING level, but at least in my case the command output is just an information for the user and nothing to worry about. Example logs at verbosity=0 from pre/post tasks using `curl` command to trigger an action via a web interface which returns a simple message like "Power on port 4" as a result. ``` Jan 05 14:02:13 myserver systemd[1]: Started bormatic backup. Jan 05 14:02:14 myserver borgmatic[8566]: Power on port 4 Jan 05 14:02:14 myserver borgmatic[8566]: WARNING Power on port 4 Jan 05 14:02:53 myserver borgmatic[8566]: Released port 4 Jan 05 14:02:53 myserver borgmatic[8566]: WARNING Released port 4 ``` It would be useful if this could be changed to INFO level so that it only appears at verbosity >= 1. Maybe an extra option can be added for the loglevel of `stdout` from tasks.
palto42 added the
enhancement
 label 2020-01-05 13:07:52 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
special_files_warn
systemd-security
develop
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No Label
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 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: palto42/borgmatic#3
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?