[
https://issues.apache.org/jira/browse/CASSANDRA-13001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Murukesh Mohanan updated CASSANDRA-13001:
-----------------------------------------
Assignee: Murukesh Mohanan
Fix Version/s: 4.0
Status: Patch Available (was: Open)
In this patch, I add three new configuration options in {{cassandra.yaml}} to
decide how slow queries are logged:
- {{slow_query_log_methods}} - a string of space-separated logging methods
({{log}}, {{command}} and {{table}}).
1. {{log}} is what's already happening,
2. {{command}} will run an external command and send JSON-encoded
slow-query data to its input. The script I wrote for CASSANDRA-13000 can be a
consumer here. A script can parse the JSON and send data to external servers.
3. {{table}} will save the entries to a specified Cassandra table
- {{slow_query_log_command}} - an array of strings, specifying the path to the
command and any arguments
- {{slow_query_log_table}} - the table where the queries should be logged (in
{{keyspace.table}} format)
Multiple methods can be specified.
> 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)
