As a user, I can configure access-like entries to be logged separately
Currently, pulpcore writes access log entries to /var/log/messages, like:
May 18 08:44:37 pmoravec-sat69-pulp3 pulpcore-api: pulp [-]: - - [18/May/2021:06:44:37 +0000] "GET /pulp/api/v3/tasks/5782d0e8-8814-4638-af71-5116328b8589/ HTTP/1.1" 200 1170 "-" "OpenAPI-Generator/3.7.1/ruby" May 17 20:33:06 pmoravec-sat69-pulp3 pulpcore-api: pulp [-]: - - [17/May/2021:18:33:06 +0000] "GET /pulp/api/v3/content/rpm/distribution_trees/?repository_version=%2Fpulp%2Fapi%2Fv3%2Frepositories%2Frpm%2Frpm%2F7b561af0-d36b-4147-851e-f428f3c78222%2Fversions%2F0%2F HTTP/1.1" 200 52 "-" "OpenAPI-Generator/3.10.0/ruby" May 17 23:01:55 pmoravec-sat69-pulp3 pulpcore-api: pulp [-]: - - [17/May/2021:21:01:55 +0000] "GET /pulp/api/v3/status HTTP/1.1" 301 0 "-" "rest-client/2.0.2 (linux-gnu x86_64) ruby/2.5.5p157"
/var/log/messages is quite spammed by those log entries, that should be categorized as (and logged to) a dedicated httpd/pulpcore access log.
Actual results: pulpcore-api logs the access logs to /var/log/messages
Expected results: the access logs should be logged either in /var/log/httpd/pulp_access.log or a similar file, or in a dedicated /var/log/pulp* log.
Additional info: The categorization of log entries can be subjective and/or there can be rationale to log them to /var/log/messages . So take this rather as a suggestion than as a bug.
Please register to edit this issue