[
https://issues.apache.org/jira/browse/FLINK-23976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17418765#comment-17418765
]
Seth Wiesman commented on FLINK-23976:
--------------------------------------
[~thw] interesting. Similar to the linked ticket we'll need to think about how
this fits into application mode, in particular jobs that multiple job graphs
and which are potentially chained.
> Add additional availability timing metrics to Job lifecycle events
> ------------------------------------------------------------------
>
> Key: FLINK-23976
> URL: https://issues.apache.org/jira/browse/FLINK-23976
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics
> Reporter: Seth Wiesman
> Priority: Major
> Labels: pull-request-available
>
> Flink currently contains a number of availability lifecycle metrics[1]
> showing how long it takes to move through different job status'. We propose
> adding two additional metrics; startingTime, and cancellingTime (open to
> bikeshedding on the metric names).
>
> * startingTime is the time it takes a job to get to running.
> * cancellingTime is the time spent in status CANCELLING
>
>
> [1]https://ci.apache.org/projects/flink/flink-docs-master/docs/ops/metrics/#availability
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
