[jira] [Resolved] (KYLIN-2776) Using dropwizard as default metric framework

["Billy Liu (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/KYLIN-2776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Billy Liu resolved KYLIN-2776.
------------------------------
       Resolution: Fixed
    Fix Version/s: v2.3.0

Commit：https://git1-us-west.apache.org/repos/asf?p=kylin.git;a=commit;h=b778f33a

> Using dropwizard as default metric framework
> --------------------------------------------
>
>                 Key: KYLIN-2776
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2776
>             Project: Kylin
>          Issue Type: New Feature
>    Affects Versions: v2.0.0
>            Reporter: yiming.xu
>            Assignee: yiming.xu
>            Priority: Major
>             Fix For: v2.3.0
>
>         Attachments: KYLIN-2776.patch, active_calls.png, calls.png, metric_structure.png, query_count.png, query_duration.png, query_result_rowcount.png, report.json
>
>
> With https://issues.apache.org/jira/browse/KYLIN-2721.We are plan to release a new metric framework. 
> New metric is different hadoop metric  and based on dropwizard . which has the following advantage:
> *     Well-defined metric model for frequently-needed metrics (ie JVM metrics)
> *     Well-defined measurements for all metrics (ie max, mean, stddev, mean_rate, etc),
> *     Built-in pluggable reporting frameworks like JMX, Console, Log, JSON 
> We refactored QueryMetric with new metrics, notice the exposed JMX MBeans have changed a little bit.
> A new tool called perflog is also introduced. Perflog traces call duration time  and current active calls by recording them to metric system.
>  Some snapshots of the new JMX MBeans can be seen in attachments



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)