[
https://issues.apache.org/jira/browse/FLINK-23976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-23976:
-----------------------------------
Labels: pull-request-available stale-major (was: pull-request-available)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 60 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> 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, stale-major
>
> 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.20.1#820001)
