flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-7781) Support simple on-demand metrics aggregation
Date Tue, 31 Oct 2017 12:39:01 GMT

    [ https://issues.apache.org/jira/browse/FLINK-7781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16226709#comment-16226709

ASF GitHub Bot commented on FLINK-7781:

Github user asfgit closed the pull request at:


> Support simple on-demand metrics aggregation
> --------------------------------------------
>                 Key: FLINK-7781
>                 URL: https://issues.apache.org/jira/browse/FLINK-7781
>             Project: Flink
>          Issue Type: Improvement
>          Components: Metrics, REST
>    Affects Versions: 1.4.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>             Fix For: 1.4.0
> We should support aggregations (min, max, avg, sum) of metrics in the REST API. This
is primarily about aggregating across subtasks, for example the number of incoming records
across all subtasks.
> This is useful for simple use-cases where a dedicated metrics backend is overkill, and
will allow us to provide better metrics in the web UI (since we can expose these aggregated
as well).
> I propose to add a new query parameter "agg=[min,max,avg,sum]". As a start this parameter
should only be used for task metrics. (This is simply the main use-case i have in mind)
> The aggregation should (naturally) only work for numeric metrics.
> We will need a HashSet of metrics that exist for subtasks of a given tasks that has to
be updated in {{MetricStore#add}}.
> All task metrics are either stored as
> # {{<subtask-index>.<metric>}} or
> # {{<subtask-index>.<operator-name>.<metric>}}.
> If a user sends a request {{get=mymetric,agg=sum}}, only the metrics of the first kind
are to be considered. Similarly, given a request {{get=myoperator.mymetric,agg=sum}} only
metrics of the second kind are to be considered.
> Ideally, the name of the aggregated metric (i.e. the original name without subtask index)
is also contained in the list of available metrics.

This message was sent by Atlassian JIRA

View raw message