Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id E5F65200C3E for ; Tue, 7 Mar 2017 03:05:37 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id E4A9B160B76; Tue, 7 Mar 2017 02:05:37 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3954A160B81 for ; Tue, 7 Mar 2017 03:05:37 +0100 (CET) Received: (qmail 49047 invoked by uid 500); 7 Mar 2017 02:05:36 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 49036 invoked by uid 99); 7 Mar 2017 02:05:36 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Mar 2017 02:05:36 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id EB5201AA96E for ; Tue, 7 Mar 2017 02:05:35 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.347 X-Spam-Level: X-Spam-Status: No, score=-2.347 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-2.999, SPF_NEUTRAL=0.652] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id oiiF13ICdc_K for ; Tue, 7 Mar 2017 02:05:35 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 02AE15F624 for ; Tue, 7 Mar 2017 02:05:35 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C59ACE08DE for ; Tue, 7 Mar 2017 02:05:33 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E158624174 for ; Tue, 7 Mar 2017 02:05:32 +0000 (UTC) Date: Tue, 7 Mar 2017 02:05:32 +0000 (UTC) From: "Murukesh Mohanan (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-13001) pluggable slow query logging / handling MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 07 Mar 2017 02:05:38 -0000 [ 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)