Alert notifiers for mobile devices

A blog post by Thomas Segismont

Aerogear | alerts | mobile | SMS

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

Action plugins overview
Figure 1. Action plugins overview
  1. The alert engine inspects notification data to determine which action messages should be sent to the Hawkular bus.

  2. Then it sends a message for each configured notification (email/SMS/push).

  3. 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 aerogear plugin is able to send notification messages to 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.

Hawkugear Android application
Figure 2. Hawkugear Android application

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.

To configure the aerogear sender plugin, add these system property definitions (with your own values) into your Wildfly standalone.xml file:

    <property name="org.hawkular.actions.aerogear.root.server.url" value="http://localhost:9191/ag-push/"/>
    <property name="" value="as304-6019-8a256afkbc-935b274-16247"/>
    <property name="org.hawkular.actions.aerogear.master.secret" value="94b2-qc156s-719725j6-4k04d566-bs0a340"/>

Or using the CLI:


Short Message Service

There’s also an sms plugin which is built on 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.

As for the aerogear plugin, add these system property definitions (with your own values) into your Wildfly standalone.xml file:

    <property name="org.hawkular.actions.sms.sid" value="ACdc5f132a3c49700934481addd5ce1659"/>
    <property name="org.hawkular.actions.sms.token" value="3036d49cAf5Cd019c81de12354d57ac49a"/>
    <property name="org.hawkular.actions.sms.from" value="+14158141829"/>

Or using the CLI:


More to come…​

We have planned to integrate with 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 us on Freenode!

Published by Thomas Segismont on 09 April 2015


© 2016 | Hawkular is released under Apache License v2.0