This article will show how to deploy a simple monitoring application in the Cloud in a couple of minutes using statusdashboard and Heroku.
I already introduced StatusDashboardseveral months ago with a small websocket client I wrote allowing to connect to the web application and streaming monitoring data directly in the terminal. The monitoring data is produced by the server which is periodically trying to call a set of defined services (HTTP, HTTPs, FTP, TCP, UDP, …).
In the last version, you can now embed StatusDashboard in any node application with a really simple to use API. This is especially nice to customize it for your needs, for example, getting settings from a configuration file, from a remote service or whatever:
Let’s deploy it on Heroku…
There is one problem with the current approach: When running such an application on Heroku with the default Heroku Plan, it will ends when nobody browse it. This will stop the monitoring loop which is not really useful for a monitoring app… In order to avoid such behavior, I added a heartbeat mechanism last night which is configured from the application settings. It also needs to define some environment variable with the heroku client. Let’s assume that your application is running on http://YOURAPP.herokuapp.com, you have to define this variable like:
It will restart your application (if not, restart it manually), will start to ping itself and keep the application alive.
One more video of a talk I gave at OW2Con 2012 about a research project I am working on since two years now called Play (and not the play framework…).
« The PLAY project develops an elastic and reliable architecture for dynamic and complex, event-driven interaction in large highly distributed and heterogeneous service systems.
Such an architecture will enable ubiquitous exchange of information between heterogeneous services, providing the possibilities to adapt and personalize their execution, resulting in the so-called situational-driven process adaptivity… »
Here is the video of a quick talk I gave two weeks ago at OW2Con 2012 dealing with Petals Enterprise Service Bus.
He gives some background about what is Petals, how it can be used, why it is a distributed runtime, what is really new in the last version and finally what is planned in the next version.
I already spent many time explaining what we have in mind to push Petals in the cloud and this will be a reality in the next months as we are currently working on that exiting feature. More information soon, for real this time!
While trying to find one free hour to give some feedback on OW2Con 2012, here are my slides from two talks I gave last week in Paris.
First talk was about what’s new in the last version of Petals Enterprise Service Bus? The session also covered what is Petals ESB, what it provides and where it goes.
One other talk was about what we are currently developing in the Play research project. The difficulty was to give a quick view of this HUGE event-driven platform. More details are coming soon on http://play.ow2.org (yes, Play platform is now an OW2 project).
I also participated to a talk called ‘Dev 2.0 at OW2’ with @sauthieg and @clementplop in which we introduced the new ways to develop using the OW2 tools and all this so-called social stuff every software forge now provides.
Coming back soon with feedback on several other talks, and some other OW2-related news.
You are right, I need to smile more, be less tired and have a demo of the BPM editor working on low resolution displays… BTW, the demo of the DSB Monitoring & Management console used to deploy and monitor BPEL process works.