[
https://issues.apache.org/jira/browse/INLONG-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated INLONG-587:
----------------------------------
Labels: pull-request-available (was: )
> Add client-side metrics statistics
> ----------------------------------
>
> Key: INLONG-587
> URL: https://issues.apache.org/jira/browse/INLONG-587
> Project: Apache InLong
> Issue Type: Improvement
> Components: inlong-tubemq
> Reporter: Guocheng Zhang
> Priority: Normal
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
>
> At present, our SDK adopts the implementation of trust mode. If the SDK users
> want to know its own production and consumption metrics, the users need to do
> additional development, and this function can be embedded into the SDK fully,
> as a standard function Externally provided.
> In addition, there will be some overhead when performing production and
> consumption statistics, so it is best to make this function a configurable
> mode, so that services can be turned on or off.
> Through this metric statistics, SDK users can obtain the metrics since the
> last statistical view, and the production-side SDK can obtain metrics since
> the last statistical query, such as the number of request timeouts in
> production, the number of request overflows, the number of messages, and the
> total packet size sent, the maximum packet length, the minimum packet length,
> the maximum delay, the minimum delay; the consumer can obtain the number of
> request timeouts, the number of request failures, the number of partitions
> consumed, the number of consumed packets per partition, and the total data
> size, consumption maximum delay, minimum delay, etc.
> Issue evaluation:
> The difficulty of this part should be medium, but it is very complicated. It
> needs enough patience and practical experience to get the data output
> approved by the users.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
