Su Ralph created EAGLE-369:
------------------------------

             Summary: Improve eagle alert email template to provide more useful 
information and user experience
                 Key: EAGLE-369
                 URL: https://issues.apache.org/jira/browse/EAGLE-369
             Project: Eagle
          Issue Type: Improvement
    Affects Versions: v0.3.1
            Reporter: Su Ralph
            Assignee: Su Ralph
             Fix For: v0.5.0


>From feedback:

(1)     Time Stamp needs to be human readable. 
(2)     Consider capitalize wordings.
(3)     What does lowNum and highNum mean here?  Do they mean number of live 
data nodes?  How does this alert come out?  Does that mean the current number 
of live data nodes go above the highNum or below the lowNum?  The lowNum should 
display as “2,884” instead of “2884.0”.  
(4)     The Description field should always be there.  If description is not 
available, it should display as “Not provided by Policy Owner”.
(5)     Should we consider displaying the name of the policy owner?  That way, 
people know whom to contact if they have question about the policy.
(6)     The information in the Actions Required field is too generic and it is 
not actionable.  Can we do something about it?
(7)     The text alignment (now always align center) may consider to align 
left.  Use want to make it look more professional.
(8)     Text font is not consistent across the message.  Should align to one 
single font.  Consider use Calibri as this is now the eBay official font type.  
(9)     Lack of policy definition
The definition is 
from every (e1 = hadoopJmxMetricEventStream[metric == 
\"hadoop.namenode.fsnamesystemstate.numlivedatanodes\" ]) -> e2 = 
hadoopJmxMetricEventStream[metric == e1.metric and host == e1.host and 
(convert(e1.value, \"long\") - 2) >= convert(value, \"long\") ] within 5 min 
select e1.metric, e1.host, e1.value as highNum, e1.timestamp as start, e2.value 
as lowNum, e2.timestamp as end insert into tmp;
 






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

Reply via email to