Monitor your web services using luntbuild and soapui

Monitor your web services using luntbuild

Halt: Due to the fact that luntbuild stops building after a couple of builds, you should consider the post “Monitor your web services using CruiseControl” instead. Meanwhile, monitor this luntbuild-bug, if you prefer luntbuild as scheduler.

In a SOA system some service providers could be implemented as web services. Proactive monitoring of these web services will give a top-down approach to monitoring the overall system as seen from a service consumer, and give early warning on response times, downtime etc.
This would be useful in a production environment, as well as in a test and development setting. Be aware that proactive monitoring is causing additional load, but the information you get from it is extremely valuable. You could act on incidents, instead of reacting to errors.

soapui and luntbuild

But a lightweight and cheap initial solution would be to combine soapui tests, and luntbuild. If you don’t use SoapUI,and are working on web services, well you should start using it. SoapUI can be used for functional testing, loadtesting, mocking, monitoring etc. The capabilities of SoapUI are combined with a continuous integration tool (scheduler and notification) for a complete web service monitoring solution.

There is no need to give a full detail of configuration here, only say that of the continuous integration tools, luntbuild has no initial cost when it comes to configuration. You could of course also use Hudson, CruiseControl, Anthill or Continuum. But for this specific scheduled execution of web service request execution luntbuild is the fastest to configure. There is detailed documentation on the SoapUI site on how to combine soapUI projects with Luntbuild for surveillance testing. See SoapUI documentation on automated web service testing.

After installing Luntbuild, follow the steps in this microsoft article (Create your own user-defined services Windows NT/2000/XP/2003) to get Luntbuild as a system service.
02.11.2009 , 19_49_16

Example of proactive web service monitoring

Then it is a matter of configuring Luntbuild. And this is really the easy part. You will have proactive monitoring up and running in 30 min!

02.11.2009 , 19_44_01

02.11.2009 , 19_44_44

02.11.2009 , 19_45_55

And notifications when webservice fails, with easy access to the full request-response cycle, including errors.

02.11.2009 , 19_47_50

now that the infrastructure for proactive monitoring is set up, it can of course be used for scheduled load testing, for automated web service testing on code repository commits, etc.

But actually, to me, the most useful part is the proactive monitoring of the active production system.


Martin Fowler on continuous integration
Test-driven development in an SOA environment
Passive vs. Active Monitoring
Create your own user-defined services Windows NT/2000/XP/2003
SoapUI documentation on automated web service testing (surveillance testing)

Comment are closed.