[
https://issues.apache.org/jira/browse/PHOENIX-2715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15170670#comment-15170670
]
James Taylor commented on PHOENIX-2715:
---------------------------------------
Good point about the gap if sampling is on with tracing, [~apurtell].
Client-side metrics alone doesn't solve this either, but I neglected to mention
how we get at this information today at SFDC. We use client-side metrics to
gather a bunch of useful metrics and produce a log line per statement
(including the text of the SQL). Then we use Splunk to produce dashboards that
show aggregated and summarized information across all use cases for the
cluster. But without something like Spunk, there's a gap, so this JIRA would
indeed fill that.
> Query Log
> ---------
>
> Key: PHOENIX-2715
> URL: https://issues.apache.org/jira/browse/PHOENIX-2715
> Project: Phoenix
> Issue Type: New Feature
> Reporter: Nick Dimiduk
>
> One useful feature of other database systems is the query log. It allows the
> DBA to review the queries run, who's run them, time taken, &c. This serves
> both as an audit and also as a source of "ground truth" for performance
> optimization. For instance, which columns should be indexed. It may also
> serve as the foundation for automated performance recommendations/actions.
> What queries are being run is the first piece. Have this data tied into
> tracing results and perhaps client-side metrics (PHOENIX-1819) becomes very
> useful.
> This might take the form of clients writing data to a new system table, but
> other implementation suggestions are welcome.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
