Meet0861 opened a new issue, #24070: URL: https://github.com/apache/pulsar/issues/24070
### Search before asking - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Motivation Having metric at the server side can help identify if there is any issue from the server side due to producer creation is failing at the client side. Recently we faced this issue where producer object creation was failing due to unavailability of the ledger belongs to the internal topic(__change_events) and consequently it was not able to read the topic policies. But there was no exceptions observed or metric available at the server side related to this to figure this out proactively. ### Solution We can have few metrics available at the server side for failures at the client side due to server side issues. ### Alternatives _No response_ ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] 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: commits-unsubscr...@pulsar.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
