[ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505215#comment-14505215
 ] 

Nick Dimiduk commented on PHOENIX-1118:
---------------------------------------

I'm not sure how many folks have a zipkin deployment, so I don't know how 
widely useful integration there will be. Further, zipkin's underlying tools are 
kind of a mirror image of HTrace's, so it's spans need to be converted from one 
format to the other before loading them from the Phoenix table into a Zipkin 
span host. I think it's better to stick with as few operational dependencies as 
possible.

The HTrace project has been working on a web UI, I think a bunch of pieces will 
be released in 3.2.0. There was a meeting [0] to discuss this topic a couple 
weeks ago. Since HTrace is already a dependency, maybe we can focus on making 
the content of Phoenix's spans table available to that UI?

[0]: 
http://mail-archives.apache.org/mod_mbox/htrace-dev/201504.mbox/%3cca+qbeuny9f9zloutoiefb9lekzvbkmkwzrjw52_5-u8jka+...@mail.gmail.com%3e

> Provide a tool for visualizing Phoenix tracing information
> ----------------------------------------------------------
>
>                 Key: PHOENIX-1118
>                 URL: https://issues.apache.org/jira/browse/PHOENIX-1118
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>            Assignee: Nishani 
>              Labels: Java, SQL, Visualization, gsoc2015, mentor
>         Attachments: MockUp1-TimeSlider.png, MockUp2-AdvanceSearch.png, 
> MockUp3-PatternDetector.png, MockUp4-FlameGraph.png
>
>
> Currently there's no means of visualizing the trace information provided by 
> Phoenix. We should provide some simple charting over our metrics tables. Take 
> a look at the following JIRA for sample queries: 
> https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14323151&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to