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-6051) Wrong metric scope names in documentation
Date Tue, 14 Mar 2017 17:11:41 GMT

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

ASF GitHub Bot commented on FLINK-6051:
---------------------------------------

GitHub user hadronzoo opened a pull request:

    https://github.com/apache/flink/pull/3538

    FLINK-6051: Correct metrics scope names

    Closes FLINK-6051.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/orgsync/flink FLINK-6051

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/flink/pull/3538.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #3538
    
----
commit ab4332801428e14b8077a2a7669a51f8a1607ca3
Author: Joshua Griffith <jgriffith@campuslabs.com>
Date:   2017-03-14T17:10:12Z

    Correct metrics scope names
    
    Closes FLINK-6051.

----


> Wrong metric scope names in documentation
> -----------------------------------------
>
>                 Key: FLINK-6051
>                 URL: https://issues.apache.org/jira/browse/FLINK-6051
>             Project: Flink
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: 1.2.0
>            Reporter: Joshua Griffith
>            Priority: Minor
>
> FLINK-4402 fixed the following metrics names:
> metrics.scope.tm.task → metrics.scope.task
> metrics.scope.tm.operator → metrics.scope.operator
> However, the [1.2.0 documentation|https://github.com/apache/flink/blob/dabeb74c10e755c655a06cdc8846dc7227d63cb9/docs/setup/config.md#metrics]
lists the incorrect metric names again.
> As a side note, it would be convenient to have all of the configuration options documented
in a machine readable format. To build docker images I [process the config file with sed|https://github.com/orgsync/docker-flink/blob/a08ec4d102b623bfba74a61d3012931e28ef92e7/Dockerfile#L36]
to extract the options and turn them into env vars, which is how I noticed this issue.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message