Story #2324
Updated by bmbouter almost 8 years ago
h3. Problem It can be challenging for a user to analyze Pulp logs. A user should be able determine what task produced a specific log statement. Potential ways to answer these questions: make this easier include: 1. What task did this * make sure the PID is included in each log statement come from? 2. What are all * include the log statements emitted by a specific task? h3. Solution To remedy this we will add the first 8 characters of the task ID within brackets to each in all log line emitted statements from within a running task. Note that celery logs the entire task id before the task is run, so even with us logging a limited portion of the task-id you can easily determine the entire task-id. Taking an example from Comment 3, the contents of the log line would be: <code>[0ca4399c] Starting new HTTPS connection (1): </code> tasks
.