Thank you for the proposal Pierre ! I think having metrics on the entities that Polaris is really helpful for telemetry as well making decisions on when and what partitions to run compactions. Iceberg already emits the metric from client end to the rest server via RestMetricsReporter <https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/rest/RESTMetricsReporter.java#L60> and things like ScanMetrics <https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/metrics/ScanMetrics.java> / CommitMetrics <https://github.com/apache/iceberg/blob/main/core/src/main/java/org/apache/iceberg/metrics/CommitMetrics.java> are already available but at this point we don't persist them and hence they are lost, there has been a request for this in Polaris slack too ! My recommendations would start from here !
Best, Prashant Singh On Thu, Sep 4, 2025 at 8:41 AM Pierre Laporte <[email protected]> wrote: > Hi folks, > > I would like to propose the addition of a component to Polaris that would > build and maintain operational metrics for the Data Lake tables and views. > The main idea is that, if those metrics can be shared across multiple Table > Management Services and/or other external services, then it would make > sense to have those metrics served by Polaris. > > I believe this feature would nor only add value to Polaris but also further > advance it as central point in the Data Lake. > > The detailed proposal document is here: > > https://docs.google.com/document/d/1yHvLwqNVD3Z84KYcc_m3c4M8bMijTXg9iP1CR0JXxCc > > Please let me know if you have any feedback or comment ! > > Thanks > -- > > Pierre >
