[
https://issues.apache.org/jira/browse/KYLIN-1908?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
kangkaisen updated KYLIN-1908:
------------------------------
Attachment: KYLIN-1908.patch
This patch add query metrics in the Server, Project, Cube three levels.
The finally ObjectNames are as shown below:
Hadoop:name=Server_Total,service=Kylin
Hadoop:name=learn_kylin,service=Kylin.QueryCount
Hadoop:name=learn_kylin,service=Kylin,sub=kylin_sales_cube.QueryCount
The first word of ObjectName "Hadoop" is hard coding in the
"org.apache.hadoop.metrics2",
I can't change it to "Kylin".
Each ObjectName has the following metrics:
QueryCount;
QueryFailCount;
QuerySuccessCount;
CacheHitCount, CacheHitCount60sNumOps, CacheHitCount300sNumOps,
CacheHitCount3600sNumOps;
QueryLatency,QueryLatencyNumOps,QueryLatencyAvgTime,QueryLatencyMaxTime,
QueryLatencyMinTime,QueryLatency60s99thPercentile,QueryLatency300s99thPercentile,
QueryLatency3600s90thPercentile;
ResultRowCount and ScanRowCount are like QueryLatency.
> Collect Metrics to JMX
> ----------------------
>
> Key: KYLIN-1908
> URL: https://issues.apache.org/jira/browse/KYLIN-1908
> Project: Kylin
> Issue Type: New Feature
> Components: Tools, Build and Test
> Affects Versions: v1.5.2
> Reporter: kangkaisen
> Assignee: kangkaisen
> Attachments: KYLIN-1908.patch, QueryMetrics.java
>
>
> As we all known, some performance metrics is important for enterprise
> applications. so we should support to collect metrics to JMX in Kylin.
> The method I have done is As shown below:
> 1. use `org.apache.hadoop.metrics2` as the metrics collection framework.
> 2. define MBean Class for the metrics that we need to collect.
> 3. update metrics in right place.
> The questions I have:
> 1. can I depend on `org.apache.hadoop.metrics2` directly?
> 2. how do you think about my method?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
