mirror of
https://github.com/fosrl/pangolin.git
synced 2026-07-16 06:08:33 -05:00
[GH-ISSUE #2247] Crowdsec fails to parse Traefik Logs - WORKAROUND PROVIDED #29945
Reference in New Issue
Block a user
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?
Originally created by @rayjaymor85 on GitHub (Jan 14, 2026).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/2247
Describe the Bug
On a fresh install there are two lines missing in the default
config/traefik/traefik_config.ymlfile that will prevent the crowdsec integration from parsing traefik logs properly.I admit I'm not familiar enough with the codebase to find the template in guithub, but I was able to fix my crowdsec implementation (setup by the self-installer tool) by adding these two lines to
accessLog.fields.nameson the above mentioned file:So essentially the top of my
traefik_config.ymlfile now looks like this:after the above changes, crowdsec is now parsing my traefik logs just fine
Environment
To Reproduce
Simply perform a fresh guided installer using the automated installer including the steps to install crowdsec.
Out of the box, traefik logs don't seem to be parsing when checking against `docker exec crowdsec cscli metrics'
Performing the above mentioned changes to
config/traefik/traefik_config.ymlthen restarting the docker stack resolves the issue.Expected Behavior
docker exec crowdsec cscli metricsshould show traefik logs being parsed, with only a small percentage remaining unparsed.@AblabiX commented on GitHub (Jan 15, 2026):
already fixed
https://github.com/crowdsecurity/hub/pull/1644
@github-actions[bot] commented on GitHub (Jan 30, 2026):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Feb 13, 2026):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.