Actions
Story #4723
closed
As a user, I can view access logs for pulp-content-app
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Sprint 52
Quarter:
Description
pulp-content-app needs to configured to write access logs to stdout.
Updated by dkliban@redhat.com about 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to dkliban@redhat.com
- Sprint set to Sprint 52
Added by dkliban@redhat.com about 5 years ago
Added by dkliban@redhat.com about 5 years ago
Revision b47f8639 | View on GitHub
Problem: pulp-content-app does not produce access logs
Solution: configure gunicorn to write access logs to stdout
Updated by dkliban@redhat.com about 5 years ago
- Status changed from ASSIGNED to POST
Updated by dkliban@redhat.com about 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset ansible-pulp3|b47f8639b096362b5e50a500be9de4fb52119131.
Added by bmbouter about 5 years ago
Revision ec4b8d2a | View on GitHub
Access logs now work
A change to ansible-pulp has pulp-content emitting access logs correctly now.
Updated by bmbouter about 5 years ago
- Status changed from POST to MODIFIED
Applied in changeset pulplift|ec4b8d2a14a10a24a8494fe898f5d11d3904bcb6.
Updated by bmbouter over 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Problem: pulp-content-app does not produce access logs
Solution: configure gunicorn to write access logs to stdout
fixes: #4723 https://pulp.plan.io/issues/4723