[jira] [Commented] (BEAM-12401) Beam metrics are unreadable in Flink history server

["David Janicek (Jira)" <ji...@apache.org>]

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

David Janicek commented on BEAM-12401:
--------------------------------------

Related to https://issues.apache.org/jira/browse/BEAM-10719

> Beam metrics are unreadable in Flink history server
> ---------------------------------------------------
>
>                 Key: BEAM-12401
>                 URL: https://issues.apache.org/jira/browse/BEAM-12401
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-flink
>            Reporter: David Janicek
>            Priority: P2
>
> Beam metric values (payload) are not readable in Flink's web UI and Flink history server. Similar problem affected Spark history server and it was resolved in BEAM-10294.
> Beam metrics are rendered by *MetricsContainerStepMap.toString()* method as JSON which is created from protobuffer defined in *metrics.proto* where metric's value is defined as bytes.
> For example, metrics in Flink web UI used to look like:
> {code:java}
> MetricQueryResults(Counters(sets-by-key-bloomfilter/filter-by-bloom-filter/ParMultiDo(FilterByBloomFilter):org.apache.beam.sdk.extensions.sketching.BloomFilters$FilterByBloomFilterFn:filtered-out: 123456789)){code}
> Now they look like:
> {code:java}
> {\n \"metrics\": {\n \"attempted\": [{\n \"urn\": \"beam:metric:user:sum_int64:v1\",\n \"type\": \"beam:metrics:sum_int64:v1\",\n \"payload\": \"ip0K\",\n \"labels\": {\n \"NAMESPACE\": \"ImageClicksReader\",\n \"NAME\": \"filtered-out\",\n \"PTRANSFORM\": \"sets-by-key-bloomfilter/filter-by-bloom-filter/ParMultiDo(FilterByBloomFilter\"\n }\n } \n} \n}{code}
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)