[
https://issues.apache.org/jira/browse/FLINK-23519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419576#comment-17419576
]
Yun Tang commented on FLINK-23519:
----------------------------------
merged in
master( 1.15.0) : e2bda3df78b0a7d16acf81611d3768e12309a1b4
release-1.13: adfbbcbe03783ce3cbe9fff4aaa2bca9ab7f2be7
> Aggregate State Backend Latency by State Level
> ----------------------------------------------
>
> Key: FLINK-23519
> URL: https://issues.apache.org/jira/browse/FLINK-23519
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Metrics, Runtime / State Backends
> Affects Versions: 1.13.0
> Reporter: Mason Chen
> Assignee: Yun Tang
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.13.3, 1.15.0, 1.14.1
>
>
> To make metrics aggregation easier, there should be a config to expose
> something like `state.backend.rocksdb.metrics.column-family-as-variable` that
> rocksdb provides to do aggregation across column families
> ([https://ci.apache.org/projects/flink/flink-docs-release-1.13/docs/deployment/config/#state-backend-rocksdb-metrics-column-family-as-variable]).
>
> In this case of state backend latency, the variable exposed would be state
> level instead column family. This makes it easier to aggregate by the various
> state levels that are reported.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
