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

Colin Patrick McCabe edited comment on HTRACE-29 at 12/30/14 12:43 AM:
-----------------------------------------------------------------------

Our goal for this initial version is just to have it possible to search for 
spans by start time, end time, description, and duration.  Start, end, duration 
will be indexed in leveldb.  description won't, so searching it will be slower 
unless there are some other parameters given.  We can always index more stuff 
later if this turns out to be a problem.

We were thinking of having a vertical split screen with the search stuff on the 
left, and the results on the right.

Right now, backbone.js and d3.js look like good choices for Javascript 
frameworks.  They are widely known, and we're already using them elsewhere in 
htrace.

Another thing we'd like to implement down the road is some kind of callgraph 
showing which span (descriptions) called which other span descriptions.  Sort 
of a way of seeing control flow.  And possibly some histograms.  We were 
thinking that the user could navigate to these through a tabbed interface with 
the tabs at the top of the screen.  This won't exist in the first version, 
though... it will start pretty basic.


was (Author: cmccabe):
Our goal for this initial version is just to have it possible to search for 
spans by start time, end time, description, and duration.  Start, end, duration 
will be indexed in leveldb.  description won't, so searching it will be slower 
unless there are some other parameters given.  We can always index more stuff 
later if this turns out to be a problem.

We were thinking of having a vertical split screen with the search stuff on the 
left, and the results on the right.

Right now, backbone.js and d3.js look like good choices for Javascript 
frameworks.  They are widely known, and we're already using them elsewhere in 
htrace.

Another thing we'd like to implement down the road is some kind of callgraph 
showing which span (descriptions) called which other span descriptions.  Sort 
of a way of seeing control flow.  And possible some histograms.  We were 
thinking that the user could navigate to these through a tabbed interface with 
the tabs at the top of the screen.  This won't exist in the first version, 
though... it will start pretty basic.

> add javascript web UI for htraced
> ---------------------------------
>
>                 Key: HTRACE-29
>                 URL: https://issues.apache.org/jira/browse/HTRACE-29
>             Project: HTrace
>          Issue Type: Improvement
>            Reporter: Colin Patrick McCabe
>            Assignee: Colin Patrick McCabe
>
> We should add a javascript web UI for htraced.



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

Reply via email to