coop-cloud/backup-bot-two
coop-cloud
/
backup-bot-two
6
0
Fork 3
Code Issues 12 Pull Requests 1 Packages Projects Releases Wiki Activity

Logging format? #27

New Issue
Closed
opened 2023-09-07 23:42:28 +00:00 by moritz · 3 comments
moritz commented 2023-09-07 23:42:28 +00:00
Member
Copy Link

At the moment I use the default logging format from the python logging library. I think a json output would be better to parse, especially for monitoring systems like grafana. Does anyone has some recommendations for logging formats?

I am also not sure how verbose the backupbot should be at which log level.

At the moment I use the default logging format from the [python `logging`](https://docs.python.org/3/library/logging.html) library. I think a json output would be better to parse, especially for monitoring systems like grafana. Does anyone has some recommendations for logging formats? I am also not sure how verbose the backupbot should be at which log level.
moritz added this to the backupbot revolution project 2023-09-07 23:42:35 +00:00
3wordchant commented 2023-11-12 00:53:18 +00:00
Owner
Copy Link

personally i don't love json logs, but if that's the group preference i'm happy to go with it.

I am also not sure how verbose the backupbot should be at which log level.

current verbosity seems reasonable to me, we can always tweak as we go

personally i don't love json logs, but if that's the group preference i'm happy to go with it. > I am also not sure how verbose the backupbot should be at which log level. current verbosity seems reasonable to me, we can always tweak as we go
moritz commented 2023-11-14 18:20:18 +00:00
Author
Member
Copy Link

It don't have to be json, but I thought about some kind of structured logging so it could easily be parsed.

It don't have to be json, but I thought about some kind of structured logging so it could easily be parsed.
moritz commented 2023-11-23 20:15:45 +00:00
Author
Member
Copy Link

Structured json logging is now only activated using the -m flag: 15275b2571
This flag is set per default inside the cron. So the automatic backup can be parsed by logging aggregation tools.

Structured json logging is now only activated using the `-m` flag: https://git.coopcloud.tech/coop-cloud/backup-bot-two/commit/15275b257192ff49a96a64600ee5df7d0566506f This flag is set per default inside the cron. So the automatic backup can be parsed by logging aggregation tools.
❤️ 1
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
main
feature/dockerfile
bb2-classic
feature/selective_paths
enable-label
backupbot_revolution
backup_volumes
multi_path
0.2.0+1.0.0
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
Projects
Clear projects
No project
backupbot revolution
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: coop-cloud/backup-bot-two#27
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?