You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
All platform
RocketMQ version
RocketMQ 5.x
JDK Version
All JDK versions
Describe the Bug
The current statistical method for the GROUP_GET_LATENCY metric fails to reveal its intended semantics
The current statistics are analyzing the time to parse messages, rather than the time to retrieve messages from message store.
Steps to Reproduce
Reference code
What Did You Expect to See?
The current statistical method for the GROUP_GET_LATENCY metric can reveal its intended semantics
What Did You See Instead?
The current statistical method for the GROUP_GET_LATENCY metric can reveal its intended semantics
Additional Context
No response
The text was updated successfully, but these errors were encountered:
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
All platform
RocketMQ version
RocketMQ 5.x
JDK Version
All JDK versions
Describe the Bug
The current statistical method for the GROUP_GET_LATENCY metric fails to reveal its intended semantics
![image](https://private-user-images.githubusercontent.com/21963954/288645676-fadbe60e-4038-45ab-a201-d18a07fbcbc4.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk0Nzg1NzgsIm5iZiI6MTczOTQ3ODI3OCwicGF0aCI6Ii8yMTk2Mzk1NC8yODg2NDU2NzYtZmFkYmU2MGUtNDAzOC00NWFiLWEyMDEtZDE4YTA3ZmJjYmM0LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTMlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEzVDIwMjQzOFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWY5ODE3YzBhNzc2YTViNzk3NjJkODYzNTcxMmM5MWVhNGJiMGE2NmM3N2U1NzVlYjI4ZmQwYzdmZWJlNDI0ZGEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.yIhx8MRoJnFovSfxFOfP4b-9VX5P-AEevj2Pxo3aSwg)
The current statistics are analyzing the time to parse messages, rather than the time to retrieve messages from message store.
Steps to Reproduce
Reference code
What Did You Expect to See?
The current statistical method for the GROUP_GET_LATENCY metric can reveal its intended semantics
What Did You See Instead?
The current statistical method for the GROUP_GET_LATENCY metric can reveal its intended semantics
Additional Context
No response
The text was updated successfully, but these errors were encountered: