<p>By default, Dashboard middleware will not be launched. To enable Dashboard functionality you need to add the following code to your configuration:</p>
<p>This configuration item is used to configure the authorization filter when accessing the Dashboard. The default filter allows LAN access. When your application wants to provide external network access, you can customize the authentication rules by setting this configuration. See the next section for details.</p>
<p>在 CAP 中，对 <codeclass="codehilite">DiagnosticSource</code> 提供了支持，监听器名称为 <codeclass="codehilite">CapDiagnosticListener</code>。</p>
<p>Diagnostics 提供对外提供的事件信息有：</p>
<p>Diagnostics provides a set of features that make it easy for us to document the critical operations that occur during the application's operation, their execution time, etc., allowing administrators to find the root cause of problems, especially in production environments.</p>
<p>The CAP provides support for <codeclass="codehilite">DiagnosticSource</code> with a listener name of <codeclass="codehilite">CapDiagnosticListener</code>.</p>
<p>Diagnostics provides external event information as follows:</p>
<ul>
<li>消息持久化之前</li>
<li>消息持久化之后</li>
<li>消息持久化异常</li>
<li>消息向MQ发送之前</li>
<li>消息向MQ发送之后</li>
<li>消息向MQ发送异常</li>
<li>消息从MQ消费保存之前</li>
<li>消息从MQ消费保存之后</li>
<li>订阅者方法执行之前</li>
<li>订阅者方法执行之后</li>
<li>订阅者方法执行异常</li>
<li>Before the message is persisted</li>
<li>After the message is persisted</li>
<li>Message persistence exception</li>
<li>Before the message is sent to MQ</li>
<li>After the message is sent to MQ</li>
<li>The message sends an exception to MQ.</li>
<li>Messages saved from MQ consumption before saving</li>
<li>After the message is saved from MQ consumption</li>
<ahref="https://github.com/dotnetcore/CAP/edit/master/docs/content/user-guide/en/monitoring/health-checks.md"title="Edit this page"class="md-icon md-content__icon"></a>
<p>Persistent storage of memory messages is often used in development and test environments, and if you use memory-based storage you lose the reliability of local transaction messages.</p>
<p>For a quick development of the MongoDB 4.0+ cluster for the development environment, you can refer to <ahref="https://www.cnblogs.com/savorboard/p/mongodb-4-cluster-install.html">this article</a>.</p>
<p>Then you can add memory-based configuration items to the <codeclass="codehilite">ConfigureServices</code> method of <codeclass="codehilite">Startup.cs</code>.</p>
<p>In Memory Queue is a memory-based message queue provided by <ahref="https://github.com/yang-xiaodong/Savorboard.CAP.InMemoryMessageQueue">Community</a>.</p>
Then you can add memory-based configuration items to the <codeclass="codehilite">ConfigureServices</code> method of <codeclass="codehilite">Startup.cs</code>.</p>
<p>Then you can add memory-based configuration items to the <codeclass="codehilite">ConfigureServices</code> method of <codeclass="codehilite">Startup.cs</code>.</p>
