platinumhamburg opened a new issue, #2391: URL: https://github.com/apache/fluss/issues/2391
### Search before asking - [x] I searched in the [issues](https://github.com/apache/fluss/issues) and found nothing similar. ### Motivation Currently, Fluss only provides a total RocksDB memory usage metric (`rocksdbMemoryUsageTotal`) at the server level. This makes it difficult to diagnose memory issues or optimize RocksDB configuration. Users need visibility into individual memory components to: - Identify memory bottlenecks (e.g., memtable vs block cache) - Tune RocksDB configuration parameters appropriately - Monitor write pressure through memtable metrics - Track read cache effectiveness through block cache metrics ### Solution Add detailed RocksDB memory metrics to monitor memory usage breakdown by component type. These metrics are aggregated at the table level (TableMetricGroup) and help users understand which RocksDB components consume the most memory. ### Anything else? _No response_ ### Willingness to contribute - [x] I'm willing to submit a PR! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
