Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Provide the delayed message publish rate stats

See original GitHub issue

Is your enhancement request related to a problem? Please describe. Currently, the producer stats contains the following information

{
    "accessMode" : "Shared",
    "msgRateIn" : 0.016669007231704083,
    "msgThroughputIn" : 11.384931939253889,
    "averageMsgSize" : 683.0,
    "chunkedMessageRate" : 0.0,
    "producerId" : 2,
    "metadata" : { },
    "address" : "/xxxx",
    "connectedSince" : "2022-03-07T14:32:57.52849Z",
    "producerName" : "xxx"
  }

From the stats, we are not able to know whether the problem is sending delayed messages or not, it will be useful for some cases to troubleshoot problems.

Describe the solution you’d like Add “delayedMsgRateIn” in the producer stats

Issue Analytics

State:
Created 2 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

shibdcommented, Mar 7, 2022

@codelipenghui I want to try it.

0reactions

Technoboy-commented, Mar 10, 2022

@codelipenghui The delays is placed in the MessageMetadata. This feature will make the broker additional a deserialization MessageMetaData when receiving the producer message. Can we accept the performance impact?

Or, We need add new field hasDeliver to CommandSend, This can avoid deserialization the data of MessageMetadata. This is an API protocol change, We need to discuss first. @codelipenghui @Technoboy- PTAL

I will help to check first and then decide to send out a discussion email.

Yes, you’re right. If add this field in the CommandSend, it is duplicated with MsgMetadata, and deserialization is much heavier, so after discussion, we decide to close this issue now.