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

Jayesh resolved EAGLE-815.
--------------------------
    Resolution: Fixed

> Support alert template to generate human readable alert 
> --------------------------------------------------------
>
>                 Key: EAGLE-815
>                 URL: https://issues.apache.org/jira/browse/EAGLE-815
>             Project: Eagle
>          Issue Type: New Feature
>    Affects Versions: v0.5.0
>            Reporter: Hao Chen
>            Assignee: Hao Chen
>             Fix For: v0.5.0
>
>         Attachments: alert.PNG, policy_editor.png
>
>
> Support alert template to generate human readable message 
> * [done] Support to define alert template in PolicyDefinition
> * [done] Support to generate alert event (subject&body, instead of using 
> AlertPublishEvent for less changes) based on policy'template and alert event 
> as context
> * [done] Dynamically load policy metadata in alert publisher
> * [done] Integration VelocityAlertTemplateEngine in alertPublisherBolt with 
> metadata lifecycle
> * [done] Support persist alert message in AlertEntity as immutable field.
> * [done] Refactor alert mail template using 
> https://github.com/mailgun/transactional-email-templates
> * Refactor Alert Template to become simple and human-readable.
> * Add Alert Category
> * Add Alert Severity (notification template color will change according to 
> different severiy): UNKNOWN (blue), OK(green), WARNING (orange), 
> CRITICAL/FATAL (dark black)
> * Add Alert Subject &Body Template Engine, for example: 
>     * Sample Subject “RESOURCEMANAGER JMX Metric Alert” is defined by 
> “$component.toUpperCase() JMX Metric Alert”
>     * Sample Body is defined as “A alert happened on 
> <strong>$component</strong> (<strong>$host</strong>) of cluster 
> <strong>$site</strong> at <strong>$ALERT_TIME</strong> because <span 
> style="color: red">$metric = $value</span>”



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to