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

ASF GitHub Bot commented on PHOENIX-1118:
-----------------------------------------

Github user JamesRTaylor commented on the pull request:

    https://github.com/apache/phoenix/pull/103#issuecomment-131611818
  
    Thanks for the update, Nishani. This is definitely an improvement. The 
primary information missing is the query itself. Without this, the user doesn't 
know what they're looking at. The query should be the description of the root 
span. I'd recommend displaying this at the top of the page in the blue box 
instead of the "data retrieved" text. It's important enough to always see this 
information rather than making it a tooltip. 


> 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, Screenshot of dependency 
> tree.png, Screenshot-loading-trace-list.png, m1-mockUI-tracedistribution.png, 
> m1-mockUI-tracetimeline.png, screenshot of tracing timeline.png, screenshot 
> of tracing web app.png, timeline.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