Particular Service Platform - Mastering NServiceBus and Persistence - page 72

We will be using the ScaleOut-ServiceControl solution. This solution is similar to an
earlier chapter's example, except that there we added service control plugins through
NuGet to generate service control endpoints for monitoring purposes:
• ServiceControl.Plugin.DebugSession : This is found at https://www.nuget.org/
packages/ServiceControl.Plugin.DebugSession/ . When deployed, the debug ses-
sion plugin adds a specified debug session identifier to the header of each mes-
sage sent by the endpoint. This allows messages sent by debugging or a test run
within Visual Studio to be correlated, filtered, and highlighted within Ser-
viceInsight.
• ServiceControl.Plugin.CustomChecks : This is found at https://www.nuget.org/
packages/ServiceControl.Plugin.CustomChecks . The result of a custom check is
either a success or a failure (with a detailed description defined by the developer).
This result is sent as a message to the ServiceControl queue.
• ServiceControl.Plugin.Heartbeat : This is found at https://www.nuget.org/pack-
ages/ServiceControl.Plugin.Heartbeat . The heartbeat plugin sends heartbeat mes-
sages from the endpoint to the ServiceControl queue. These messages are sent
every 10 seconds (by default).
• ServiceControl.Plugin.SagaAudit : This is found at https://www.nuget.org/pack-
ages/ServiceControl.Plugin.SagaAudit . The Saga Audit plugin collects the activ-
ity information of a saga runtime. This information enables the display of detailed
saga data, behaviors, and the current status in ServiceInsight Saga View. The plu-
gin sends the relevant saga state information as messages to the ServiceControl
queue whenever a saga state changes.
ServiceControl normally runs through the URL at http://localhost:33333/api .
If the ServiceControl screen does not come up correctly, you may want to check to see
whether the Particular.ServiceControl Windows service has started. Ser-