在ASP.NET健康监测的理解心跳 [英] Understanding heartbeat in ASP.NET health monitoring

问题描述

谁触发事件？是什么使得它在＆LT的后果/效益;启用healthMonitoring =真heartbeatInterval =30＆GT; ，除了它出现在日志中每30秒？它有什么关系NLB心跳？什么时间间隔是在生产中使用好？

Who's triggering the event? What are consequences/benefits of enabling it in <healthMonitoring enabled="true" heartbeatInterval="30"> except it appears every 30 seconds in the logs? Has it anything to do with NLB heartbeat? What interval is better for production use?

推荐答案

在web.config中启用它以这种方式会导致应用程序域养 WebHeartbeatEvent 定期（在你的情况下，每30秒），基本上检查，如果你的应用是还活着（如检查人类的心跳）。您可以指定这样的附加规则：

Enabling it in this way in the web.config will cause the Application Domain to raise a WebHeartbeatEvent periodically (in your case every 30 seconds), basically to check if your application is 'still alive' (like checking a human's heartbeat). You can specify additional rules like this:

<healthMonitoring enabled="true" heartbeatInterval="100">
  <rules>
    <add name="Heart Beat Events"
      eventName="Heartbeats"
      provider="EventLogProvider"
      profile="Default"
      minInterval="00:01:00" />
  </rules>
</healthMonitoring>

指定 EventLogProvider '将导致事件记录到事件日志，但你也可以编写自己的供应商，的在这里看到。

Specifying 'EventLogProvider' will cause the events to be logged to the EventLog, but you could also write your own Provider, see here.

它无关的方式，它仅用于负载均衡的目的NLB心跳。

It has nothing to do with the NLB heartbeat by the way, which is only used for Load Balancing purposes.

这篇关于在ASP.NET健康监测的理解心跳的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！