[jira] [Updated] (PHOENIX-5030) Page to view what host a query comes from

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-5030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-5030:
--
Description: There is no any way to view the host for a sql query 
generated. This should be fixed on the tracing Web App.

> Page to view what host a query comes from
> -
>
> Key: PHOENIX-5030
> URL: https://issues.apache.org/jira/browse/PHOENIX-5030
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>Priority: Major
>
> There is no any way to view the host for a sql query generated. This should 
> be fixed on the tracing Web App.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (PHOENIX-5030) Page to view what host a query comes from

[Nishani (JIRA)]

Nishani  created PHOENIX-5030:
-

 Summary: Page to view what host a query comes from
 Key: PHOENIX-5030
 URL: https://issues.apache.org/jira/browse/PHOENIX-5030
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Assigned] (PHOENIX-4428) Trace details can't be shown in the Phoenix Tracing Web Application

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-4428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-4428:
-

Assignee: Nishani 

> Trace details can't be shown in the Phoenix Tracing Web Application
> ---
>
> Key: PHOENIX-4428
> URL: https://issues.apache.org/jira/browse/PHOENIX-4428
> Project: Phoenix
>  Issue Type: Bug
>Affects Versions: 4.13.0
>Reporter: Alex Chistyakov
>Assignee: Nishani 
>Priority: Major
> Attachments: Screen Shot 2017-12-01 at 18.34.07.png, Screen Shot 
> 2017-12-01 at 18.34.12.png
>
>
> A timeline or a dependency tree can't be shown for a trace.
> {code}
> 298752 [qtp440434003-46] WARN org.eclipse.jetty.servlet.ServletHandler  - 
> /trace/
> java.lang.RuntimeException: The passed parentId/traceId is not a number.
> at 
> org.apache.phoenix.tracingwebapp.http.TraceServlet.searchTrace(TraceServlet.java:117)
> at 
> org.apache.phoenix.tracingwebapp.http.TraceServlet.doGet(TraceServlet.java:67)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
> at 
> org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:648)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
> at 
> org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:559)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072)
> at 
> org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382)
> at 
> org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
> at 
> org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006)
> at 
> org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
> at 
> org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
> at org.eclipse.jetty.server.Server.handle(Server.java:365)
> at 
> org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485)
> at 
> org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926)
> at 
> org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988)
> at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635)
> at 
> org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235)
> at 
> org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
> at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627)
> at 
> org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51)
> at 
> org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
> at 
> org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.NumberFormatException: null
> at java.lang.Long.parseLong(Long.java:552)
> at java.lang.Long.parseLong(Long.java:631)
> at 
> org.apache.phoenix.tracingwebapp.http.TraceServlet.searchTrace(TraceServlet.java:114)
> ... 26 more
> {code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (PHOENIX-2187) Creating a front-end application for Phoenix Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2187:
--
Summary: Creating a front-end application for Phoenix Tracing Web App  
(was: Creating the front-end application for Phoenix Tracing Web App)

> Creating a front-end application for Phoenix Tracing Web App
> 
>
> Key: PHOENIX-2187
> URL: https://issues.apache.org/jira/browse/PHOENIX-2187
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
> Fix For: 4.6.0
>
> Attachments: 2187-master.patch
>
>
> This will include the following tracing visualization features.
> List - lists the traces with their attributes
> Trace Count - Chart view over the trace description
> Dependency Tree - tree view of  trace ids
> Timeline - timeline of trace ids
> Trace Distribution - Distribution chart of hosts of traces



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Commented] (PHOENIX-3193) Tracing UI cleanup - final tasks before GSoC pull request

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-3193:
---

Hi,
When the jetty version 7 is used the issue is resolved. I am working on a
better solution.

Thanks.

On Tue, Aug 30, 2016 at 12:55 AM, ASF GitHub Bot (JIRA) 




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


> Tracing UI cleanup - final tasks before GSoC pull request
> -
>
> Key: PHOENIX-3193
> URL: https://issues.apache.org/jira/browse/PHOENIX-3193
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>
> Points from GSoC presentation on tracing imporvements:
> *Tracing UI*
> * Remove line chart 
> * In list page, run query with description, start_time, (end_time-start_time) 
> duration from T where trace_id = ?
> * More space for descriptions on bar chart. Wrap if necessary
> * Label for X axis on timeline sometime again start from 0, if X axis is in 
> seconds then it should not rollover after 60 seconds unless minutes are also 
> shown
> * X-axis labeled as Node on various charts, but should be Percentage
> *Zipkin*
> * Flip zipkin chart on vertical axis with arrows going other way. So start 
> from the top level root on the leftmost side and work toward children on the 
> right.
> * Ask zipkin community if there's a way to tell it that date/time is in 
> milliseconds.
> *Overall*
> * Please put together a pull request to the phoenix project to add the 
> zipkiin work you've done to the OS project. Ideally, include the zipkin work 
> in the phoenix-tracing module and call it phoeix-tracing. Only if there is 
> some major hurdle, create a new module.
> * Test with trace_ids that have multiple spans with duration (end_time - 
> start_time) > 5 ms and verify that UI and Zipkin output shows the correct 
> corresponding timeline
>   



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

[jira] [Created] (PHOENIX-3190) Creating Tracing Visualization Ducumentation

[Nishani (JIRA)]

Nishani  created PHOENIX-3190:
-

 Summary: Creating Tracing Visualization Ducumentation
 Key: PHOENIX-3190
 URL: https://issues.apache.org/jira/browse/PHOENIX-3190
 Project: Phoenix
  Issue Type: Sub-task
Affects Versions: 4.8.0
Reporter: Nishani 
Assignee: Nishani 
 Fix For: 4.8.0


Documentation will contain
-Improved Search Features
-How to start the Phoenix Zipkin Web App
-How to change the zookeeper host and port 
-Features of Phoenix Zipkin Web App




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

[jira] [Updated] (PHOENIX-1119) Use Zipkin to visualize Phoenix metrics data

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1119:
--
Attachment: spans.png
dependency.png
callcount.png
dependencytree.png

Hi,
The screenshots are attached. Please share your feedback. 
https://github.com/AyolaJayamaha/phoenix/tree/zipkin 

> Use Zipkin to visualize Phoenix metrics data
> 
>
> Key: PHOENIX-1119
> URL: https://issues.apache.org/jira/browse/PHOENIX-1119
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>  Labels: gsoc2016, tracing
> Attachments: Screenshot from 2016-07-30.png, callcount.png, 
> dependency.png, dependencytree.png, spans.png
>
>
> Zipkin provides a nice tool for visualizing trace information: 
> http://twitter.github.io/zipkin/
> It's likely not difficult to visualize the Phoenix tracing data through this 
> tool.



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

[jira] [Updated] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2208:
--
Attachment: tracetimeline.png
traceduration.png
tracedistributionbycount.png
tracebyhostname.png

Hi,

The tracing timeline with custom tooltip is attached. The trace distribution is 
visualized by hostname, by trace count and by durations.
 

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
> Attachments: Query-builder.png, Screenshot from 2016-06-21 
> 18-03-02.png, tracebyhostname.png, tracedistributionbycount.png, 
> traceduration.png, tracetimeline.png
>
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Updated] (PHOENIX-1119) Use Zipkin to visualize Phoenix metrics data

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1119:
--
Attachment: Screenshot from 2016-07-30.png

Hi,
The custom zipkin-server is created. The phoenix tracing table data needs to be 
read and converted into zipkin traces. Then they are exposed through the rest 
interface which serve the zipkin ui.

> Use Zipkin to visualize Phoenix metrics data
> 
>
> Key: PHOENIX-1119
> URL: https://issues.apache.org/jira/browse/PHOENIX-1119
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>  Labels: gsoc2016, tracing
> Attachments: Screenshot from 2016-07-30.png
>
>
> Zipkin provides a nice tool for visualizing trace information: 
> http://twitter.github.io/zipkin/
> It's likely not difficult to visualize the Phoenix tracing data through this 
> tool.



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

[jira] [Created] (PHOENIX-3034) Passing zookeeper quorum host and port numbers as commandline arguments

[Nishani (JIRA)]

Nishani  created PHOENIX-3034:
-

 Summary: Passing zookeeper quorum host and port numbers as 
commandline arguments
 Key: PHOENIX-3034
 URL: https://issues.apache.org/jira/browse/PHOENIX-3034
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.8.0
Reporter: Nishani 
Priority: Minor


Currently the host and port are set to localhost:2181. They need to be changed 
if user requires.



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

