coop-cloud/traefik
7
2
Fork 19
Code Issues 14 Pull Requests 5 Releases Wiki Activity

feat: access logs #126

Open
fauno wants to merge 4 commits from access-log into master
pull from: access-log
merge into: coop-cloud:master
Conversation 6 Commits 4 Files Changed 4
+31 -1
fauno commented 2026-07-28 17:20:12 +00:00
Owner
Copy Link
Copy Source
<!-- Thank you for doing recipe maintenance work! Please mark all checklist items which are relevant for your changes. Please remove the checklist items which are not relevant for your changes. Feel free to remove this comment. --> * [x] I have deployed and tested my changes * [ ] I have [updated relevant versions in `abra.sh`](https://docs.coopcloud.tech/maintainers/upgrade/#updating-versions-in-the-abrash) * [x] I have made my environment variable changes [backwards compatible](https://docs.coopcloud.tech/maintainers/upgrade/#backwards-compatible-environment-variable-changes) * [ ] I have added a [release note entry](https://docs.coopcloud.tech/maintainers/upgrade/#creating-new-release-notes)
fauno added 1 commit 2026-07-28 17:20:12 +00:00
feat: access logs
continuous-integration/drone/pr Build is failing
Details
b4a38da20d
fauno requested review from 3wordchant 2026-07-28 17:20:13 +00:00
fauno requested review from decentral1se 2026-07-28 17:20:13 +00:00
decentral1se approved these changes 2026-07-28 17:24:58 +00:00
fauno added 1 commit 2026-07-28 17:52:12 +00:00
fix: missing compose version
continuous-integration/drone/pr Build is failing
Details
ca914a5d9f
fauno added 1 commit 2026-07-28 19:07:57 +00:00
fix: don't filter
continuous-integration/drone/pr Build is failing
Details
a7f66744a4
p4u1 reviewed 2026-07-28 20:58:36 +00:00
p4u1 left a comment
Owner
Copy Link
Copy Source

The crowd sec PR also adds access logs. #122

Will it be possible to reuse the access log implementation from here in the crowd sec PR? @devydave

The crowd sec PR also adds access logs. https://git.coopcloud.tech/coop-cloud/traefik/pulls/122 Will it be possible to reuse the access log implementation from here in the crowd sec PR? @devydave
fauno commented 2026-07-28 22:47:53 +00:00
Author
Owner
Copy Link
Copy Source

mmm according to this, crowdsec should be able to parse json logs so we could merge both implementations. maybe make crowdsec depend on access-log?

mmm [according to this, crowdsec should be able to parse json logs](https://github.com/crowdsecurity/hub/blob/master/parsers/s01-parse/crowdsecurity/traefik-logs.yaml#L25) so we could merge both implementations. maybe make crowdsec depend on access-log?
devydave commented 2026-07-31 20:35:44 +00:00
Member
Copy Link
Copy Source

mmm according to this, crowdsec should be able to parse json logs so we could merge both implementations. maybe make crowdsec depend on access-log?

that should work I can adjust it, when this is merged. One thing I am unsure should we add docs for new users that they need to include COMPOSE_FILE="$COMPOSE_FILE:compose.access-log.yml" or should I set ACCESS_LOG_ENABLED: "true" in the crowdsec compose file.

> mmm [according to this, crowdsec should be able to parse json logs](https://github.com/crowdsecurity/hub/blob/master/parsers/s01-parse/crowdsecurity/traefik-logs.yaml#L25) so we could merge both implementations. maybe make crowdsec depend on access-log? that should work I can adjust it, when this is merged. One thing I am unsure should we add docs for new users that they need to include COMPOSE_FILE="$COMPOSE_FILE:compose.access-log.yml" or should I set ACCESS_LOG_ENABLED: "true" in the crowdsec compose file.
fauno commented 2026-07-31 20:57:37 +00:00
Author
Owner
Copy Link
Copy Source

@devydave i'm not sure what is best:

  • remind users to enable access logs and possibly fail if they don't
  • disable crowdsec's access log acquisition if access log is disabled (afaict it's optional, right? is it a privacy issue too? as in are they being sent to crowdsec servers?)
  • add the ACCESS_LOG_ENABLED on compose.crowdsec.yml without adding the volume, so if you want persistent storage you need to enable compose.access-log.yml yourself
  • chain the two compose files COMPOSE_FILE="$COMPOSE_FILE:compose.access-log.yml:compose.crowdsec.yml so enabling crowdsec also enables access-log without further reading
@devydave i'm not sure what is best: * remind users to enable access logs and possibly fail if they don't * disable crowdsec's access log acquisition if access log is disabled (afaict it's optional, right? is it a privacy issue too? as in are they being sent to crowdsec servers?) * add the `ACCESS_LOG_ENABLED` on `compose.crowdsec.yml` without adding the volume, so if you want persistent storage you need to enable `compose.access-log.yml` yourself * chain the two compose files `COMPOSE_FILE="$COMPOSE_FILE:compose.access-log.yml:compose.crowdsec.yml` so enabling crowdsec also enables access-log without further reading
fauno added 1 commit 2026-07-31 21:05:35 +00:00
doc: log rotation
continuous-integration/drone/pr Build is failing
Details
68f07eff9b
p4u1 reviewed 2026-08-01 09:19:29 +00:00
.env.sample
@@ -227,1 +227,4 @@
#ONION_ENABLED=1
## Keep access logs on a volume.
# You'll need to setup rotation yourself and send the USR1 signal to
p4u1 commented 2026-08-01 09:19:29 +00:00
Owner
Copy Link
Copy Source

Can you give an example of how to setup the log rotation?

Can you give an example of how to setup the log rotation?
❤️ 1
Some checks are pending
continuous-integration/drone/pr Build is failing
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
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.
Reviewers
No Reviewers
3wordchant
decentral1se
p4u1
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
Assignees
Clear assignees
3wordchant aadil (Aadil Ayub) abra-bot (Abra Bot) ammaratef45 amras (Sarma) BornDeleuze Brooke carla cas (Cassowary) coopcloud decentral1se (d1) fauno (fauno) javielico (Javielico) jjsfunhouse kawaiipunk (KawaiiPunk) knoflook moosemower moritz notplants oxaliq (sorrel) p4u1 renovate-bot (Comrade Renovate Bot) simon stevensting trav yksflip
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/traefik#126
Delete Branch "access-log"

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?