[AMBARI-10249] Add a Log Appender for Alert State Change Events

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Component/s: ambari-server
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 27/Mar/15 17:28
• Updated: 28/Mar/15 04:03
• Resolved: 27/Mar/15 20:38

Description

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

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");

Issue Links

• links to: Reviewboard