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 4ABF9200B62 for ; Thu, 28 Jul 2016 15:40:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 495A2160A85; Thu, 28 Jul 2016 13:40:22 +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 91238160A56 for ; Thu, 28 Jul 2016 15:40:21 +0200 (CEST) Received: (qmail 44792 invoked by uid 500); 28 Jul 2016 13:40:20 -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 44769 invoked by uid 99); 28 Jul 2016 13:40:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 28 Jul 2016 13:40:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 851932C0D60 for ; Thu, 28 Jul 2016 13:40:20 +0000 (UTC) Date: Thu, 28 Jul 2016 13:40:20 +0000 (UTC) From: "Jonathan Ellis (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-12151) Audit logging for database activity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 28 Jul 2016 13:40:22 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-12151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397542#comment-15397542 ] Jonathan Ellis commented on CASSANDRA-12151: -------------------------------------------- Can we back up a little and talk about design? Some questions in my mind: # Do we want a global audit log, or server-local? If the former (easier for users to query), it should go in system_distributed keyspace; otherwise just in system (higher performance). # Is there a use case where you'd want to log every query? That seems like it would entail a prohibitive performance penalty. I would think most users would be better served by logging meta-changes (adding roles, altering tables, etc) > Audit logging for database activity > ----------------------------------- > > Key: CASSANDRA-12151 > URL: https://issues.apache.org/jira/browse/CASSANDRA-12151 > Project: Cassandra > Issue Type: New Feature > Reporter: stefan setyadi > Fix For: 3.x > > Attachments: 12151.txt > > > we would like a way to enable cassandra to log database activity being done on our server. > It should show username, remote address, timestamp, action type, keyspace, column family, and the query statement. > it should also be able to log connection attempt and changes to the user/roles. > I was thinking of making a new keyspace and insert an entry for every activity that occurs. > Then It would be possible to query for specific activity or a query targeting a specific keyspace and column family. -- This message was sent by Atlassian JIRA (v6.3.4#6332)