ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (AMBARI-10249) Add a Log Appender for Alert State Change Events
Date Fri, 27 Mar 2015 20:38:53 GMT

     [ https://issues.apache.org/jira/browse/AMBARI-10249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Hurley resolved AMBARI-10249.
--------------------------------------
    Resolution: Fixed

> Add a Log Appender for Alert State Change Events
> ------------------------------------------------
>
>                 Key: AMBARI-10249
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10249
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>             Fix For: 2.1.0
>
>
> Currently there is no permanent audit trail for alert state change events. Although the
history and notifications of an alert are kept in the database, a deletion of the alert definition
will cascade to its children, thus removing the history. 
> Similar to {{ambari.config-changes.file}}, create a new logger that logs the following
information:
> - Alert state changed events
> -- date, state, name, threshold values (if any), text, instance, label
> {code}
> ambari.alert-state-changes.file=ambari-alert-state-changes.log
> # Log config changes
> log4j.logger.alerts=INFO,alerts
> log4j.additivity.alerts=false
> log4j.appender.alerts=org.apache.log4j.FileAppender
> log4j.appender.alerts.File=${ambari.log.dir}/${ambari.alert-state-changes.file}
> log4j.appender.alerts.layout=org.apache.log4j.PatternLayout
> log4j.appender.alerts.layout.ConversionPattern=%d{ISO8601} %5p - %m%n
> private static final Logger alertLogger = LoggerFactory.getLogger("alerts");
> {code}



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

Mime
View raw message