[jira] [Updated] (PHOENIX-2701) Improve Tracing UI in Phoenix

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2701:
--
Attachment: Screenshot from 2016-06-18 16-50-46.png
Screenshot from 2016-06-21 18-07-09.png
Screenshot from 2016-06-21 18-07-04.png
Screenshot from 2016-06-21 18-05-45.png
Screenshot from 2016-06-21 18-03-02.png

Hi All,

The sample screenshots from the query-builder branch[1] are attached.
Any other requirements or improvements needed please mention.

Thank you.
[1] https://github.com/AyolaJayamaha/phoenix/tree/query-builder

> Improve Tracing UI in Phoenix
> -
>
> Key: PHOENIX-2701
> URL: https://issues.apache.org/jira/browse/PHOENIX-2701
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>  Labels: gsoc2016, tracing
> Attachments: Screenshot from 2016-06-18 16-50-46.png, Screenshot from 
> 2016-06-21 18-03-02.png, Screenshot from 2016-06-21 18-05-45.png, Screenshot 
> from 2016-06-21 18-07-04.png, Screenshot from 2016-06-21 18-07-09.png
>
>
> See subtasks below for moving the Tracing UI work forward. An alternate 
> approach would be to allow the tracing backend to be plugged into Zipkin 
> (PHOENIX-1119).



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

[jira] [Updated] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2208:
--
Attachment: Screenshot from 2016-06-21 18-03-02.png

Hi All,

Attached is the screenshot of trace information retrieved from query instead of 
trace_id. The code is on the below branch.

https://github.com/AyolaJayamaha/phoenix/tree/query-builder 

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
> Attachments: Query-builder.png, Screenshot from 2016-06-21 
> 18-03-02.png
>
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Updated] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2208:
--
Attachment: Query-builder.png

MockUI for Query Builder is attached. Options to turn trace on, execute the 
query and turn trace off are given. For the result set timeline,list, 
dependency tree and distribution can be shown.

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
> Attachments: Query-builder.png
>
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Commented] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2208:
---

Hi,

An issue is raised if the query is not unique (ex. same query is run multiple 
times). Therefore trace id is more appropriate. Else the first few characters 
from description of traces can be used.

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Issue Comment Deleted] (PHOENIX-2211) Set a common Jetty version for Phoenix

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2211:
--
Comment: was deleted

(was: A common Jetty version can be included for the whole project from 
communicating with Nick Dimiduk.)

> Set a common Jetty version for Phoenix
> --
>
> Key: PHOENIX-2211
> URL: https://issues.apache.org/jira/browse/PHOENIX-2211
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>  Labels: tracing
>
> Jetty is used in the Tracing Web Application. The Jetty version used is 
> defined at the root pom file. The Jetty version that is used needs to be 
> common to the whole Phoenix project.



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

[jira] [Assigned] (PHOENIX-1119) Use Zipkin to visualize Phoenix metrics data

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-1119:
-

Assignee: Nishani 

> Use Zipkin to visualize Phoenix metrics data
> 
>
> Key: PHOENIX-1119
> URL: https://issues.apache.org/jira/browse/PHOENIX-1119
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>  Labels: gsoc2016, tracing
>
> Zipkin provides a nice tool for visualizing trace information: 
> http://twitter.github.io/zipkin/
> It's likely not difficult to visualize the Phoenix tracing data through this 
> tool.



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

[jira] [Commented] (PHOENIX-1119) Use Zipkin to visualize Phoenix metrics data

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1119:
---

Hi All,

htrace-zipkin provides span receiver sends spans to zipkin collector. 
htrace-hbase provides span receiver which sends tracing spans to HBase and a 
viewer which retrieves spans from HBase and displays them graphically.

[1] https://github.com/apache/incubator-htrace

> Use Zipkin to visualize Phoenix metrics data
> 
>
> Key: PHOENIX-1119
> URL: https://issues.apache.org/jira/browse/PHOENIX-1119
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>  Labels: gsoc2016, tracing
>
> Zipkin provides a nice tool for visualizing trace information: 
> http://twitter.github.io/zipkin/
> It's likely not difficult to visualize the Phoenix tracing data through this 
> tool.



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

[jira] [Issue Comment Deleted] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2208:
--
Comment: was deleted

(was: Hi,

We can achieve this by having a module for mapping queries to tracing IDs. And 
this module includes user interface elements and it can be plugged to all pages 
where it needs as mentioned by [~mujtabachohan]
)

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Issue Comment Deleted] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2208:
--
Comment: was deleted

(was: For the regex query search can we have sql query %like ? Yes it is 
possible to have top headers for each feature. )

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Commented] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2208:
---

Hi,

We can achieve this by having a module for mapping queries to tracing IDs. And 
this module includes user interface elements and it can be plugged to all pages 
where it needs as mentioned by [~mujtabachohan]


> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Commented] (PHOENIX-2166) Prevent writing to tracing table when tracing data collected

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2166:
---

Hi [~mujtabachohan]
In tracing web app it shows all the records in tracing table that includes 
reading, writing data to tracing table also. Only for visualization purposes we 
can skip those information by filtering the queries.
Is there any configuration to stop writing tracing information of tracing table 
to tracing table.

If there is no configuration level we have to change the code base.

