[
https://issues.apache.org/jira/browse/CASSANDRA-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15898600#comment-15898600
]
Murukesh Mohanan commented on CASSANDRA-13001:
----------------------------------------------
{{MonitoringTask}} also logs timed-out queries using pretty much identical code
as that used for slow queries. Does it make sense to move both of them to the
same (pluggable) logging method? If so, do I pass something like a {{Type:
"slow"}} or {{Type: "time-out"}} to the method doing the logging?
> 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-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)
