[
https://issues.apache.org/jira/browse/HDDS-7394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christos Bisias updated HDDS-7394:
----------------------------------
Description:
On the Prometheus endpoint for the OM, in the DecayRpcScheduler summary for
users, the username is exposed in the metric name, instead of in a label.
In the below example, the username(hadoop) is between caller and metric
type(volume or priority):
{code:java}
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21 {code}
It makes almost impossible to monitor these values as every time a new user
shows up we need to register a new metrics name.
The OM jmx endpoint registers the metrics name as expected.
was:
On the Prometheus endpoint for the OM, in the DecayRpcScheduler summary for
users, the username is exposed in the metric name, instead of in a label.
In the below example, the username(hadoop) is between caller and metric type
which is either volume or priority:
{code:java}
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21
# TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume counter
org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
21 {code}
It makes almost impossible to monitor these values as every time a new user
shows up we need to register a new metrics name.
The OM jmx endpoint registers the metrics name as expected.
> OM RPC FairCallQueue decay decision metrics list caller username in the
> metric instead of a label
> -------------------------------------------------------------------------------------------------
>
> Key: HDDS-7394
> URL: https://issues.apache.org/jira/browse/HDDS-7394
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Christos Bisias
> Assignee: Christos Bisias
> Priority: Major
>
> On the Prometheus endpoint for the OM, in the DecayRpcScheduler summary for
> users, the username is exposed in the metric name, instead of in a label.
> In the below example, the username(hadoop) is between caller and metric
> type(volume or priority):
> {code:java}
> # TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume counter
> org_apache_hadoop_ipc_decay_rpc_scheduler_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
> 21
> # TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume counter
> org_apache_hadoop_ipc_decay_rpc_scheduler_caller_hadoop_volume{context="ipc.9862",hostname="1ad339cc5aba"}
> 21
> # TYPE org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume counter
> org_apache_hadoop_ipc_decay_rpc_scheduler_decayed_call_volume{context="ipc.9862",hostname="1ad339cc5aba"}
> 21 {code}
> It makes almost impossible to monitor these values as every time a new user
> shows up we need to register a new metrics name.
> The OM jmx endpoint registers the metrics name as expected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
