[jira] [Commented] (AMBARI-15241) Basic Operational Audit Logging

["Sebastian Toader (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMBARI-15241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15218707#comment-15218707 ] 

Sebastian Toader commented on AMBARI-15241:
-------------------------------------------

Committed to trunk:

{code}
commit 46a34ccdeeeeabe0ad4172e94a63c9b077e17861
Author: Toader, Sebastian <st...@hortonworks.com>
Date:   Wed Mar 30 20:02:27 2016 +0200

    AMBARI-15241. Basic Operational Audit Logging. (Daniel Gergely via stoader)
{code}

> Basic Operational Audit Logging
> -------------------------------
>
>                 Key: AMBARI-15241
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15241
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>            Reporter: Sebastian Toader
>            Assignee: Daniel Gergely
>            Priority: Critical
>             Fix For: 2.4.0
>
>         Attachments: AMBARI-15241.v2.patch
>
>
> Ambari should audit operational events (including user, timestamp, etc) such as: start, stop, restart, move, add/delete service, add/delete component, enable/disable kerberos, enter/leave maintenance mode, create/edit/enable/disable alerts. This should also include user/group role changes (including Ambari Admin flag).
> This information should be available in an operational log.
> When an operation is executed in Ambari, append an entry to a history log showing:
> The timestamp is when the operation is started
> The user is the logged in user
> The operation is what is currently displayed in the operations UI
> The success/fail is what is displayed in the UI when the operation is completed
> Comment is an optional field the user can supply



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)