Hi Pariksheet, Phoenix Tracing might help you here. See: http://phoenix.apache.org/tracing.html
With tracing on, you can get information on the the scans being executed - duration of each scan, region server on which it is being executed, query plan etc. All this is logged in the trace table (default - SYSTEM.TRACING_STATS). You would want to use our latest release 4.3 (soon to be out) since it has a critical fix for a bug that was causing region servers to crash (https://issues.apache.org/jira/browse/PHOENIX-1596). We have plans for enhancing our tracing framework. See - https://issues.apache.org/jira/browse/PHOENIX-1121 As far as exposing JDBC metrics through JMX, we have something similar planned for logging client side metrics: https://issues.apache.org/jira/browse/PHOENIX-1452 Hope this helps. - Samarth On Wed, Feb 11, 2015 at 9:00 AM, Nick Dimiduk <ndimi...@gmail.com> wrote: > Hi Pari, > > I'm not aware of a Phoenix-aware, end-to-end solution here. You can > probably write a custom collector for a Phenox application that can report > into OpenTSDB; I think JDBC metrics are available via JMX. That would be a > great addition for that project! > > I've also seen a product demo from HP that does a lot of this for other > tools on HBase, though I don't think it supports Phoenix yet (cc Rohit). > > Thanks, > Nick > > On Wednesday, February 11, 2015, Pariksheet Barapatre < > pbarapa...@gmail.com> > wrote: > > > Hello All, > > > > Can you suggest good monitoring tool for phoenix. Our QA hbase cluster is > > crashing randomly. We wanted to know stats like which query causing the > > issue and how many queries running on that particular time window, > resource > > consumption of query etc. > > > > Cheers > > Pari > > >
