phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ayola Jayamaha <raphaelan...@gmail.com>
Subject Re: [jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information
Date Wed, 03 Jun 2015 14:22:34 GMT
Hi Nick,

Main objective will be UI part. According to the timeline I'm finalizing
the mock uis(basic implementation) and feature list. Yes I will update and
get the community feedback.
Both names are fine. Nishani is preferred.
Thanks.

On Wed, Jun 3, 2015 at 1:55 AM, Nick Dimiduk <ndimiduk@gmail.com> wrote:

> Dropping the incubator list.
>
> What Jesse said :)
>
> This is off to a nice start Nishani! (Sorry, or is it Ayola?) What are you
> thinking of for your next objective? Wiring up the backend to query the
> life Phoenix table? More UI work? Keep at it and as always, let us know if
> you're having troubles.
>
> -n
>
> On Tue, Jun 2, 2015 at 9:48 AM, Jesse Yates <jesse.k.yates@gmail.com>
> wrote:
>
>> Ids are randomly assigned. Spans have parents (the process/thread/logic
>> element) that kicked them off, so each span is going to have a parent id.
>> All 'start' spans have the same 'parent id' the "ROOT SPAN ID".
>>
>> On Tue, Jun 2, 2015 at 8:34 AM Ayola Jayamaha <raphaelanne2@gmail.com>
>> wrote:
>>
>> > Hi,
>> >
>> > I'm planing to use Jetty as the web server(there will be a war file that
>> > can be hosted in any server) and AngularJS and Bootstrap for the Web
>> User
>> > Interface. Is it alright? Currently I'm planing to expose the tracing
>> data
>> > as a REST service(only GET) with json format.
>> >
>> > Can you give me details about the parent id and span id? The
>> relationship
>> > between them ? As I see there are common parent ids and span ids.
>> >
>> > There are some negative ids. Is it purposely done or randomly done?
>> >
>> >
>> > On Tue, Jun 2, 2015 at 10:03 AM, Nishani (JIRA) <jira@apache.org>
>> wrote:
>> >
>> > >
>> > >     [
>> > >
>> >
>> https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14568503#comment-14568503
>> > > ]
>> > >
>> > > Nishani  commented on PHOENIX-1118:
>> > > -----------------------------------
>> > >
>> > > Hi,
>> > > As we discussed I have used Jetty Server. The code is in the repo [1].
>> > The
>> > > screenshot of the tracing web app is attached. Here I have used
>> AngularJS
>> > > and Bootstrap. Regarding the implementation details you can find in my
>> > blog.
>> > >
>> > > [1] https://github.com/AyolaJayamaha/TracingWebApp
>> > >
>> > > > 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
>> > tracing
>> > > web app.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)
>> > >
>> >
>> >
>> >
>> > --
>> > Best Regards,
>> > Ayola Jayamaha
>> > http://ayolajayamaha.blogspot.com/
>> >
>>
>
>


-- 
Best Regards,
Ayola Jayamaha
http://ayolajayamaha.blogspot.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message