This Jira is to track adding complete metrics to the Java client. There are many cases where applications using the client have issues that are difficult to debug. The primary reason is that it's hard to reason about what the application is doing with the Kudu client without inspecting the code, and even then it can be easy to miss an issue in the code as well.
For example we have seen many cases where an application creates a Kudu client, sends a few messages, and then closes the client in a loop. Creating many clients over an over not only impacts performance/stability of the application but can also put unwelcome load on the servers. If we had request metrics with a client id tag periodically logged, then it would be easy to grep the application logs for unique client ids and spot the issue and the offending application.