<html><head>
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
</head><body bgcolor="#FFFFFF" text="#000000"><br>
<br>
<blockquote style="border: 0px none;"
cite="mid:54D4B0DA.90202@redhat.com" type="cite">
<div style="margin:30px 25px 10px 25px;" class="__pbConvHr"><div
style="display:table;width:100%;border-top:1px solid
#EDEEF0;padding-top:5px"> <div
style="display:table-cell;vertical-align:middle;padding-right:6px;"><img
photoaddress="tsegismo@redhat.com" photoname="Thomas Segismont"
src="cid:part1.01090203.09060205@redhat.com"
name="compose-unknown-contact.jpg" height="25px" width="25px"></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;width:100%">
<a moz-do-not-send="true" href="mailto:tsegismo@redhat.com"
style="color:#737F92
!important;padding-right:6px;font-weight:bold;text-decoration:none
!important;">Thomas Segismont</a></div> <div
style="display:table-cell;white-space:nowrap;vertical-align:middle;">
<font color="#9FA2A5"><span style="padding-left:6px">February 6, 2015
at 7:17 AM</span></font></div></div></div>
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody"><div>Hi,<br><br>I've
been thinking about the alert notification system lately.<br><br>What's
the information needed to send a notification?<br>How to convert the
information into text when a human is the recipient? <br>How to
configure the system?<br>How to make it fit into the Hawkular suite?<br><br>1.
Contextual data<br><br>A notification has contextual data. Contextual
data is comprised of:<br>- alert definition data<br>- data involved in
the trigger (for example metrics and availability values)<br></div></div>
</blockquote>
Many times there are symptoms of a problem that are seen through
alerts. If there are many alerts happening around the same trigger
time, should we be adding pointers to other potentially related alerts
to help users diagnose the root cause faster?<br>
<blockquote style="border: 0px none;"
cite="mid:54D4B0DA.90202@redhat.com" type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div><br>2. Notifier data<br><br>2.1 Who is the recipient?<br><br>Email:
address<br>SMS: phone number<br><br>Sometimes the recipient is fixed
(for example when sending email to a <br>mailing-list).<br>Sometimes it
should be picked from user information (for example when <br>sending
emails to a group of users)<br><br>This information depends on the alert
definition, but a default should <br>be configurable for convenience.<br></div>
</div>
</blockquote>
Are we considering alert escalation? Setting up a list that the alerts
go to by default, and then if they are not resolved by some configurable
SLA, they are then sent to another group of people to raise the
awareness of the problem?<br>
<blockquote style="border: 0px none;"
cite="mid:54D4B0DA.90202@redhat.com" type="cite">
<div style="color: rgb(136, 136, 136); margin-left: 24px;
margin-right: 24px;" __pbrmquotes="true" class="__pbConvBody">
<div><br>2.2 How should the message be sent?<br><br>Email: SMTP
address/port and credentials<br>SMS: Web service HTTP URL and
credentials<br><br>The information depends on the tenant (in rare cases,
on the alert <br>definition, but let's ignore the problem for now)<br><br>3.
How should the message be formatted?<br><br>When a human is the
recipient, information can be turned into text with <br>a template
engine (like freemarker).<br><br>Information depends on the alert
definition, but a default should be <br>configurable for convenience.<br></div>
</div>
</blockquote>
Can we do full HTML format (maybe txt vs. HTML configurable). It would
be nice to add links directly into the web console for that resource
that alerted so users can very quickly click through to investigate the
problem.<br>
<blockquote style="border: 0px none;"
cite="mid:54D4B0DA.90202@redhat.com" type="cite">
<div style="color:#888888;margin-left:24px;margin-right:24px;"
__pbrmquotes="true" class="__pbConvBody">
<div><br>4. Configuration<br><br>Notifiers may expose REST endpoints
(with standardized URIs)<br><br>- default config:
/emailnotifier/configuration<br><br>- alert definition level config:
/emailnotifier/configuration/1<br><br>Example:<br><br>{<br> "to":
[<a class="moz-txt-link-rfc2396E" href="mailto:paul@foobar.com">"paul@foobar.com"</a>, <a class="moz-txt-link-rfc2396E" href="mailto:alfred@foobar.com">"alfred@foobar.com"</a>],<br> "cc":
[<a class="moz-txt-link-rfc2396E" href="mailto:backoffice-mw-ops@foobar.com">"backoffice-mw-ops@foobar.com"</a>],<br> "subject": "Pool soon
exhausted",<br> "mode": "plaintext+html"<br> "templates":<br>
[{<br> name: "plaintext",<br> uri:
"/emailnotifier/configuration/1/templates/plaintext"<br> },{<br>
name: "html",<br> uri:
"/emailnotifier/configuration/1/templates/html"<br> }]<br>}<br><br>-
template configs:<br><br>Example:<br><br>/emailnotifier/configuration/1/templates/plaintext<br>/emailnotifier/configuration/1/templates/html<br><br><br>I'm
still not sure which component should be responsible of loading user <br>information
when a user (or a group of users) is selected as the recipient.<br><br>5.
Process<br><br>- Alerts sends contextual data on the bus<br>- Notifier
picks it up<br>- Notifier loads configuration for this alert definition
or the default one<br>- Notifier applies the template (optional)<br>-
Notifier sends email or invoke sender API<br><br>6. Storage<br><br>There
needs to be some shared storage where to bind configuration and <br>templates
to alert definitions.<br><br><br>Comments?<br><br>Regards,<br>Thomas<br>_______________________________________________<br>hawkular-dev
mailing list<br><a class="moz-txt-link-abbreviated" href="mailto:hawkular-dev@lists.jboss.org">hawkular-dev@lists.jboss.org</a><br><a class="moz-txt-link-freetext" href="https://lists.jboss.org/mailman/listinfo/hawkular-dev">https://lists.jboss.org/mailman/listinfo/hawkular-dev</a><br></div>
</div>
</blockquote>
<br>
<div class="moz-signature">-- <br>Catherine Robson<br>
User Experience Design<br>
Red Hat JBoss Middleware<br>
c: 978-944-3825<br>
<br>
</div>
</body></html>