I don't really get why all services get their own access-log flag. But I think I generally don't fully understand how the traefik-access-log architecture for the co-op cloud is supposed to work, yet. Will it require all services to set a label via the .env or ist this something I'll configure via traefik centrally? A bit of documentation would be the bare minimum I guess :)
I don't really get why all services get their own access-log flag. But I think I generally don't fully understand how the traefik-access-log architecture for the co-op cloud is supposed to work, yet. Will it require all services to set a label via the .env or ist this something I'll configure via traefik centrally? A bit of documentation would be the bare minimum I guess :)
I don't really get why all services get their own access-log flag. But I think I generally don't fully understand how the traefik-access-log architecture for the co-op cloud is supposed to work, yet. Will it require all services to set a label via the .env or ist this something I'll configure via traefik centrally? A bit of documentation would be the bare minimum I guess :)
sure! i had already forgot how it worked xD
> I don't really get why all services get their own access-log flag. But I think I generally don't fully understand how the traefik-access-log architecture for the co-op cloud is supposed to work, yet. Will it require all services to set a label via the .env or ist this something I'll configure via traefik centrally? A bit of documentation would be the bare minimum I guess :)
sure! i had already forgot how it worked xD
fauno
requested review from dannygroenewegen 2026-09-25 14:05:50 +00:00
You are not authorized to merge this pull request.
This pull request can be merged automatically.
This branch is out-of-date with the base branch
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.
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.
LGTM but I don't use this recipe!
Traefik PR was merged and a new version released
36ef86e8b7tof9820da529ready for review!
Include a short line for the release notes.
@@ -128,1 +128,4 @@#ALERT_NODE_MEMORY_USAGE=85# Tell Traefik to keep access logs (could be very verbose)ALLOY_ACCESS_LOGS=falseIn the labels, the default value is already set to false, so can these variables in .env.sample be commented out, like the other optional features?
preferably: make it
that way you only have to comment in if you want to enable it.
done
I don't really get why all services get their own access-log flag. But I think I generally don't fully understand how the traefik-access-log architecture for the co-op cloud is supposed to work, yet. Will it require all services to set a label via the .env or ist this something I'll configure via traefik centrally? A bit of documentation would be the bare minimum I guess :)
sure! i had already forgot how it worked xD
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.