Project

Profile

Help

Actions
Send by e-mail Copy link

Issue #8393

closed

correlation id messages pollute log files

Added by jsherril@redhat.com about 3 years ago. Updated about 3 years ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

By default when running pulpcore 3.9 or later, if you do not specify a correlation id in a request you will see in the log:

django_guid:INFO: Header Correlation-ID was not found in the incoming request. Generated new GUID: 2e1c2346c146466f8c990819c9d4d6d7

If you do specify one, its also logged:

django_guid:INFO: Correlation-ID found in the header: 1c64238b-3706-418d-b67a-55a05dc46ed1

I would argue that neither of these should be logged.

Related issues

Is duplicate of Pulp - Issue #7982: "`Correlation-ID` was not found in the incoming request. Generated new GUID" log messages are spammyCLOSED - CURRENTRELEASEdalleyActions
Actions
Copy link
 #1

Updated by dalley about 3 years ago

  • Status changed from NEW to CLOSED - DUPLICATE
Actions
Copy link
 #2

Updated by dalley about 3 years ago

  • Is duplicate of Issue #7982: "`Correlation-ID` was not found in the incoming request. Generated new GUID" log messages are spammy added
Actions
Send by e-mail Copy link

Also available in: Atom PDF