Just wanted to get a feel out there if anyone has been using the Webservicemon probe. Anyone have any success using it or find significant value in it? Seems to be pretty powerful but not sure of the best way to use it at this point.
Could anybody assist in defining the pros and cons of webservicemon versus url_response?
Am I the only one who's used this?
If your company runs webservices, then this is very valuable. they are very difficult to monitor using URL_Response, and if you know the required values (wsdl url, enpoint, etc ... ) then this makes monitoring webservices much easier and more reliable.
Think i clicked on the solved button on this tread.. oops.. Anyway, my perspective to the pros and cons of this probe is that if you have a specific web service, you can test the various methods of that service and test things such as response time of a given method, alarm on values put out by it. I suppose it really depends on the method use in the service, but it can be pretty powerful. The real benfit I see is being able to excercise the service. You can call the wsdl or just the url of a service using the url_response probe, but that only tells you if the url is hosting a page. It's not really excersing it. For us, one of the cons to this probe is having to work with each app team to identify a method to test against. It would be nice if each web service had a standard monitoring method to use. Also, the url_response probe has been relatively easy to configure and set up for some basic simple tests. That's where it shines.. Webservicemon is a bit more time consuming to set up tho.
the use cases for url_response and webservicemon are different, as chris said above.
Often webservices have some rather simple queries you can make to identify that they are operational.
Retrieving data ...