coop-cloud/backup-bot-two
coop-cloud/backup-bot-two
6
0
Fork 4
Code Issues 9 Pull Requests 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
Owner
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
Owner
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
Owner
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
decentral1se moved this to Done in backupbot revolution on 2025-04-20 06:03:23 +00:00
decentral1se moved this to Done in backupbot revolution on 2025-04-20 06:03:25 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
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
Milestone
No items
No Milestone
Projects
Clear projects
No project backupbot revolution
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 Apfelwurm appletalk arjan basebuilder Brooke carla cas codegod100 coopcloud decentral1se fauno flancian Frando iexos javielico kawaiipunk knoflook lambdabundesverband mac-chaffee marlon mayel mirsal moritz nicksellen notplants p4u1 pau renovate-bot rix sef simon stevensting tobias trav val virtualboys wolcen wykwit xynosis yksflip
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/backup-bot-two#27
No description provided.
Delete Branch "%!s()"

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?