Can you tell that which is the best tool to monitor WCF services, WMI or WS-Discovery implementation.
相关问题
- How to Debug/Register a Permanent WMI Event Which
- How to make a .svc file write to asp.net Trace.axd
- WCF Service Using Client Certificates Requires Ano
- WCF error with net.tcp "The service endpoint faile
- WCF Service Reference Support Files Not Updating
相关文章
- WCF发布Windows服务 POST方式报错 GET方式没有问题 应该怎么解决?
- XCopy or MOVE do not work when a WCF Service runs
- Could not find default endpoint element that refer
- The 'DbProviderFactories' section can only
- Do I need to expose a constructor in a WCF DataCon
- exposing net.tcp endpoint
- When is destructor called in a WCF service
- Getting error detail from WCF REST
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.