Skip to content
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.

Sign up for GitHub

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

Jump to bottom

WSGI Access Logging #26

Open
gierens opened this issue Feb 2, 2022 · 0 comments
Open

WSGI Access Logging #26

gierens opened this issue Feb 2, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@gierens
Copy link
Owner

gierens commented Feb 2, 2022 •
edited
Loading

The production WSGI server waitress does not log web traffic by default. One needs to use the TransLogger middleware for that. See https://buildmedia.readthedocs.org/media/pdf/waitress/latest/waitress.pdf . This would be a nice feature and should be integrated with the general log level and the verbosity argument.
@gierens gierens added this to the Release milestone Feb 2, 2022
@gierens gierens added the enhancement New feature or request label Feb 2, 2022
@gierens gierens removed this from the Release milestone Feb 2, 2022
@gierens gierens mentioned this issue Feb 3, 2022
Merged
gierens added a commit that referenced this issue Feb 3, 2022
@gierens
Merge branch 'feature-8-logging'
7d79d8c 
Integrated basic logging functionality including `-v/--verbosew with
multiplicity for setting the desired verbosity. Also configured the
waitress log level. So this resolves #8.

Access logging like Flask's WSGI server does it however requires an a
little more elaborated approach, so we do this later on, see #26.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gierens