> Prevent writing to tracing table when tracing data collected
> 
>
> Key: PHOENIX-2166
> URL: https://issues.apache.org/jira/browse/PHOENIX-2166
> Project: Phoenix
>  Issue Type: Sub-task
>Affects Versions: 4.5.0
>Reporter: Mujtaba Chohan
>  Labels: gsoc2016, tracing
>
> When tracing is turned ON, trace table grows at fast pace and is filled with 
> the following traces which should not be present:
> {code}
> Executing UPSERT INTO SYSTEM.TRACING_STATS (trace_id, ...
> Writing mutation batch for table: SYSTEM.TRACING_STATS ...
> and so on
> {code}



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

[jira] [Commented] (PHOENIX-2211) Set a common Jetty version for Phoenix

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2211:
---

A common Jetty version can be included for the whole project from communicating 
with Nick Dimiduk.

> Set a common Jetty version for Phoenix
> --
>
> Key: PHOENIX-2211
> URL: https://issues.apache.org/jira/browse/PHOENIX-2211
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>  Labels: tracing
>
> Jetty is used in the Tracing Web Application. The Jetty version used is 
> defined at the root pom file. The Jetty version that is used needs to be 
> common to the whole Phoenix project.



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

[jira] [Updated] (PHOENIX-1120) Provide additional metrics beyond wall clock time

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1120:
--
Description: 
We should add additional metrics beyond wall clock time. In particular:
- cpu time
- io time
- idle time
- memory
- resource wastage
Probably a zillion more.

  was:
We should add additional metrics beyond wall clock time. In particular:
- cpu time
- io time
- idle time
Probably a zillion more.


> Provide additional metrics beyond wall clock time
> -
>
> Key: PHOENIX-1120
> URL: https://issues.apache.org/jira/browse/PHOENIX-1120
> Project: Phoenix
>  Issue Type: Sub-task
>Affects Versions: 4.1.0
>Reporter: James Taylor
>  Labels: tracing
>
> We should add additional metrics beyond wall clock time. In particular:
> - cpu time
> - io time
> - idle time
> - memory
> - resource wastage
> Probably a zillion more.



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

[jira] [Commented] (PHOENIX-2403) PHOENIX-2248 sub-task: Reduce size of Phoenix Server runnable jar

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2403:
---

+1

> PHOENIX-2248 sub-task: Reduce size of Phoenix Server runnable jar
> -
>
> Key: PHOENIX-2403
> URL: https://issues.apache.org/jira/browse/PHOENIX-2403
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Mujtaba Chohan
>Assignee: Mujtaba Chohan
>Priority: Minor
> Attachments: PHOENIX-2403.patch
>
>
> We can reduce size of phoenix-server-runnable uber jar by adding Phoenix 
> client jar on classpath instead of bundling all classes in 
> phoenix-server-runnable jar.



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

[jira] [Commented] (PHOENIX-2391) PHOENIX-2248 sub-task: Reduce size of Tracing web-app uber jar

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2391:
---

Thanks for the patch.

> PHOENIX-2248 sub-task: Reduce size of Tracing web-app uber jar
> --
>
> Key: PHOENIX-2391
> URL: https://issues.apache.org/jira/browse/PHOENIX-2391
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Mujtaba Chohan
>Assignee: Mujtaba Chohan
> Attachments: PHOENIX-2391.patch
>
>
> Update tracing web-app. python script so it can use phoenix-client jar and 
> tracing web-app minimal jar plus phoenix client jar instead.



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

[jira] [Commented] (PHOENIX-2218) Tracing UI - List page should display last x number of top level traces

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2218:
---

The current list view has option to load the recent n number of traces. So is 
there any more needs to fulfill? 

> Tracing UI - List page should display last x number of top level traces
> ---
>
> Key: PHOENIX-2218
> URL: https://issues.apache.org/jira/browse/PHOENIX-2218
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>Priority: Minor
>  Labels: tracing
>
> Rather than displaying all traces, list page for traces should only display 
> last few traces or in the last x hours. This number can be chosen from drop 
> down list. Also only top level traces and its description should be shown.



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

[jira] [Commented] (PHOENIX-2218) Tracing UI - List page should display last x number of top level traces

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2218:
---

ok. Thanks. I'll try to proceed with it.

> Tracing UI - List page should display last x number of top level traces
> ---
>
> Key: PHOENIX-2218
> URL: https://issues.apache.org/jira/browse/PHOENIX-2218
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>Priority: Minor
>  Labels: tracing
>
> Rather than displaying all traces, list page for traces should only display 
> last few traces or in the last x hours. This number can be chosen from drop 
> down list. Also only top level traces and its description should be shown.



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

[jira] [Commented] (PHOENIX-2218) Tracing UI - List page should display last x number of top level traces

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2218:
---

Hi,

Currently the UI loads the latest x number of traces. 'x' can be entered on the 
UI.
What is needed to be changed?

> Tracing UI - List page should display last x number of top level traces
> ---
>
> Key: PHOENIX-2218
> URL: https://issues.apache.org/jira/browse/PHOENIX-2218
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>Priority: Minor
>  Labels: tracing
>
> Rather than displaying all traces, list page for traces should only display 
> last few traces or in the last x hours. This number can be chosen from drop 
> down list. Also only top level traces and its description should be shown.



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

[jira] [Assigned] (PHOENIX-1519) Determine the usefulness of tracing

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-1519:
-

Assignee: Nishani 

> Determine the usefulness of tracing
> ---
>
> Key: PHOENIX-1519
> URL: https://issues.apache.org/jira/browse/PHOENIX-1519
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: James Taylor
>Assignee: Nishani 
>
> In order to help prioritize the child JIRAs under PHOENIX-1121, we need to do 
> a usability study around tracing. What problem(s) are we trying to solve and 
> what's the delta between the existing tracing feature and the required 
> tracing features. Are we capturing enough information to be useful? Is it 
> structured in a such a way to lend itself to analysis? 
> For example, is the main use case of tracing to determine the top 10 queries 
> that take the longest amount of time in production? Would we then want 
> tracing on all the time, so having a way to enable/disable tracing 
> (PHOENIX-1433, PHOENIX-1191, PHOENIX-1518, PHOENIX-1115) becomes moot.
> Or is it more of something that would be used in a perf testing environment 
> where we'd need to information generated to be only for a particular query 
> (in which case the above JIRAs are more important)?



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

[jira] [Commented] (PHOENIX-1119) Use Zipkin to visualize Phoenix metrics data

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1119:
---

As I think this issue is redundant since we have Tracing Web App installed. The 
web app can visualize all the required tracing information and Phoenix Metrics. 

> Use Zipkin to visualize Phoenix metrics data
> 
>
> Key: PHOENIX-1119
> URL: https://issues.apache.org/jira/browse/PHOENIX-1119
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: James Taylor
>
> Zipkin provides a nice tool for visualizing trace information: 
> http://twitter.github.io/zipkin/
> It's likely not difficult to visualize the Phoenix tracing data through this 
> tool.



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

[jira] [Created] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

Nishani  created PHOENIX-2273:
-

 Summary: Join Queries fail to give results within a finite time 
period 
 Key: PHOENIX-2273
 URL: https://issues.apache.org/jira/browse/PHOENIX-2273
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 


When the join queries are run on Phoenix Data Tables it fails to give results. 
Either it takes a long time to give the results or the join queries are not 
executed properly. 



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

https://github.com/apache/phoenix/tree/master/phoenix-tracing-webapp

The solution Tracing Web App as tool for trace visualization is added to 
Phoenix Master.

> Provide a tool for visualizing Phoenix tracing information
> --
>
> Key: PHOENIX-1118
> URL: https://issues.apache.org/jira/browse/PHOENIX-1118
> Project: Phoenix
>  Issue Type: New Feature
>Reporter: James Taylor
>Assignee: Nishani 
>  Labels: Java, SQL, Visualization, gsoc2015, mentor
> Fix For: 4.6.0
>
> 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151
> The tool need to provide visualization over SYSTEM.TRACING_STATS table.



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

[jira] [Resolved] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  resolved PHOENIX-1118.
---
Resolution: Fixed

> Provide a tool for visualizing Phoenix tracing information
> --
>
> Key: PHOENIX-1118
> URL: https://issues.apache.org/jira/browse/PHOENIX-1118
> Project: Phoenix
>  Issue Type: New Feature
>Reporter: James Taylor
>Assignee: Nishani 
>  Labels: Java, SQL, Visualization, gsoc2015, mentor
> Fix For: 4.6.0
>
> 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=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151
> The tool need to provide visualization over SYSTEM.TRACING_STATS table.



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

[jira] [Commented] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2273:
---

The required information is added. If you need more details please mention them.

Thanks

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Updated] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2273:
--
Attachment: ScreenshotOfOrders
ScreenShotOfJoinquery.png

The Tables CUSTOMERS & ORDERS used for join query.

create table ORDERS (id integer not null primary key, item varchar, customerid 
varchar);

create table CUSTOMERS (id integer not null primary key, name varchar);

SELECT O.ID, C.Name, O.Item FROM Orders AS O INNER JOIN Customers AS C ON 
O.CustomerID = C.ID;

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Assigned] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-2273:
-

Assignee: Nishani 

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Comment Edited] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

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

Nishani  edited comment on PHOENIX-2273 at 9/19/15 5:29 AM:


Hi [~maryannxue] ,

The required information is added. If you need more details please mention them.

Thanks


was (Author: nishani):
[~maryannxue]
Hi [~maryannxue]
The required information is added. If you need more details please mention them.

Thanks

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Comment Edited] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

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

Nishani  edited comment on PHOENIX-2273 at 9/19/15 5:28 AM:


[~maryannxue]
Hi [~maryannxue]
The required information is added. If you need more details please mention them.

Thanks


was (Author: nishani):
The required information is added. If you need more details please mention them.

Thanks

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Commented] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2273:
---

The Environmental and System Matrices are given below.

jdk1.8.0_45
hbase-0.94.27
zookeeper-3.4.6
phoenix-3.3.1

OS - Linux Mint 17.1 "Rebecca"

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Commented] (PHOENIX-2273) Join Queries fail to give results within a finite time period

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2273:
---

I have followed http://phoenix.apache.org/joins.html in creating a join query. 
But it fails to give any results even after hours of waiting.
The size and schema of the tables are given in the screenshots.

Thank you.

> Join Queries fail to give results within a finite time period 
> --
>
> Key: PHOENIX-2273
> URL: https://issues.apache.org/jira/browse/PHOENIX-2273
> Project: Phoenix
>  Issue Type: Bug
>Reporter: Nishani 
>  Labels: Phoenix, query
> Attachments: ScreenShotOfJoinquery.png, 
> ScreenshotOfOrders
>
>
> When the join queries are run on Phoenix Data Tables it fails to give 
> results. Either it takes a long time to give the results or the join queries 
> are not executed properly. 



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

[jira] [Resolved] (PHOENIX-2244) fix rat violations

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  resolved PHOENIX-2244.
---
Resolution: Fixed

Issue Resolved.

> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani 
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before 
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
>   src/main/webapp/css/bootstrap-theme.css
>   src/main/webapp/css/bootstrap-theme.css.map
>   src/main/webapp/css/bootstrap.css
>   src/main/webapp/css/bootstrap.css.map
>   src/main/webapp/css/font-awesome.css
>   src/main/webapp/fonts/fontawesome-webfont.svg
>   src/main/webapp/fonts/glyphicons-halflings-regular.svg
>   src/main/webapp/index.html
>   src/main/webapp/js/api/chart-model.js
>   src/main/webapp/js/app.js
>   src/main/webapp/js/config/chart-config.js
>   src/main/webapp/js/controllers/accordion-controllers.js
>   src/main/webapp/js/controllers/dependency-tree-controllers.js
>   src/main/webapp/js/controllers/list-controllers.js
>   src/main/webapp/js/controllers/search-controllers.js
>   src/main/webapp/js/controllers/timeline-controllers.js
>   src/main/webapp/js/controllers/trace-count-controllers.js
>   src/main/webapp/js/controllers/trace-distribution-controllers.js
>   src/main/webapp/js/factories/statement-factory-config.js
>   src/main/webapp/js/factories/statement-factory.js
>   src/main/webapp/js/lib/angular-mocks.js
>   src/main/webapp/js/lib/angular-route.js
>   src/main/webapp/js/lib/angular.js
>   src/main/webapp/js/lib/bootstrap.js
>   src/main/webapp/js/lib/jquery-2.1.4.js
>   src/main/webapp/js/lib/jquery.min.js
>   src/main/webapp/js/lib/ng-google-chart.js
>   src/main/webapp/js/lib/ui-bootstrap-tpls.js
>   src/main/webapp/js/services/generate-statement-service.js
>   src/main/webapp/partials/about.html
>   src/main/webapp/partials/chart.html
>   src/main/webapp/partials/contact.html
>   src/main/webapp/partials/dependency-tree.html
>   src/main/webapp/partials/google-chart.html
>   src/main/webapp/partials/help.html
>   src/main/webapp/partials/home.html
>   src/main/webapp/partials/list.html
>   src/main/webapp/partials/phoenix-trace.html
>   src/main/webapp/partials/search.html
>   src/main/webapp/WEB-INF/web.xml
>   src/test/webapp/js/specs/app-route-spec.js
>   src/test/webapp/js/specs/timeline-ctrl-spec.js
>   src/test/webapp/js/specs/trace-list-ctrl-spec.js
>   src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}



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

[jira] [Reopened] (PHOENIX-2244) fix rat violations

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reopened PHOENIX-2244:
---

> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani 
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before 
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
>   src/main/webapp/css/bootstrap-theme.css
>   src/main/webapp/css/bootstrap-theme.css.map
>   src/main/webapp/css/bootstrap.css
>   src/main/webapp/css/bootstrap.css.map
>   src/main/webapp/css/font-awesome.css
>   src/main/webapp/fonts/fontawesome-webfont.svg
>   src/main/webapp/fonts/glyphicons-halflings-regular.svg
>   src/main/webapp/index.html
>   src/main/webapp/js/api/chart-model.js
>   src/main/webapp/js/app.js
>   src/main/webapp/js/config/chart-config.js
>   src/main/webapp/js/controllers/accordion-controllers.js
>   src/main/webapp/js/controllers/dependency-tree-controllers.js
>   src/main/webapp/js/controllers/list-controllers.js
>   src/main/webapp/js/controllers/search-controllers.js
>   src/main/webapp/js/controllers/timeline-controllers.js
>   src/main/webapp/js/controllers/trace-count-controllers.js
>   src/main/webapp/js/controllers/trace-distribution-controllers.js
>   src/main/webapp/js/factories/statement-factory-config.js
>   src/main/webapp/js/factories/statement-factory.js
>   src/main/webapp/js/lib/angular-mocks.js
>   src/main/webapp/js/lib/angular-route.js
>   src/main/webapp/js/lib/angular.js
>   src/main/webapp/js/lib/bootstrap.js
>   src/main/webapp/js/lib/jquery-2.1.4.js
>   src/main/webapp/js/lib/jquery.min.js
>   src/main/webapp/js/lib/ng-google-chart.js
>   src/main/webapp/js/lib/ui-bootstrap-tpls.js
>   src/main/webapp/js/services/generate-statement-service.js
>   src/main/webapp/partials/about.html
>   src/main/webapp/partials/chart.html
>   src/main/webapp/partials/contact.html
>   src/main/webapp/partials/dependency-tree.html
>   src/main/webapp/partials/google-chart.html
>   src/main/webapp/partials/help.html
>   src/main/webapp/partials/home.html
>   src/main/webapp/partials/list.html
>   src/main/webapp/partials/phoenix-trace.html
>   src/main/webapp/partials/search.html
>   src/main/webapp/WEB-INF/web.xml
>   src/test/webapp/js/specs/app-route-spec.js
>   src/test/webapp/js/specs/timeline-ctrl-spec.js
>   src/test/webapp/js/specs/trace-list-ctrl-spec.js
>   src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}



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

[jira] [Issue Comment Deleted] (PHOENIX-2244) fix rat violations

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2244:
--
Comment: was deleted

(was: Issue Resolved.)

> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani 
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before 
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
>   src/main/webapp/css/bootstrap-theme.css
>   src/main/webapp/css/bootstrap-theme.css.map
>   src/main/webapp/css/bootstrap.css
>   src/main/webapp/css/bootstrap.css.map
>   src/main/webapp/css/font-awesome.css
>   src/main/webapp/fonts/fontawesome-webfont.svg
>   src/main/webapp/fonts/glyphicons-halflings-regular.svg
>   src/main/webapp/index.html
>   src/main/webapp/js/api/chart-model.js
>   src/main/webapp/js/app.js
>   src/main/webapp/js/config/chart-config.js
>   src/main/webapp/js/controllers/accordion-controllers.js
>   src/main/webapp/js/controllers/dependency-tree-controllers.js
>   src/main/webapp/js/controllers/list-controllers.js
>   src/main/webapp/js/controllers/search-controllers.js
>   src/main/webapp/js/controllers/timeline-controllers.js
>   src/main/webapp/js/controllers/trace-count-controllers.js
>   src/main/webapp/js/controllers/trace-distribution-controllers.js
>   src/main/webapp/js/factories/statement-factory-config.js
>   src/main/webapp/js/factories/statement-factory.js
>   src/main/webapp/js/lib/angular-mocks.js
>   src/main/webapp/js/lib/angular-route.js
>   src/main/webapp/js/lib/angular.js
>   src/main/webapp/js/lib/bootstrap.js
>   src/main/webapp/js/lib/jquery-2.1.4.js
>   src/main/webapp/js/lib/jquery.min.js
>   src/main/webapp/js/lib/ng-google-chart.js
>   src/main/webapp/js/lib/ui-bootstrap-tpls.js
>   src/main/webapp/js/services/generate-statement-service.js
>   src/main/webapp/partials/about.html
>   src/main/webapp/partials/chart.html
>   src/main/webapp/partials/contact.html
>   src/main/webapp/partials/dependency-tree.html
>   src/main/webapp/partials/google-chart.html
>   src/main/webapp/partials/help.html
>   src/main/webapp/partials/home.html
>   src/main/webapp/partials/list.html
>   src/main/webapp/partials/phoenix-trace.html
>   src/main/webapp/partials/search.html
>   src/main/webapp/WEB-INF/web.xml
>   src/test/webapp/js/specs/app-route-spec.js
>   src/test/webapp/js/specs/timeline-ctrl-spec.js
>   src/test/webapp/js/specs/trace-list-ctrl-spec.js
>   src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}



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

[jira] [Commented] (PHOENIX-2244) fix rat violations

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2244:
---

Hi,

Is it ok to update the respective PRs?

Thanks.

> fix rat violations
> --
>
> Key: PHOENIX-2244
> URL: https://issues.apache.org/jira/browse/PHOENIX-2244
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nick Dimiduk
>Assignee: Nishani 
>Priority: Blocker
> Fix For: 4.6.0
>
>
> We'll need to resolve the licensing header violations introduced here before 
> we can release.
> {noformat}
> *
> Summary
> ---
> Generated at: 2015-09-09T16:45:47-07:00
> Notes: 0
> Binaries: 9
> Archives: 1
> Standards: 53
> Apache Licensed: 9
> Generated Documents: 0
> JavaDocs are generated and so license header is optional
> Generated files do not required license headers
> 44 Unknown Licenses
> ***
> Unapproved licenses:
>   src/main/webapp/css/bootstrap-theme.css
>   src/main/webapp/css/bootstrap-theme.css.map
>   src/main/webapp/css/bootstrap.css
>   src/main/webapp/css/bootstrap.css.map
>   src/main/webapp/css/font-awesome.css
>   src/main/webapp/fonts/fontawesome-webfont.svg
>   src/main/webapp/fonts/glyphicons-halflings-regular.svg
>   src/main/webapp/index.html
>   src/main/webapp/js/api/chart-model.js
>   src/main/webapp/js/app.js
>   src/main/webapp/js/config/chart-config.js
>   src/main/webapp/js/controllers/accordion-controllers.js
>   src/main/webapp/js/controllers/dependency-tree-controllers.js
>   src/main/webapp/js/controllers/list-controllers.js
>   src/main/webapp/js/controllers/search-controllers.js
>   src/main/webapp/js/controllers/timeline-controllers.js
>   src/main/webapp/js/controllers/trace-count-controllers.js
>   src/main/webapp/js/controllers/trace-distribution-controllers.js
>   src/main/webapp/js/factories/statement-factory-config.js
>   src/main/webapp/js/factories/statement-factory.js
>   src/main/webapp/js/lib/angular-mocks.js
>   src/main/webapp/js/lib/angular-route.js
>   src/main/webapp/js/lib/angular.js
>   src/main/webapp/js/lib/bootstrap.js
>   src/main/webapp/js/lib/jquery-2.1.4.js
>   src/main/webapp/js/lib/jquery.min.js
>   src/main/webapp/js/lib/ng-google-chart.js
>   src/main/webapp/js/lib/ui-bootstrap-tpls.js
>   src/main/webapp/js/services/generate-statement-service.js
>   src/main/webapp/partials/about.html
>   src/main/webapp/partials/chart.html
>   src/main/webapp/partials/contact.html
>   src/main/webapp/partials/dependency-tree.html
>   src/main/webapp/partials/google-chart.html
>   src/main/webapp/partials/help.html
>   src/main/webapp/partials/home.html
>   src/main/webapp/partials/list.html
>   src/main/webapp/partials/phoenix-trace.html
>   src/main/webapp/partials/search.html
>   src/main/webapp/WEB-INF/web.xml
>   src/test/webapp/js/specs/app-route-spec.js
>   src/test/webapp/js/specs/timeline-ctrl-spec.js
>   src/test/webapp/js/specs/trace-list-ctrl-spec.js
>   src/test/webapp/js/specs/tracing-app-ctrl-spec.js
> {noformat}



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

