Skip to content

Add cs-bytes and sc-bytes to the W3CLogger #35614

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
ajkonkol opened this issue Aug 23, 2021 · 3 comments
Open

Add cs-bytes and sc-bytes to the W3CLogger #35614

ajkonkol opened this issue Aug 23, 2021 · 3 comments
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions feature-http-logging
Milestone

Comments

@ajkonkol
Copy link

Is your feature request related to a problem? Please describe.

As our company migrates from mainly Windows/IIS/Full Framework to more and more Linux/Kestrel/.NET 6, we'd like to continue feeding our web server access (W3C) logs into our Elastic stack. Our current IIS logs include fields that indicate the size of each request and response (in bytes) in fields named cs-bytes (client-to-server) and sc-bytes (server-to-client). We noticed that the new W3CLogger doesn't include these fields, which can be very handy when troubleshooting issues and monitoring system health.

Describe the solution you'd like

We'd like to see cs-bytes and sc-bytes be new fields added to the W3CLogger. This would include seeing these fields on the Microsoft.AspNetCore.HttpLogging.W3CLoggingFields enum.

Additional context

Add any other context or screenshots about the feature request here.

@wtgodbe wtgodbe added this to the .NET 7-Candidate milestone Aug 24, 2021
@wtgodbe wtgodbe self-assigned this Aug 24, 2021
@wtgodbe
Copy link
Member

wtgodbe commented Aug 24, 2021

Good suggestion, we will consider adding these for .Net 7. Unfortunately it is too late to add new API to .Net 6 at this point.

@ghost
Copy link

ghost commented Sep 9, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@wtgodbe wtgodbe removed their assignment Nov 28, 2022
@amcasey amcasey added area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Aug 24, 2023
@amcasey amcasey modified the milestones: .NET 8 Planning, Backlog Feb 14, 2024
@MarcelVersteeg
Copy link

I would like to have these fields in the logfiles generated by the W3CLogger too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions feature-http-logging
Projects
None yet
Development

No branches or pull requests

6 participants