[
https://issues.apache.org/jira/browse/PHOENIX-2218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14943897#comment-14943897
]
Mujtaba Chohan commented on PHOENIX-2218:
-----------------------------------------
Yes only the top level traces as otherwise there is just too much information
in listview. Sql you can use can be of the following format {code}SELECT
TRACE_ID, PARENT_ID, SPAN_ID, START_TIME, END_TIME, DESCRIPTION FROM
SYSTEM.TRACING_STATS WHERE PARENT_ID IN (SELECT SPAN_ID FROM
SYSTEM.TRACING_STATS WHERE PARENT_ID=477902) ORDER BY START_TIME DESC;
{code} which would display all top level traces generated by turning sql _trace
on_ statement.
It would be great if you can also add a UI element to clear out
SYSTEM.TRACING_STATS table as it can grow to a rather large size and degrade
overall UI performance by issuing {code}DELETE FROM SYSTEM.TRACING_STATS;{code}
> 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)