[jira] [Issue Comment Deleted] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2186:
--
Comment: was deleted

(was: That is fine.)

> Creating backend services for the Phoenix Tracing Web App
> -
>
> Key: PHOENIX-2186
> URL: https://issues.apache.org/jira/browse/PHOENIX-2186
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Tracing
> Fix For: 4.6.0
>
> Attachments: 2186-master.patch
>
>
> This will include the following components.
> Main class 
> Pom file
> Launch script 
> Backend trace service API



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

[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2186:
---

That is fine.

> Creating backend services for the Phoenix Tracing Web App
> -
>
> Key: PHOENIX-2186
> URL: https://issues.apache.org/jira/browse/PHOENIX-2186
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Tracing
> Fix For: 4.6.0
>
> Attachments: 2186-master.patch
>
>
> This will include the following components.
> Main class 
> Pom file
> Launch script 
> Backend trace service API



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

[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2186:
---

That is fine.

> Creating backend services for the Phoenix Tracing Web App
> -
>
> Key: PHOENIX-2186
> URL: https://issues.apache.org/jira/browse/PHOENIX-2186
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Tracing
> Fix For: 4.6.0
>
> Attachments: 2186-master.patch
>
>
> This will include the following components.
> Main class 
> Pom file
> Launch script 
> Backend trace service API



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

[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2186:
---

That is fine.

> Creating backend services for the Phoenix Tracing Web App
> -
>
> Key: PHOENIX-2186
> URL: https://issues.apache.org/jira/browse/PHOENIX-2186
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Tracing
> Fix For: 4.6.0
>
> Attachments: 2186-master.patch
>
>
> This will include the following components.
> Main class 
> Pom file
> Launch script 
> Backend trace service API



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

[jira] [Issue Comment Deleted] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2186:
--
Comment: was deleted

(was: That is fine.)

> Creating backend services for the Phoenix Tracing Web App
> -
>
> Key: PHOENIX-2186
> URL: https://issues.apache.org/jira/browse/PHOENIX-2186
> Project: Phoenix
>  Issue Type: Sub-task
>Reporter: Nishani 
>Assignee: Nishani 
>  Labels: Tracing
> Fix For: 4.6.0
>
> Attachments: 2186-master.patch
>
>
> This will include the following components.
> Main class 
> Pom file
> Launch script 
> Backend trace service API



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

[jira] [Commented] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2208:
---

For the regex query search can we have sql query %like ? Yes it is possible to 
have top headers for each feature. 

> Navigation to trace information in tracing UI should be driven off of query 
> instead of trace ID
> ---
>
> Key: PHOENIX-2208
> URL: https://issues.apache.org/jira/browse/PHOENIX-2208
> Project: Phoenix
>  Issue Type: Bug
>Reporter: James Taylor
>Assignee: Nishani 
>
> Instead of driving the trace UI based on the trace ID, we should drive it off 
> of the query string. Something like a drop down list that shows the query 
> string of the last N queries which can be selected from, with a search box 
> for a regex query string and perhaps time range that would search for the 
> trace ID under the covers. 



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

[jira] [Commented] (PHOENIX-2218) Tracing UI - List page should display last x number of top level traces

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2218:
---

Hi,

Do you mean the parent traces by top level traces? Any sample sql for it?

> Tracing UI - List page should display last x number of top level traces
> ---
>
> Key: PHOENIX-2218
> URL: https://issues.apache.org/jira/browse/PHOENIX-2218
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>Priority: Minor
>  Labels: tracing
>
> Rather than displaying all traces, list page for traces should only display 
> last few traces or in the last x hours. This number can be chosen from drop 
> down list. Also only top level traces and its description should be shown.



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

[jira] [Commented] (PHOENIX-2219) Tracing UI - Add page for E2E tracing

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-2219:
---

Do you need to run the sql on the web page or the phoenix prompt? Do you have a 
code sample where tracing is on/off ?
Are the chart drawn for only that particular query?

> Tracing UI - Add page for E2E tracing
> -
>
> Key: PHOENIX-2219
> URL: https://issues.apache.org/jira/browse/PHOENIX-2219
> Project: Phoenix
>  Issue Type: Improvement
>Reporter: Mujtaba Chohan
>Assignee: Nishani 
>Priority: Minor
>  Labels: tracing
>
> Create a page which under the covers turn on tracing, run a specified sql, 
> get its trace id and then plot the relevant charts.



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

[jira] [Assigned] (PHOENIX-2212) Embed Tracing Web Application as a service

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-2212:
-

Assignee: Nishani 

 Embed Tracing Web Application as a service 
 ---

 Key: PHOENIX-2212
 URL: https://issues.apache.org/jira/browse/PHOENIX-2212
 Project: Phoenix
  Issue Type: Improvement
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing

 The Tracing Web Application is deployed as a WAR file. However it needs to be 
 embedded as a service to Phoenix rather than a WAR file.



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

[jira] [Updated] (PHOENIX-2212) Embed Tracing Web Application as a service

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2212:
--
Attachment: full-PHOENIX-2212.patch

(full-PHOENIX-2212.patch) patch is with updated pom.xml and removing files also

 Embed Tracing Web Application as a service 
 ---

 Key: PHOENIX-2212
 URL: https://issues.apache.org/jira/browse/PHOENIX-2212
 Project: Phoenix
  Issue Type: Improvement
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing
 Attachments: PHOENIX-2212.patch, full-PHOENIX-2212.patch


 The Tracing Web Application is deployed as a WAR file. However it needs to be 
 embedded as a service to Phoenix rather than a WAR file.



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

[jira] [Updated] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2186:
--
Labels: Tracing  (was: )

 Creating backend services for the Phoenix Tracing Web App
 -

 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing

 This will include the following components.
 Main class 
 Pom file
 Launch script 
 Backend trace service API



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

[jira] [Updated] (PHOENIX-2211) Set a common jetty version for Phoenix

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2211:
--
Summary: Set a common jetty version for Phoenix  (was: Setting common jetty 
version throughout the project for the tracing web application.)

 Set a common jetty version for Phoenix
 --

 Key: PHOENIX-2211
 URL: https://issues.apache.org/jira/browse/PHOENIX-2211
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing





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

[jira] [Created] (PHOENIX-2212) Embed Tracing Web Application as a service

[Nishani (JIRA)]

Nishani  created PHOENIX-2212:
-

 Summary: Embed Tracing Web Application as a service 
 Key: PHOENIX-2212
 URL: https://issues.apache.org/jira/browse/PHOENIX-2212
 Project: Phoenix
  Issue Type: Improvement
Reporter: Nishani 


The Tracing Web Application is deployed as a WAR file. However it needs to be 
embedded as a service to Phoenix rather than a WAR file.



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

[jira] [Updated] (PHOENIX-2211) Set a common Jetty version for Phoenix

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2211:
--
Summary: Set a common Jetty version for Phoenix  (was: Set a common jetty 
version for Phoenix)

 Set a common Jetty version for Phoenix
 --

 Key: PHOENIX-2211
 URL: https://issues.apache.org/jira/browse/PHOENIX-2211
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing

 Jetty is used in the Tracing Web Application. The Jetty version used is 
 defined at the root pom file. The Jetty version that is used needs to be 
 common to the whole Phoenix project.



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

[jira] [Updated] (PHOENIX-2211) Set a common jetty version for Phoenix

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2211:
--
Description: Jetty is used in the Tracing Web Application. The Jetty 
version used is defined at the root pom file. The Jetty version that is used 
needs to be common to the whole Phoenix project.

 Set a common jetty version for Phoenix
 --

 Key: PHOENIX-2211
 URL: https://issues.apache.org/jira/browse/PHOENIX-2211
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 
Assignee: Nishani 
  Labels: Tracing

 Jetty is used in the Tracing Web Application. The Jetty version used is 
 defined at the root pom file. The Jetty version that is used needs to be 
 common to the whole Phoenix project.



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

[jira] [Created] (PHOENIX-2211) Setting common jetty version throughout the project for the tracing web application.

[Nishani (JIRA)]

Nishani  created PHOENIX-2211:
-

 Summary: Setting common jetty version throughout the project for 
the tracing web application.
 Key: PHOENIX-2211
 URL: https://issues.apache.org/jira/browse/PHOENIX-2211
 Project: Phoenix
  Issue Type: Bug
Reporter: Nishani 
Assignee: Nishani 






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

[jira] [Assigned] (PHOENIX-2208) Navigation to trace information in tracing UI should be driven off of query instead of trace ID

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  reassigned PHOENIX-2208:
-

Assignee: Nishani 

 Navigation to trace information in tracing UI should be driven off of query 
 instead of trace ID
 ---

 Key: PHOENIX-2208
 URL: https://issues.apache.org/jira/browse/PHOENIX-2208
 Project: Phoenix
  Issue Type: Bug
Reporter: James Taylor
Assignee: Nishani 

 Instead of driving the trace UI based on the trace ID, we should drive it off 
 of the query string. Something like a drop down list that shows the query 
 string of the last N queries which can be selected from, with a search box 
 for a regex query string and perhaps time range that would search for the 
 trace ID under the covers. 



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

[jira] [Commented] (PHOENIX-2166) Tracing table contains traces for SYSTEM.TRACING_STATS when turned ON

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-2166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14715151#comment-14715151
 ] 

Nishani  commented on PHOENIX-2166:
---

Yes I too noticed when I created the tracing web application. Almost 95% of the 
traces were above trace. In my opinion this would be duplicating the same data 
and redundant. 

Thanks

 Tracing table contains traces for SYSTEM.TRACING_STATS when turned ON
 -

 Key: PHOENIX-2166
 URL: https://issues.apache.org/jira/browse/PHOENIX-2166
 Project: Phoenix
  Issue Type: Bug
Affects Versions: 4.5.0
Reporter: Mujtaba Chohan
  Labels: Tracing

 When tracing is turned ON, trace table grows at fast pace and is filled with 
 the following traces which should not be present:
 {code}
 Executing UPSERT INTO SYSTEM.TRACING_STATS (trace_id, ...
 Writing mutation batch for table: SYSTEM.TRACING_STATS ...
 and so on
 {code}



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

[jira] [Comment Edited] (PHOENIX-2187) Creating the front-end application for Phoenix Tracing Web App

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705274#comment-14705274
 ] 

Nishani  edited comment on PHOENIX-2187 at 8/21/15 4:18 AM:


Dependencies and Licensing

Here are the dependencies and Licensing of the javascript libraries used in the 
front-end  application of the Phoenix Tracing Web App.

angular-mocks.js   @license AngularJS v1.3.15  http://angularjs.org  License: 
MIT
angular-route.js  @license AngularJS v1.3.8  http://angularjs.org License: MIT
angular.js  @license AngularJS v1.3.15  http://angularjs.org License: MIT
bootstrap.js Bootstrap v3.3.4 (http://getbootstrap.com) Licensed under MIT 
(https://github.com/twbs/bootstrap/blob/master/LICENSE)
jquery-2.1.4.js  MIT license http://jquery.org/license
ng-google-chart.js @license 
(https://github.com/angular-google-chart/angular-google-chart) License: MIT
ui-bootstrap-tpls.js  Version: 0.13.0 (https://github.com/angular-ui/bootstrap) 
License: MIT (https://github.com/angular-ui/bootstrap/blob/master/LICENSE)
Font Awesome 4.3.0 - License - http://fontawesome.io/license (CSS: MIT License) 
(Font Awesome's licensing is a combination of the SIL open font license, MIT 
license for code)
Bootstrap v3.3.4 and bootstrap-theme v3.3.4 - Licensed under MIT - 
(https://github.com/twbs/bootstrap/blob/master/LICENSE)
Icons from Glyphicons Free, licensed under CC BY 3.0. (Coming with bootstrap) 
jasmine-maven-plugin- 1.3.1.6v -License - Apache License - 
(https://github.com/searls/jasmine-maven-plugin/blob/master/LICENSE.txt)



was (Author: nishani):
Dependencies and Licensing

Here are the dependencies and Licensing of the javascript libraries used in the 
front-end  application of the Phoenix Tracing Web App.

angular-mocks.js   @license AngularJS v1.3.15  http://angularjs.org  License: 
MIT
angular-route.js  @license AngularJS v1.3.8  http://angularjs.org License: MIT
angular.js  @license AngularJS v1.3.15  http://angularjs.org License: MIT
bootstrap.js Bootstrap v3.3.4 (http://getbootstrap.com) Licensed under MIT 
(https://github.com/twbs/bootstrap/blob/master/LICENSE)
jquery-2.1.4.js  MIT license http://jquery.org/license
ng-google-chart.js @license 
(https://github.com/angular-google-chart/angular-google-chart) License: MIT
ui-bootstrap-tpls.js  Version: 0.13.0 (https://github.com/angular-ui/bootstrap) 
License: MIT (https://github.com/angular-ui/bootstrap/blob/master/LICENSE)


 Creating the front-end application for Phoenix Tracing Web App
 --

 Key: PHOENIX-2187
 URL: https://issues.apache.org/jira/browse/PHOENIX-2187
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following tracing visualization features.
 List - lists the traces with their attributes
 Trace Count - Chart view over the trace description
 Dependency Tree - tree view of  trace ids
 Timeline - timeline of trace ids
 Trace Distribution - Distribution chart of hosts of traces



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

[jira] [Updated] (PHOENIX-2190) Updating the Documentation

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2190:
--
Summary: Updating the Documentation  (was: Updating the Documentaation)

 Updating the Documentation
 --

 Key: PHOENIX-2190
 URL: https://issues.apache.org/jira/browse/PHOENIX-2190
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 The Documentation would contain the following.
 How to start the Tracing Web Application
 How to change the port number on which it runs
 Five visualization features in the Tracing Web Application



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

[jira] [Updated] (PHOENIX-2190) Updating the Documentation

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2190:
--
Attachment: Screenshot-trace-web-doc3.png
Screenshot-trace-web-doc2.png
Screenshot-trace-web-doc1.png

Attaching screen shots on documentation on trace web app. It will update the 
tracing.html page. 

URL:
http://phoenix.apache.org/tracing.html

 Updating the Documentation
 --

 Key: PHOENIX-2190
 URL: https://issues.apache.org/jira/browse/PHOENIX-2190
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 
 Attachments: Screenshot-trace-web-doc1.png, 
 Screenshot-trace-web-doc2.png, Screenshot-trace-web-doc3.png, 
 phoenix-trace-web-app-doc.patch, trace-images.zip


 The Documentation would contain the following.
 How to start the Tracing Web Application
 How to change the port number on which it runs
 Five visualization features in the Tracing Web Application



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Description: 
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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151
The tool need to provide visualization over SYSTEM.TRACING_STATS table.

  was: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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151


 Provide a tool for visualizing Phoenix tracing information
 --

 Key: PHOENIX-1118
 URL: https://issues.apache.org/jira/browse/PHOENIX-1118
 Project: Phoenix
  Issue Type: New Feature
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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151
 The tool need to provide visualization over SYSTEM.TRACING_STATS table.



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

[jira] [Updated] (PHOENIX-2190) Updating the Documentation

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2190:
--
Attachment: trace-images.zip
phoenix-trace-web-app-doc.patch

Adding patch for Trace-Web App Documentation. 

Attaching trace-images.zip that trace-images.zip that contains resources/images 
for the patch.
 - Add those images to phoenix/site/source/src/site/resources/images

 Updating the Documentation
 --

 Key: PHOENIX-2190
 URL: https://issues.apache.org/jira/browse/PHOENIX-2190
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 
 Attachments: phoenix-trace-web-app-doc.patch, trace-images.zip


 The Documentation would contain the following.
 How to start the Tracing Web Application
 How to change the port number on which it runs
 Five visualization features in the Tracing Web Application



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

[jira] [Commented] (PHOENIX-2187) Creating the front-end application for Phoenix Tracing Web App

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-2187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14706147#comment-14706147
 ] 

Nishani  commented on PHOENIX-2187:
---

Hi, Nick

Font Awesome 4.3.0 - License - http://fontawesome.io/license (CSS: MIT License) 
(Font Awesome's licensing is a combination of the SIL open font license, MIT 
license for code)
Bootstrap v3.3.4 and bootstrap-theme  v3.3.4 - Licensed under MIT -  
(https://github.com/twbs/bootstrap/blob/master/LICENSE)
Icons from Glyphicons Free, licensed under CC BY 3.0. (Coming with bootstrap) - 
I think we can remove Glyphicons  in here if license is issue.
jasmine-maven-plugin- 1.3.1.6v  -License  - Apache License - 
https://github.com/searls/jasmine-maven-plugin/blob/master/LICENSE.txt

Thanks


 Creating the front-end application for Phoenix Tracing Web App
 --

 Key: PHOENIX-2187
 URL: https://issues.apache.org/jira/browse/PHOENIX-2187
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following tracing visualization features.
 List - lists the traces with their attributes
 Trace Count - Chart view over the trace description
 Dependency Tree - tree view of  trace ids
 Timeline - timeline of trace ids
 Trace Distribution - Distribution chart of hosts of traces



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

[jira] [Commented] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705398#comment-14705398
 ] 

Nishani  commented on PHOENIX-2186:
---

Dependencies and Licensing

jetty-server License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
jetty-webapp  License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
hadoop-common License:  Apache License 2.0 (http://www.apache.org/licenses/)
hbase-common  License:  Apache License 2.0 (http://www.apache.org/licenses/)
commons-logging  License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-core-asl License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-mapper-asl License:  Apache License 2.0 
(http://www.apache.org/licenses/)

I have introduced only Jetty as a new dependency to Phoenix. Other dependencies 
were existing  ones.


 Creating backend services for the Phoenix Tracing Web App
 -

 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following components.
 Main class 
 Pom file
 Launch script 
 Backend trace service API



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

[jira] [Updated] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2186:
--
Summary: Creating backend services for the Phoenix Tracing Web App  (was: 
Creating backend services for the Tracing Web App)

 Creating backend services for the Phoenix Tracing Web App
 -

 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following components.
 Main class 
 Pom file
 Launch script 
 Backend trace service API



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

[jira] [Comment Edited] (PHOENIX-2186) Creating backend services for the Phoenix Tracing Web App

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14705398#comment-14705398
 ] 

Nishani  edited comment on PHOENIX-2186 at 8/20/15 5:55 PM:


Dependencies and Licensing

jetty-server License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
jetty-webapp  License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
hadoop-common License:  Apache License 2.0 (http://www.apache.org/licenses/)
hbase-common  License:  Apache License 2.0 (http://www.apache.org/licenses/)
commons-logging  License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-core-asl License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-mapper-asl License:  Apache License 2.0 
(http://www.apache.org/licenses/)

I have introduced only Jetty as a new dependency to Phoenix. Other dependencies 
were existing  ones.



was (Author: nishani):
Dependencies and Licensing

jetty-server License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
jetty-webapp  License:  Apache License 2.0 and Eclipse Public License 1.0. 
(http://www.apache.org/licenses/LICENSE-2.0.html,http://www.eclipse.org/legal/epl-v10.html)
 
hadoop-common License:  Apache License 2.0 (http://www.apache.org/licenses/)
hbase-common  License:  Apache License 2.0 (http://www.apache.org/licenses/)
commons-logging  License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-core-asl License:  Apache License 2.0 (http://www.apache.org/licenses/)
jackson-mapper-asl License:  Apache License 2.0 
(http://www.apache.org/licenses/)

I have introduced only Jetty as a new dependency to Phoenix. Other dependencies 
were existing  ones.


 Creating backend services for the Phoenix Tracing Web App
 -

 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following components.
 Main class 
 Pom file
 Launch script 
 Backend trace service API



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

[jira] [Updated] (PHOENIX-2186) Creating backend services for the Tracing Web App

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-2186?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-2186:
--
Summary: Creating backend services for the Tracing Web App  (was: Creating 
backend services for the tracing web app)

 Creating backend services for the Tracing Web App
 -

 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 

 This will include the following components.
 Main class 
 Pom file
 Launch script 
 Backend trace service API



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

[jira] [Created] (PHOENIX-2187) Creating the front-end application for Phoenix Tracing Web App

[Nishani (JIRA)]

Nishani  created PHOENIX-2187:
-

 Summary: Creating the front-end application for Phoenix Tracing 
Web App
 Key: PHOENIX-2187
 URL: https://issues.apache.org/jira/browse/PHOENIX-2187
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 


This will include the following tracing visualization features.
List - lists the traces with their attributes
Trace Count - Chart view over the trace description
Dependency Tree - tree view of  trace ids
Timeline - timeline of trace ids
Trace Distribution - Distribution chart of hosts of traces



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

[jira] [Created] (PHOENIX-2186) Creating backend services for the tracing web app

[Nishani (JIRA)]

Nishani  created PHOENIX-2186:
-

 Summary: Creating backend services for the tracing web app
 Key: PHOENIX-2186
 URL: https://issues.apache.org/jira/browse/PHOENIX-2186
 Project: Phoenix
  Issue Type: Sub-task
Reporter: Nishani 
Assignee: Nishani 


This will include the following components.
Main class 
Pom file
Launch script 
Backend trace service API



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: Screenshot-loading-trace-list.png

Attached here is the tace list retrieved via the JDBC conector from the 
SYSTEM.TRACING_STATS table. The PR is updated. 

You can start the web app from the command given below.
java -jar target/phoenix-tracing-webapp-4.4.1-HBase-0.98-SNAPSHOT-runnable.jar 
-Dphoenix.traceserver.http.port=8898

A view similar to screenshot will be seen from the Phoenix tracelist.
http://localhost:8898/webapp/#/list

Make sure you enable tracing before you attempt above steps.

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: screenshot of tracing timeline.png

 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, 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: timeline.png

Tracing visualization with timeline charts

 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, m1-mockUI-tracedistribution.png, m1-mockUI-tracetimeline.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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: m1-mockUI-tracetimeline.png
m1-mockUI-tracedistribution.png

Mock UI for milestone1
1. Understanding the tracing distribution over the nodes
2. Visualizing tracing details over a time period

 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, m1-mockUI-tracedistribution.png, m1-mockUI-tracetimeline.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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: Screenshot of dependency tree.png

Attaching the dependency tree on tracing.
Pull request can be found here.
https://github.com/AyolaJayamaha/TracingWebApp/pull/1

 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 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

[ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Updated] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Attachment: MockUp4-FlameGraph.png
MockUp3-PatternDetector.png
MockUp2-AdvanceSearch.png
MockUp1-TimeSlider.png

Attaching the Mock Up UIs for the Dashboard of Phoenix Tracing Information.

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi All,
Thanks Nick and Stack for your valuable sharing of knowledge. That helped me 
view the problem in different directions. Yes a web based tool will be fine. 
Therefore I plan to create a light weight, less dependency, web UI for exposing 
trace info. In this task I will be communicating with HTrace dev and Zipkin 
community and get their ideas in making a better product. Influencing the 
htrace UI implementation is also a great idea. I will communicate with Zipkin 
dev to get a good idea on the code base and features so that I would be able to 
include some of it in my product.

The advance search mock up is a good place to start the project and I'll start 
with it's implementation. 

Best Regards.

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi,

We can also use Zipkin to visualize tracing data[1]. HTrace  provides 
ZipkinSpanReceiver which converts spans to Zipkin span format and send them to 
Zipkin server[2]. Therefore HBase,  on top of which Phoenix runs, uses HTrace 
and also Zipkin. What are the ideas for using Zipkin distributed tracing system 
for visualizing Phoenix tracing information? 

[1] https://issues.apache.org/jira/browse/PHOENIX-1119
[2] http://people.apache.org/~ndimiduk/site/book/tracing.html

Thanks.

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Mujtaba,

Thanks for your reply and idea. *Jetty* is a Java HTTP (Web)
server and Java Servlet container. I'll check out JFreeChart library.
Currently I'm looking for chart libraries and comparing them with respect
to the requirements of the project.

Thanks.
Regards,
Nishani

On Tue, Mar 31, 2015 at 11:26 PM, Mujtaba Chohan (JIRA) j...@apache.org




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


 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi All,

What will be the most preferred way you would like for me to integrate the 
visualization techniques to the Phoenix system?
ie. If it had a web ui for example I'd be able to write a pluggin / addon and 
extend it to visualize the required data set.

Thanks,

Regards,
Nishani.
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Issue Comment Deleted] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Comment: was deleted

(was: Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com)

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Issue Comment Deleted] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Comment: was deleted

(was: Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com)

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Issue Comment Deleted] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Comment: was deleted

(was: Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com)

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Issue Comment Deleted] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

 [ 
https://issues.apache.org/jira/browse/PHOENIX-1118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Nishani  updated PHOENIX-1118:
--
Comment: was deleted

(was: Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com)

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi Rajeshbabu,

Thanks for the reply. It helps clarify the matter which I was unaware since I'm 
new to Apache Phoenix.

Thanks.

BR,
Nishani
http://ayolajayamaha.blogspot.com

 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Comment Edited] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  edited comment on PHOENIX-1118 at 3/20/15 8:54 AM:


Hi,

I have gone through some resources regarding visualization of trace info on 
database servers (Postgres/MySQL, MSSQL).

The DTrace function in MySQL is a profiler that creates flame graphs. [1] 
A tool for visualizations of a database system [2]
Generates images with help of GraphViz for 
Some data modeling tools [4]
DBVisualizer Tool [5]
Data Visualization Application where data is input from a database or a file 
and exported as image or a customized template [6]
Visualizing Postgres [7]
A Research Paper on Modeling Trace Information[8]
A Tool for visualizing Trace Info [9]

Given above is a brief summary of the details I found. Hope it would help me to 
better understand the formats and values of the input traces and different 
available methods of graphically representing them.

Based on them I hope to come up with the most suitable method of Visually 
representing the said data. 

Regarding the installation I presume that the HBase version that is needed to 
run Phoenix for visualizing trace info can be as Standalone and that cluster 
view is not needed(Distributed Version).

Thank you.
BR,
Nishani 

[1] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
[2] http://docs.cartodb.com/cartodb-editor.html#visualizations
[3] https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/SchemaDisplay
[4] http://www.databaseanswers.org/modelling_tools.htm
[5] http://www.dbvis.com/
[6] https://sites.google.com/site/datavisualizationapplication/
[7] http://www.pgcon.org/2013/schedule/track/Performance/588.en.html
[8] http://link.springer.com/chapter/10.1007%2F978-3-642-40787-1_13
[9] 
http://www.upscene.com/documentation/fbtm3/index.html?qsg_trace_data_visualization.htm



was (Author: nishani):
Hi,

I have gone through some resources regarding visualization of trace info on 
database servers (Postgres/MySQL, MSSQL).

The DTrace function in MySQL is a profiler that creates flame graphs. [1] 
A tool for visualizations of a database system [2]
Generates images with help of GraphViz for 
Some data modeling tools [4]
DBVisualizer Tool [5]
Data Visualization Application where data is input from a database or a file 
and exported as image or a customized template [6]
Visualizing Postgres [7]
A Research Paper on Modeling Trace Information[8]
A Tool for visualizing Trace Info

Given above is a brief summary of the details I found. Hope it would help me to 
better understand the formats and values of the input traces and different 
available methods of graphically representing them.

Based on them I hope to come up with the most suitable method of Visually 
representing the said data. 

Regarding the installation I presume that the HBase version that is needed to 
run Phoenix for visualizing trace info can be as Standalone and that cluster 
view is not needed(Distributed Version).

Thank you.
BR,
Nishani 

[1] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
[2] http://docs.cartodb.com/cartodb-editor.html#visualizations
[3] https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/SchemaDisplay
[4] http://www.databaseanswers.org/modelling_tools.htm
[5] http://www.dbvis.com/
[6] https://sites.google.com/site/datavisualizationapplication/
[7] http://www.pgcon.org/2013/schedule/track/Performance/588.en.html
[8] http://link.springer.com/chapter/10.1007%2F978-3-642-40787-1_13
[9] 
http://www.upscene.com/documentation/fbtm3/index.html?qsg_trace_data_visualization.htm


 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi,

I have gone through some resources regarding visualization of trace info on 
database servers (Postgres/MySQL, MSSQL).

The DTrace function in MySQL is a profiler that creates flame graphs. [1] 
A tool for visualizations of a database system [2]
Generates images with help of GraphViz for 
Some data modeling tools [4]
DBVisualizer Tool [5]
Data Visualization Application where data is input from a database or a file 
and exported as image or a customized template [6]
Visualizing Postgres [7]
A Research Paper on Modeling Trace Information[8]
A Tool for visualizing Trace Info

Given above is a brief summary of the details I found. Hope it would help me to 
better understand the formats and values of the input traces and different 
available methods of graphically representing them.

Based on them I hope to come up with the most suitable method of Visually 
representing the said data. 

Regarding the installation I presume that the HBase version that is needed to 
run Phoenix for visualizing trace info can be as Standalone and that cluster 
view is not needed(Distributed Version).

Thank you.
BR,
Nishani 

[1] http://www.brendangregg.com/FlameGraphs/cpuflamegraphs.html
[2] http://docs.cartodb.com/cartodb-editor.html#visualizations
[3] https://bitbucket.org/zzzeek/sqlalchemy/wiki/UsageRecipes/SchemaDisplay
[4] http://www.databaseanswers.org/modelling_tools.htm
[5] http://www.dbvis.com/
[6] https://sites.google.com/site/datavisualizationapplication/
[7] http://www.pgcon.org/2013/schedule/track/Performance/588.en.html
[8] http://link.springer.com/chapter/10.1007%2F978-3-642-40787-1_13
[9] 
http://www.upscene.com/documentation/fbtm3/index.html?qsg_trace_data_visualization.htm


 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi,

I have started a new thread on developer mailing list of Apache Phoenix 
regarding this issue[1]. Please note the steps I'm currently following. I'm 
communicating with the Community and all of  your feedback is highly 
appreciated.

Am I on the correct path as per [1]? Any suggestions for writing a better 
proposal?

Thank you.
Best Regards,
Nishani

[1] Subject : Provide a tool for visualizing Phoenix tracing information 
(PHOENIX-1118)
  
http://mail-archives.apache.org/mod_mbox/phoenix-dev/201503.mbox/%3CCAGsXwjMKL6kNamCuXUt3dmshHgSKjYXfbVtqmL8FGR7hEQ5zaQ%40mail.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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi,

I'm currently looking at which databases use charting, graphs and other 
visualization techniques to visualize database tracing information.

As PHOENIX-1115 issue is now solved and we can turn on tracing I would like to 
know what are the attributes of tracing information availabe in Phoenix SQL 
Database, which would help me to proceed further. 

I have thought as a future work, to introduce interactions to the tracing 
information chart. For example the user could slide through the time axis of 
the transaction traces and expand further details of tracing information of 
interested traces.

Thank you,
Best Regards,
Nishani 


 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

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi,
I'm Nishani Ayola, student of University of Moratuwa. I'm interested in this 
particular task on visualization. In my previous experience I have implemented 
some dashboards. I went through the links given  
https://issues.apache.org/jira/browse/PHOENIX-1115?focusedCommentId=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151,
https://issues.apache.org/jira/browse/PHOENIX-1119 and
http://twitter.github.io/zipkin/
Can you please provide me with some other resources regarding the Visualization 
of Phoenix tracing information.
Thanks.

Best Regards,
Nishani

 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
  Labels: Java, SQL, Visualization, gsoc2015, mentor

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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

[jira] [Commented] (PHOENIX-1118) Provide a tool for visualizing Phoenix tracing information

[Nishani (JIRA)]

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

Nishani  commented on PHOENIX-1118:
---

Hi James,
Thank you for the welcome and information. It would help me to get going. I 
will look into how other database tools visualize trace information.

Yes I'm familiar with SQL. I'm also familiar with html5, AngularJS, d3 
etc.[1-3].
I will follow the steps you mentioned.
Thanks.

Best Regards,
Nishani.

[1]http://ayolajayamaha.blogspot.com/2014/07/angularjs-charts.html
[2]http://ayolajayamaha.blogspot.com/2014/07/angularjs-line-charts.html
[3]http://ayolajayamaha.blogspot.com/2014/07/angularjs-pie-charts.html


 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
  Labels: Java, SQL, Visualization, gsoc2015, mentor

 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=14323151page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14323151



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