feat: add global TCP access logging #11998
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Implement a TCP access log handler that logs connection start and end events, including client/server addresses, bytes in/out, duration, client certificate and errors. - Integrate the TCP access log middleware globally at the entrypoint/server level, mirroring HTTP access log behavior. - Enable TCP access logging via the global static configuration (accessLog), with no per-router or manual wiring required. - Ensure thread-safe log writes and support for both JSON and text log formats.
kevinpollet
added
kind/enhancement
Member
|
Hello @Kronusus and thanks for your contribution, We have set the status to "design-review" to allow us to check the PR and ensure there is no deep impact on Traefik before moving forward. We will keep you updated once the analysis is done. |
|
How is that design-review going? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Implement a TCP access log handler that logs connection start and end events, including client/server addresses, bytes in/out, duration, client certificate and errors. - Integrate the TCP access log middleware globally at the entrypoint/server level, mirroring HTTP access log behavior. - Enable TCP access logging via the global static configuration (accessLog), with no per-router or manual wiring required. - Ensure thread-safe log writes and support for both JSON and text log formats.
What does this PR do?
This PR Implements a TCP access log handler that logs connection start and end events, including client/server addresses, bytes in/out, duration, client certificate and errors.
Motivation
resolves #7800
More
Additional Notes
Early Pull Request draft --> I tested the feature on my end with some demo set-ups, but would appreciate some feedback if it goes in the right direction and if something should be changed to make a merge possible.