Support custom headers in Traefik Logs, e.g. Cloudflare's cf-connecting-ip
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
When using cloudflare domains with proxy turned on, the client's IP is passed in the header with the key CF-Connecting-IP
We have been receiving many 404s to paths that do not exist in our applications.
Currently, the Traefik request logs only shows the IP of the client, which would be Cloudflare.
Describe the solution you'd like
It would be helpful if we can also extract custom values from the header to include in the logs.
That way, we can include the CF-Connecting-IP.
Describe alternatives you've considered
Printing out the IP at the application level
Additional context
No response
Will you send a PR to implement it?
No
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Traefik request-log configuration and the TypeScript code that assembles or serializes request-log fields. Check how custom headers such as CF-Connecting-IP could be selected, then verify that the header value appears in request logs while existing client-IP logging remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100