[
https://issues.apache.org/jira/browse/FLINK-6464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16337608#comment-16337608
]
ASF GitHub Bot commented on FLINK-6464:
---------------------------------------
Github user zentol commented on the issue:
https://github.com/apache/flink/pull/5332
@aljoscha Done, we now include the function name instead. Is a bit more
complicated that I had hoped though...
> Metric name is not stable
> -------------------------
>
> Key: FLINK-6464
> URL: https://issues.apache.org/jira/browse/FLINK-6464
> Project: Flink
> Issue Type: Bug
> Components: DataStream API, Metrics
> Affects Versions: 1.2.0
> Reporter: Andrey
> Assignee: Chesnay Schepler
> Priority: Critical
> Fix For: 1.5.0, 1.4.1
>
>
> Currently according to the documentation
> (https://ci.apache.org/projects/flink/flink-docs-release-1.2/monitoring/metrics.html)
> operator metrics constructed using the following pattern:
> <operator_name>, <subtask_index>
> For some operators, "operator_name" could contain default implementation of
> toString method. For example:
> {code}
> TriggerWindow(TumblingProcessingTimeWindows(3000),
> ListStateDescriptor{serializer=org.apache.flink.api.java.typeutils.runtime.kryo.KryoSerializer@c65792d4},
> xxx.Trigger@665fe457, WindowedStream.apply(WindowedStream.java:521)) ->
> Sink: Unnamed
> {code}
> The part "@c65792d4" will be changed every time job is restarted/cancelled.
> As a consequence it's not possible to store metrics for a long time.
> Expected:
> * ensure all operators return human readable, non-default names OR
> * change the way TriggerWindow generates it's name.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
