You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2020/03/23 11:57:00 UTC
[jira] [Updated] (HDDS-3239) Provide message-level metrics from the
generic protocol dispatch
[ https://issues.apache.org/jira/browse/HDDS-3239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated HDDS-3239:
---------------------------------
Labels: pull-request-available (was: )
> Provide message-level metrics from the generic protocol dispatch
> -----------------------------------------------------------------
>
> Key: HDDS-3239
> URL: https://issues.apache.org/jira/browse/HDDS-3239
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
> Reporter: Marton Elek
> Assignee: Marton Elek
> Priority: Major
> Labels: pull-request-available
>
> Ozone RPC protocols (due to the limitation of protobuf) are very simple: There is only one message per service and the message is routed to the appropriate method based on the type.
> It makes very easy to add tracing / metrics as we have one generic dispatcher (OzoneProtocolMessageDispatcher.java) where we implemented opentracing support and basic metric collection.
> In this patch I propose to improve this metric to add the message type to the metrics as a tag to make it easier to follow what's going on... (eg. see the distribution of the incoming message types)
> We can also measure the total amount of time spent to serve one specific type of requests which can be used to calculate the moving average for latency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org