Hi folks, I would like to discuss a proposal that I have in mind: the "observe" API.
The purpose of this API is to return some metrics and gauges from Polaris, like: - what's number of entities (number of tables, views; etc) in a Polaris catalog - what's the number of times a entity as been accessed on a period - optionaly, access to "polished" metrics from table (extracted++ from the metadata) - optionaly, provide extra details (from Parquet metrics for instance) In terms of use cases, this API could be helpful: - to have a policy "activated" depending of this metrics (something like policy A is only valid if a catalog has more than X tables, or policy B is activated when a view has been accessed more than Y times in the last hour, etc). We can have TMS service "fined triggered" with these policies. - to be leverage by a FGAC mechanism (e.g. governance depending of these metrics) - to be easily displayed by a UI or CLI I already have a few ideas in mind that I would be happy to share in a design document. But before that, I would like to get your feedback about this proposal. Thanks ! Regards JB
