hi Mickael
> No, my plan is to not change the Authorizer APIs. The aclCount() method
stays.
I'll update StandardAuthorizer to use the KIP-877 APIs to register the
metrics listed in the KIP.
thanks again. I will file another jira to be follow-up to deprecate
aclCount()
Best,
Chia-Ping
Mickael M
Hi,
No, my plan is to not change the Authorizer APIs. The aclCount() method stays.
I'll update StandardAuthorizer to use the KIP-877 APIs to register the
metrics listed in the KIP.
Thanks,
Mickael
On Fri, Feb 14, 2025 at 6:21 PM Chia-Ping Tsai wrote:
>
> hi Mickael
>
> thanks for all sharing. i
hi Mickael
thanks for all sharing. it is great to know that all are in progress.
> Broker-side support is next on my todo list and that will include these
metrics.
KIP-877 appears to intend to allow authorizer implementations to write
their own metrics. If this is the case, does KIP-877 plan to
Hi Chia-Ping,
The plan is to introduce these metrics as part of KIP-877 which
supersedes KIP-608:
https://cwiki.apache.org/confluence/display/KAFKA/KIP-877:+Mechanism+for+plugins+and+connectors+to+register+metrics#KIP877:Mechanismforpluginsandconnectorstoregistermetrics-KIP-608
So far we added:
-
hi all,
I'm revisiting authorizer metrics, which are currently absent from the
codebase. While KIP-608 and KIP-801 both propose adding authorizer metrics,
neither of them has implemented the actual metrics. Since authorizer
metrics are valuable for Kafka maintainers, I intend to implement them
bas
