[
https://issues.apache.org/jira/browse/FLINK-35065?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated FLINK-35065:
-----------------------------------
Labels: pull-request-available (was: )
> Add numFiredTimers and numFiredTimersPerSecond metrics
> ------------------------------------------------------
>
> Key: FLINK-35065
> URL: https://issues.apache.org/jira/browse/FLINK-35065
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics, Runtime / Task
> Affects Versions: 1.19.0
> Reporter: Piotr Nowojski
> Assignee: Piotr Nowojski
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.20.0
>
>
> Currently there is now way of knowing how many timers are being fired by
> Flink, so it's impossible to distinguish, even using code profiling, if
> operator is firing only a couple of heavy timers per second using ~100% of
> the CPU time, vs firing thousands of timer per seconds.
> We could add the following metrics to address this issue:
> * numFiredTimers - total number of fired timers per operator
> * numFiredTimersPerSecond - per second rate of firing timers per operator
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
