<commit_before>= Alert notifiers for mobile devices
<NAME>
2015-04-14
:jbake-type: post
:jbake-status: draft
:jbake-tags: blog, alerts, mobile, SMS, Aerogear
:idprefix:
:linkattrs:

Hawkular Alerts has new notifications senders which target mobile devices. Let's start with a brief explanation of
notification sending.

== How notification senders work?

When the alert engine detects a problem, it sends an action message to the configured sender(s) for this type of issue.
The action message has all the details:

* which problem triggered the alert
* who are the configured recipients

[[img-action-plugins]]
.Action plugins overview
ifndef::env-github[]
image::/img/blog/2015/alert-action-plugins.png[Action plugins overview,600,align="center"]
endif::[]
ifdef::env-github[]
image::../../../../assets/img/alert-action-plugins.png[Action plugins overview,600,align="center"]
endif::[]

. The alert engine inspects notification data to determine which action messages should be sent to the Hawkular bus.
. Then it sends a message for each configured notification (email/SMS/push).
. Action plugins pick up their messages and build the notification with the details given in the notification message.

Makes sense? Now which new plugins do we have?

=== Unified Push Notifications

Hawkular Alert's `areogear` plugin is able to send notification messages to
https://www.jboss.org/unifiedpush/[Aerogear's Unified Push Server]. Which means that you can send alerts as native push
messages to an Android, iOS, Windows or Firefox OS application.

At the time of writing, Hawkular doesn't have a mobile application for any of these platforms (an Android application
might come soon with the help of a Google Summer of Code student). So for demonstration purposes we've built a sample
application, `Hawkugear` and ran it with the Android Emulator.

[[img-action-plugins]]
.Hawkugear Android application
ifndef::env-github[]
image::/img/blog/2015/hawkugear-android-app.png[Hawkugear Android application,350,align="center"]
endif::[]
ifdef::env-github[]
image::../../../../assets/img/hawkugear-android-app.png[Hawkugear Android application,350,align="center"]
endif::[]

The application lacks proper formatting of course, but you can see on this screenshot that the notification message
landed properly on the mobile device after travelling through the Hawkular Bus, the Aerogear Unified Push Server and
Google Cloud's Messaging platform.

=== Short Message Service

There's also an `sms` plugin which is built on https://www.twilio.com/sms[Twilio's SMS services]. No mobile application
required here, all you need to do is to create a Twilio account and configure the plugin with your application `sid`,
authorization `token`, and `from` number.

=== More to come...

We have planned to integrate with http://www.pagerduty.com/[PagerDuty]. In the beginning, each notification message
will be sent with a new indentifier. As a consequence, PagerDuty will see recurrent notifications of the same problem
as different incidents. The Hawkular Alerts team is working on an incident worflow and we should be able to solve this
problem in the near future.

That's it! Questions? Comments? Feel free to ask here or join in `#hawkular` channel on Freenode!<commit_msg>Add IRC link<commit_after>= Alert notifiers for mobile devices
<NAME>
2015-04-14
:jbake-type: post
:jbake-status: draft
:jbake-tags: blog, alerts, mobile, SMS, Aerogear
:idprefix:
:linkattrs:

Hawkular Alerts has new notifications senders which target mobile devices. Let's start with a brief explanation of
notification sending.

== How notification senders work?

When the alert engine detects a problem, it sends an action message to the configured sender(s) for this type of issue.
The action message has all the details:

* which problem triggered the alert
* who are the configured recipients

[[img-action-plugins]]
.Action plugins overview
ifndef::env-github[]
image::/img/blog/2015/alert-action-plugins.png[Action plugins overview,600,align="center"]
endif::[]
ifdef::env-github[]
image::../../../../assets/img/alert-action-plugins.png[Action plugins overview,600,align="center"]
endif::[]

. The alert engine inspects notification data to determine which action messages should be sent to the Hawkular bus.
. Then it sends a message for each configured notification (email/SMS/push).
. Action plugins pick up their messages and build the notification with the details given in the notification message.

Makes sense? Now which new plugins do we have?

=== Unified Push Notifications

Hawkular Alert's `areogear` plugin is able to send notification messages to
https://www.jboss.org/unifiedpush/[Aerogear's Unified Push Server]. Which means that you can send alerts as native push
messages to an Android, iOS, Windows or Firefox OS application.

At the time of writing, Hawkular doesn't have a mobile application for any of these platforms (an Android application
might come soon with the help of a Google Summer of Code student). So for demonstration purposes we've built a sample
application, `Hawkugear` and ran it with the Android Emulator.

[[img-action-plugins]]
.Hawkugear Android application
ifndef::env-github[]
image::/img/blog/2015/hawkugear-android-app.png[Hawkugear Android application,350,align="center"]
endif::[]
ifdef::env-github[]
image::../../../../assets/img/hawkugear-android-app.png[Hawkugear Android application,350,align="center"]
endif::[]

The application lacks proper formatting of course, but you can see on this screenshot that the notification message
landed properly on the mobile device after travelling through the Hawkular Bus, the Aerogear Unified Push Server and
Google Cloud's Messaging platform.

=== Short Message Service

There's also an `sms` plugin which is built on https://www.twilio.com/sms[Twilio's SMS services]. No mobile application
required here, all you need to do is to create a Twilio account and configure the plugin with your application `sid`,
authorization `token`, and `from` number.

=== More to come...

We have planned to integrate with http://www.pagerduty.com/[PagerDuty]. In the beginning, each notification message
will be sent with a new indentifier. As a consequence, PagerDuty will see recurrent notifications of the same problem
as different incidents. The Hawkular Alerts team is working on an incident worflow and we should be able to solve this
problem in the near future.

That's it! Questions? Comments? Feel free to ask here or irc://irc.freenode.net/#hawkular[join us on Freenode]!
{'fraction_non_alphanumeric': 0.08436876821598405, 'fraction_numerical': 0.008590274581991103, 'mean_word_length': 4.992647058823529, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 5, 'https://': 4, 'lorem ipsum': 0, 'www.': 6, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2279907', 'n_tokens_mistral': 1810, 'n_tokens_neox': 1681, 'n_words': 823}