No Branch/Tag Specified
main
renovate/docker-29.x
feature/makeDeleteDefault
restic-exporter
cmd-setup-restic-s3
prom-mon
feature/dockerfile
bb2-classic
feature/selective_paths
list
enable-label
backupbot_revolution
backup_volumes
multi_path
2.4.0+2.4.0
2.3.0+2.3.0-beta
2.2.0+2.2.1-beta
2.1.0+2.2.0-beta
2.0.1+2.1.1-beta
1.0.0+2.0.0-beta
0.2.0+1.0.0
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
backupbot revolution
Done
Assignees
3wordchant
aadil (Aadil Ayub)
abra-bot (Abra Bot)
ammaratef45
amras (Sarma)
Apfelwurm
appletalk
arjan
basebuilder
BornDeleuze
Brooke
carla
cas (Cassowary)
codegod100
coopcloud
cyrnel
decentral1se (d1)
dede
devydave
fauno (fauno)
flancian
Frando
iexos
jade (Jade Ambrose)
javielico (Javielico)
jjsfunhouse
jmakdah2 (Jackie Makdah)
joe-irving (Joe Irving)
kawaiipunk (KawaiiPunk)
knoflook
kolaente
lambdabundesverband
linnealovespie (April)
marlon (marlon)
mayel
mirsal
moosemower
moritz
nicksellen (Nick Sellen)
notplants
oxaliq (sorrel)
p4u1
pau
pharaohgraphy (Andrew 🐦🔥❤️🔥✴️)
PhiNatalie
renovate-bot (Comrade Renovate Bot)
ripclap
rix
rscmbbng
sef (sef)
simon
sixsmith (Sixsmith)
stevensting
tobias
trav (Trav Fryer)
val (val (he/him))
vaznasty
virtualboys
wolcen (Chris Thompson)
wykwit
xynosis
yksflip
Clear assignees
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/backup-bot-two#27
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
At the moment I use the default logging format from the python
logginglibrary. 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.
personally i don't love json logs, but if that's the group preference i'm happy to go with it.
current verbosity seems reasonable to me, we can always tweak as we go
It don't have to be json, but I thought about some kind of structured logging so it could easily be parsed.
Structured json logging is now only activated using the
-mflag:15275b2571This flag is set per default inside the cron. So the automatic backup can be parsed by logging aggregation tools.