Can you tell that which is the best tool to monitor WCF services, WMI or WS-Discovery implementation.
Asked
Active
Viewed 865 times
0
-
Hi, what kind of monitoring? timings, errors, is running, ..? – Cybermaxs Sep 06 '12 at 13:35
-
specifically status of the service whether available or not – Milan Raval Sep 07 '12 at 05:07
1 Answers
1
The requirements look easy, but in fact it's quite difficult. Service may be available but operations may fails and vice-versa. There are also many potential problems : network failure, pool/service host stopped, wcf activation fails, operation errors... A service can be available but all operations fails because of a corrupt database. WMI/Perf counters seems to be a good approach as you can have many details for different scopes (service/operation/endpoint). But In addition if your hosting your service under IIS, application pool idle default timeout is 20 minutes: counters/WMI will be unavailable.
In conclusion, i would said that the best monitoring strategy is an agregation of all tools/components available to server side and to client side.
Cybermaxs
- 24,378
- 8
- 83
- 112
-
any limitations of WS-Discovery if it is used for discovery and service status? – Milan Raval Sep 07 '12 at 07:23
-
WCF services hosted under IIS or WAS do not run until IIS/WAS receives a message bound for the service, so they cannot be discoverable by default. You have to use AppFabric Auto-Start feature. As i said, your service can be up, but all your operations may fails. In py opinion, it is not enough for monitoring. – Cybermaxs Sep 07 '12 at 07:43