feat: access log coop-cloud/traefik#126 #27

Open
fauno wants to merge 2 commits from access-log into main
Owner
No description provided.
fauno requested review from 3wordchant 2026-07-28 17:26:41 +00:00
fauno requested review from decentral1se 2026-07-28 17:26:41 +00:00
decentral1se left a comment
Owner

LGTM but I don't use this recipe!

LGTM but I don't use this recipe!
Owner

Traefik PR was merged and a new version released

Traefik PR was merged and a new version released
ammaratef45 changed target branch from alloy to main 2026-09-02 22:57:41 +00:00
fauno added 1 commit 2026-09-11 09:54:56 +00:00
fauno force-pushed access-log from 36ef86e8b7 to f9820da529 2026-09-11 09:54:56 +00:00 Compare
Author
Owner

ready for review!

ready for review!
dannygroenewegen left a comment
Owner

Include a short line for the release notes.

Include a short line for the release notes.
.env.sample Outdated
@@ -128,1 +128,4 @@
#ALERT_NODE_MEMORY_USAGE=85
# Tell Traefik to keep access logs (could be very verbose)
ALLOY_ACCESS_LOGS=false
Owner

In 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?

In 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?
Owner

preferably: make it

#ALLOY_ACCESS_LOGS=true

that way you only have to comment in if you want to enable it.

preferably: make it ``` #ALLOY_ACCESS_LOGS=true ``` that way you only have to comment in if you want to enable it.
Author
Owner

done

done
Owner

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 :)
fauno added 1 commit 2026-09-25 14:04:20 +00:00
Author
Owner

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.
git fetch -u origin access-log:access-log
git checkout access-log
Sign in to join this conversation.