Add RPC incoming and reply log
Bug #2072156 reported by
LIU Yulong
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
oslo.messaging |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
We had this log [1] before, but the commit [2] 859e0d4eaa45d75
So add the log back with the attribute msg_id for base IncomingMessage class.
[1] https:/
[2] https:/
Changed in oslo.messaging: | |
status: | New → In Progress |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/c/openstack /oslo.messaging /+/923337 /opendev. org/openstack/ oslo.messaging/ commit/ 104a63b9aa040dd a567d356e598aad 5f8734d3ec
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 104a63b9aa040dd a567d356e598aad 5f8734d3ec
Author: LIU Yulong <email address hidden>
Date: Fri Oct 11 23:22:23 2019 +0800
Add RPC incoming and reply log
Typically a simple log will not narrow down the performance, but give
us more information about the service status.
The commit 859e0d4eaa45d75 eb822f4a6be46c5 47187c6358 directly revert
the log due to the msg_id is not accessable for non-rabbit drivers.
It's not the right way to make things better.
So add the log back with the attribute msg_id for base IncomingMessage
class.
Closes-Bug: #2072156
Related-Bug: #1847747
Related-Bug: #1855775
Change-Id: Ib35c8fbb24d5c5 1d3b54e8ca63e66 3428318eca5