Return-Path: X-Original-To: apmail-accumulo-notifications-archive@minotaur.apache.org Delivered-To: apmail-accumulo-notifications-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F484182AB for ; Thu, 6 Aug 2015 21:14:15 +0000 (UTC) Received: (qmail 79123 invoked by uid 500); 6 Aug 2015 21:14:08 -0000 Delivered-To: apmail-accumulo-notifications-archive@accumulo.apache.org Received: (qmail 79054 invoked by uid 500); 6 Aug 2015 21:14:08 -0000 Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jira@apache.org Delivered-To: mailing list notifications@accumulo.apache.org Received: (qmail 78765 invoked by uid 99); 6 Aug 2015 21:14:07 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Aug 2015 21:14:07 +0000 Date: Thu, 6 Aug 2015 21:14:07 +0000 (UTC) From: "James Mello (JIRA)" To: notifications@accumulo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ACCUMULO-3946) Not all accumulo events are audited for Audit logging MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ACCUMULO-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14660802#comment-14660802 ] James Mello commented on ACCUMULO-3946: --------------------------------------- So looking at the code it appears that rolling up things into a single audit event is going to be difficult. I can take the MasterRepo classes that are executed by Fate and instrument the steps. But because this appears to be a chain of command pattern there is no one event that I can use in the Fate execution calls to say that an operation is done. For the termination of the chain I can mention success, but for intermediate failures I won't be able to. For example the flow for a create table CreateTable -> SetupPermissions -> PopulateZookeeper -> CreateDir -> PopulateMetadata -> FinishCreateTable I suppose since these classes are imperatively tied to each other I can log the start (CreateTable) and the end (FinishCreateTable) for a successful create. And for the intermediate steps log that table creation failed during one of the other operations. Does this sound good? > Not all accumulo events are audited for Audit logging > ----------------------------------------------------- > > Key: ACCUMULO-3946 > URL: https://issues.apache.org/jira/browse/ACCUMULO-3946 > Project: Accumulo > Issue Type: Bug > Affects Versions: 1.5.3 > Reporter: James Mello > Assignee: James Mello > Fix For: 1.5.4 > > > Currently accumulo does not log all the major events such as table creation and permissions changes. Please modify the existing logging to include missing auditing. Note this is related to ticket ACCUMUO-3939. -- This message was sent by Atlassian JIRA (v6.3.4#6332)