[
https://issues.apache.org/jira/browse/HDDS-17169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-17169:
----------------------------------
Labels: pull-request-available (was: )
> Add OM and datanode client call latency metrics in S3 Gateway
> -------------------------------------------------------------
>
> Key: HDDS-17169
> URL: https://issues.apache.org/jira/browse/HDDS-17169
> Project: Apache Ozone
> Issue Type: Improvement
> Components: metrics, s3gateway
> Reporter: Siyao Meng
> Assignee: Huang Kuan Hao
> Priority: Major
> Labels: pull-request-available
>
> S3GatewayMetrics reports latency per S3 API, and XceiverClientMetrics counts
> datanode operations, but S3 Gateway has no latency metrics for the calls it
> makes to OM and datanodes. When an S3 request is slow it is hard to tell
> which backend is responsible.
> Add latency metrics in S3 Gateway, broken down per OM API (e.g. lookupKey,
> listKeys, commitKey) and per datanode operation (e.g. WriteChunk, PutBlock,
> ReadChunk).
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
