It is recommended that Internet Protocol (IP) addresses involved in an event are included in the logging contents. Currently, the log contents consist of timestamps, user identifiers, and actions/events.
For security logging assistance, reverence Security Log Collection, Analysis and Retention(DS-19) and/or contact irteam-recon@umichl.edu. REF: Security Log Collection, Analysis, and Retention (DS-19) - U-M General Policies DS-19
Describe the solution you'd like
We are not logging anything from Gunicorn. We'd probably need to create an issue and research how we'd capture request logs with correct IP addresses.
Describe any possible alternatives you've considered
pushyamig
commented
2 months ago
Thank you for contributing to this project!
Describe your problem or feature you'd like added
It is recommended that Internet Protocol (IP) addresses involved in an event are included in the logging contents. Currently, the log contents consist of timestamps, user identifiers, and actions/events.
For security logging assistance, reverence Security Log Collection, Analysis and Retention(DS-19) and/or contact irteam-recon@umichl.edu. REF: Security Log Collection, Analysis, and Retention (DS-19) - U-M General Policies DS-19
Describe the solution you'd like
We are not logging anything from Gunicorn. We'd probably need to create an issue and research how we'd capture request logs with correct IP addresses.
Describe any possible alternatives you've considered
ROHQ does logging but doesn't capture IP addresses, there's a issue out to fix that we haven't implemented. https://github.com/tl-its-umich-edu/remote-office-hours-queue/issues/359