使用C＃.NET 3.5分布式监测服务 [英] Distributed Monitoring Service using C# .NET 3.5

问题描述

让我们说，例如，你必须使用相同的平台（基于Windows）全部写自己的网络服务5个不同的公司，有什么用C＃和.NET 3.5，你会建议使用监视所有的不​​同的Web服务技术？

我的目的是要建立一个按需提供视觉反馈的服务状态。当然网站管理员和电子邮件/短信通知的应用程序。是否有一个最佳实践或方法在您看来可循？

此外，是否有任何基于Windows的工具，可用来执行这一点，我不知道了吗？ preferrably开源？

*编辑：认为最终的结果，那只是表明旁边横跨不同公司运行服务红灯或绿灯的应用程序

。

公司1
     > Web服务1  - 绿色
     > Web服务2  - 绿色
公司2
     > Web服务1  - 红
     > Web服务2  - 绿色

解决方案

您应该尝试PolyMon，在codePLEX一个基于.NET的，开放源码的监测工具： HTTP：//polymon.$c$cplex.com/

至少对于我们而言，它击中了最佳点的功能和清晰而简单的设置。

您可以从出的现成的有些像平或URL监测任务选择，但你也可以很容易地实现自己的更复杂的任务。能够很好地适合我们。

该工具本身不散发，但你可以很容易地设置服务的两个实例（例如，在不同地点的服务器）和监控相同的服务，或者用一个实例来监视对方。

我们刚刚经历了一个问题，这是很烦人的，有点古怪，当被同时运行PolyMon一台服务器，并使用PolyMon SQL Server实例反复坠毁，机上重新启动（重新启动的无限循环）。似乎是某种形式的竞争状态。因此，我强烈建议主办PolyMon服务，并在不同的（虚拟）机SQL Server服务，或设置PolyMon服务的启动类型为手动，而不是自动，并经过手工一切引导启动PolyMon ，为了避免这个问题。

Let's say for example you have 5 different companies using the same platform (Windows based) all wrote their own web services, what technique using C# and .Net 3.5 would you recommend using to monitor all their different web services?

My intention is to build an application that provides visual feedback on service statuses to site administrators and of course e-mail/sms alerts as needed. Is there a best practice or methodology to follow in your opinion?

In addition, are there any windows based tools available to perform this that I'm unaware off? Preferrably open-source?

*Edit: Think of the end result, an application that just shows a red or green light next to the services running across the different companies.

Company 1
     > Web Service 1 - Green
     > Web Service 2 - Green
Company 2
     > Web Service 1 - Red
     > Web Service 2 - Green

解决方案

You should try PolyMon, a .NET based, open-source monitoring tool on CodePlex: http://polymon.codeplex.com/

At least for our case, it hit the sweet-spot of functionality and a lean and easy setup.

You can choose from some out-of-the-box tasks like Ping or URL monitoring, but you can also easily implement your own more complex tasks. Works quite well for us.

The tool itself is not distributed, but you can easily set up two instances of the service (e. g. on servers in different locations) and monitor the same services, or use one instance to monitor the other.

We experienced just one issue that was very annoying and a little freaky, when a server that was running both PolyMon and the SQL Server instance used by PolyMon repeatedly crashed on reboots (endless loop of reboot). Seems to be some kind of race condition. Therefore I strongly recommend to host the PolyMon service and the SQL Server service on different (virtual) machines, or set the start-up type of the PolyMon service to "Manual" instead of "Automatic", and start PolyMon manually after everything else booted, to avoid this problem.

这篇关于使用C＃.NET 3.5分布式监测服务的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！