You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/05/11 11:43:01 UTC

[jira] [Commented] (FLINK-22631) Metrics are incorrect when task finished

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

Konstantin Knauf commented on FLINK-22631:
------------------------------------------

I changed this to "Improvement" as this is the expected behavior. I think, one could also arque that this behavior is ok. Metrics don't need to be 100% accurate for most use cases, specifically monitoring. Prometheus is actually a good example for this philosophy.

> Prometheus values reliability. You can always view what statistics are available about your system, even under failure conditions. If you need 100% accuracy, such as for per-request billing, Prometheus is not a good choice as the collected data will likely not be detailed and complete enough. In such a case you would be best off using some other system to collect and analyze the data for billing, and Prometheus for the rest of your monitoring.
(https://prometheus.io/docs/introduction/overview/#when-does-it-not-fit)

What is your use case? What do you measure in that particular case?


> Metrics are incorrect when task finished
> ----------------------------------------
>
>                 Key: FLINK-22631
>                 URL: https://issues.apache.org/jira/browse/FLINK-22631
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Metrics
>            Reporter: Li
>            Priority: Major
>
>         MetricReporters are reported periodically, default 10 seconds. The final metrics may not be reported to metric system like pushgateway when task finished. This makes users unable to obtain the correct metrics。
> 	
>         Maybe metricReporters should be reported once manually before closed.



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