[
https://issues.apache.org/jira/browse/CASSANDRA-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murukesh Mohanan updated CASSANDRA-13001:
-----------------------------------------
Attachment: 0001-Add-basic-pluggable-logging-to-debug.log-and-table.patch
Jon, can you go over the new patch and see if I'm headed in the right direction
this time?
Essentially:
- a new interface {{o.a.c.db.monitoring.IQueryLogger}}, with one function
{{void logQueries(MonitoringTask.AggregatedOperations operations,
MonitoringTask.OperationType type, long elapsed)}}, accordingly, various
elements in {{MonitoringTask}} have been made {{public}}
- Two classes implementing it, {{o.a.c.d.m.QueryDebugLogger}} and
{{{{o.a.c.d.m.QueryTableLogger}}. The former implements the current
{{debug.log}} behaviour and is default, and the latter saves stats and metadata
to a table (hard-coded to {{perf.slow_log}}, looking for better ideas on this).
- New configuration setting {{slow_query_logger}}, works like {{authenticator}}.
- Rolled up both timed out and slow operation logging in {{MonitoringTask}} to
use the interface. Accordingly cleaned up {{MonitoringTask}}. Perhaps the
configuration setting should be renamed, again looking for ideas.
The patch is far from ready, but ...
> pluggable slow query logging / handling
> ---------------------------------------
>
> Key: CASSANDRA-13001
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13001
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Jon Haddad
> Assignee: Murukesh Mohanan
> Fix For: 4.0
>
> Attachments:
> 0001-Add-basic-pluggable-logging-to-debug.log-and-table.patch,
> 0001-Add-multiple-logging-methods-for-slow-queries-CASSAN.patch
>
>
> Currently CASSANDRA-12403 logs slow queries as DEBUG to a file. It would be
> better to have this as an interface which we can log to alternative
> locations, such as to a table on the cluster or to a remote location (statsd,
> graphite, etc).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
