You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@phoenix.apache.org by "Nishani (JIRA)" <ji...@apache.org> on 2015/10/01 20:23:26 UTC
[jira] [Assigned] (PHOENIX-1519) Determine the usefulness of
tracing
[ 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)