WCF服务监控应该使用什么?WMI 或 WS-Discovery [英] What should be used for WCF service monitoring ? WMI or WS-Discovery

查看:27
本文介绍了WCF服务监控应该使用什么?WMI 或 WS-Discovery的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您能说出哪个是监视 WCF 服务、WMI 或 WS-Discovery 实现的最佳工具吗?

Can you tell that which is the best tool to monitor WCF services, WMI or WS-Discovery implementation.

推荐答案

要求看起来很简单,但实际上很难.服务可能可用,但操作可能会失败,反之亦然.还有很多潜在的问题:网络故障、池/服务主机停止、wcf 激活失败、操作错误……一个服务可以使用但由于数据库损坏而导致所有操作失败.WMI/Perf 计数器似乎是一种很好的方法,因为您可以拥有不同范围(服务/操作/端点)的许多详细信息.但另外,如果您在 IIS 下托管您的服务,应用程序池空闲默认超时为 20 分钟:计数器/WMI 将不可用.

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.

这篇关于WCF服务监控应该使用什么?WMI 或 WS-Discovery的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