You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Zhong Yanghong (JIRA)" <ji...@apache.org> on 2017/08/22 10:42:00 UTC

[jira] [Commented] (KYLIN-2725) Introduce a tool for creating system cubes relating to query & job metrics

    [ https://issues.apache.org/jira/browse/KYLIN-2725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16136621#comment-16136621 ] 

Zhong Yanghong commented on KYLIN-2725:
---------------------------------------

Related commit for branch yaho-cube-planner is as follows:
https://github.com/apache/kylin/commit/74e167f090bed8537858cb44e4266f0427a0d3c7

> Introduce a tool for creating system cubes relating to query & job metrics
> --------------------------------------------------------------------------
>
>                 Key: KYLIN-2725
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2725
>             Project: Kylin
>          Issue Type: Sub-task
>    Affects Versions: v2.2.0
>            Reporter: Zhong Yanghong
>            Assignee: Zhong Yanghong
>
> System cubes are the basis of dashboard & cube planner. Dashboard & cube planner can query on system cubes to fetch required data. Currently, we design five system cubes. The details are as follows:
> * *METRICS_QUERY*
> ** Dimension
>     USER, HOST, PROJECT, REALIZATION, REALIZATION_TYPE, QUERY_TYPE, EXCEPTION, *TIME_DIMENSIONS*
> ** Measure
>     COUNT, 
>     MIN & MAX & SUM & PERCENTILE of QUERY_TIME_COST,
>     MAX & SUM of CALCITE_COUNT_RETURN,
>     MAX & SUM of STORAGE_COUNT_RETURN,
>     MAX & SUM of CALCITE_COUNT_AGGREGATE_FILTER,
>     COUNT_DISTINCT(hll) of QUERY_HASH_CODE
> * *METRICS_QUERY_CUBE*
> ** Dimension
>     CUBE_NAME, SEGMENT_NAME, CUBOID_SOURCE, CUBOID_TARGET, IF_MATCH, IF_SUCCESS, *TIME_DIMENSIONS*
> ** Measure
>     COUNT,
>     SUM of WEIGHT_PER_HIT,
>     MAX & SUM of STORAGE_CALL_COUNT,
>     MAX & SUM of STORAGE_CALL_TIME_SUM,
>     MAX & SUM of STORAGE_CALL_TIME_MAX,
>     MAX & SUM of STORAGE_COUNT_SKIP,
>     MAX & SUM of STORAGE_COUNT_SCAN,
>     MAX & SUM of STORAGE_COUNT_RETURN,
>     MAX & SUM of STORAGE_COUNT_AGGREGATE_FILTER
>     MAX & SUM of STORAGE_COUNT_AGGREGATE
> * *METRICS_QUERY_RPC*
> ** Dimension
>     HOST, PROJECT, REALIZATION, RPC_SERVER, EXCEPTION, *TIME_DIMENSIONS*
> ** Measure
>     COUNT,
>     MAX & SUM & PERCENTILE of CALL_TIME,
>     MAX & SUM of COUNT_RETURN,
>     MAX & SUM of COUNT_SCAN,
>     MAX & SUM of COUNT_SKIP,
>     MAX & SUM of COUNT_AGGREGATE_FILTER,
>     MAX & SUM of COUNT_AGGREGATE
> * *METRICS_JOB*
> ** Dimension
>     USER, PROJECT, CUBE_NAME, JOB_TYPE, CUBING_TYPE, *TIME_DIMENSIONS*
> ** Measure
>     COUNT, 
>     MIN & MAX & SUM & PERCENTILE of DURATION,
>     MIN & MAX & SUM of TABLE_SIZE,
>     MIN & MAX & SUM of CUBE_SIZE,
>     MIN & MAX & SUM of PER_BYTES_TIME_COST,
>     MIN & MAX & SUM of WAIT_RESOURCE_TIME,
>     MAX & SUM of STEP_DURATION_DISTINCT_COLUMNS,
>     MAX & SUM of STEP_DURATION_DICTIONARY,
>     MAX & SUM of STEP_DURATION_INMEM_CUBING,
>     MAX & SUM of STEP_DURATION_HFILE_CONVERT
> * *METRICS_JOB_EXCEPTION*
> ** Dimension
>     USER, PROJECT, CUBE_NAME, JOB_TYPE, CUBING_TYPE, EXCEPTION, *TIME_DIMENSIONS*
> ** Measure
>     COUNT
> * *TIME_DIMENSIONS*
>     KYEAR_BEGIN_DATE, KMONTH_BEGIN_DATE, KWEEK_BEGIN_DATE, KDAY_DATE, KTIME_HOUR, KTIME_MINUTE



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)