You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "Ethan Rose (Jira)" <ji...@apache.org> on 2026/08/20 17:17:00 UTC

[jira] [Created] (HDDS-16238) Latency metrics for internal OM requests are not populated

Ethan Rose created HDDS-16238:
---------------------------------

             Summary: Latency metrics for internal OM requests are not populated
                 Key: HDDS-16238
                 URL: https://issues.apache.org/jira/browse/HDDS-16238
             Project: Apache Ozone
          Issue Type: Bug
            Reporter: Ethan Rose
            Assignee: Ethan Rose


The OM's {{ProtocolMessageMetrics}} is only used in the server side translator. This captures end-to-end latency for all client facing requests (like {{RenameKey}}), but not for internal OM requests submitted directly to Ratis by background services (like {{PurgeKeys}}). This causes latency metrics for internal requests to always be 0.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org