[ https://issues.apache.org/jira/browse/FLINK-10452?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17328549#comment-17328549 ]
Flink Jira Bot commented on FLINK-10452: ---------------------------------------- This major issue is unassigned and itself and all of its Sub-Tasks have not been updated for 30 days. So, it has been labeled "stale-major". If this ticket is indeed "major", please either assign yourself or give an update. Afterwards, please remove the label. In 7 days the issue will be deprioritized. > Expose Additional Metrics to Reason about Statesize > --------------------------------------------------- > > Key: FLINK-10452 > URL: https://issues.apache.org/jira/browse/FLINK-10452 > Project: Flink > Issue Type: Improvement > Components: Runtime / Metrics, Runtime / State Backends > Reporter: Konstantin Knauf > Priority: Major > Labels: stale-major > > For monitoring purposes it would be helpful, if Flink could expose metrics > about the number of keys/windows for each registered keyed state. > Open Questions: > * One Metric per Registered State? One Metric per KeyedOperator? > * Performance Impact (should this be default behavior?) > * Possible to know the number of windows during runtime? > * RocksDB only gives you an estimate of the number keys. Would be nice if we > could derive the exact number inside Flink. This would also help in sizing > the RocksDB instances and estimated their memory footprint. -- This message was sent by Atlassian Jira (v8.3.4#803005)