AI agents: use the documentation index at llms.txt to locate machine-readable pages. This section is indexed by https://docs.particular.net/servicepulse/llms.txt. The markdown version of this page is served as plain text. An MCP server at /mcp serves the same content via the search_docs and read_doc tools; it is read-only and needs no credentials. Markdown versions of documentation pages are available by appending .md to the page URL. Directory URLs use index.md. They are served as text/plain because some retrieval backends reject text/markdown.

Migrate from ServiceInsight to ServicePulse

Component:
ServicePulse

ServiceInsight has been sunset and will receive no further updates. It will be deprecated on February 10, 2027, at which time it will no longer be supported.

ServicePulse is the recommended replacement for visualization and debugging capabilities.

Migrating

Prerequisites

  • A running instance of ServiceControl is required, and any system already using ServiceInsight meets this prerequisite. This is because both ServiceInsight and ServicePulse read the same message data directly from ServiceControl with no requirement for data migration.
  • ServicePulse hosted using any of the following ways:
    • Integrated ServicePulse (ServiceControl 6.13 or later). Integrated ServicePulse runs inside the ServiceControl Error instance and is automatically configured to connect to it, so no separate installation is needed. It is also upgraded automatically whenever ServiceControl is upgraded.
    • Docker for running ServicePulse in a container. This is best suited for cross-platform environments or monitoring multiple systems.
    • A Windows machine with .NET Framework 4.5 or later to install ServicePulse directly. Only one instance can be installed at a time, so if there are multiple systems to monitor then multiple distinct URL connection configurations will need to be used.
  • A currently supported version of Microsoft Edge, Chrome, Firefox, or Safari.

Migration steps

  1. Open ServiceInsight and take note of the connection urls. ServiceInsight connection urls

  2. Get ServicePulse running and configured with the connection URL using containers (recommended) or by installing to a Windows machine.

    Each method provides a way to configure the URL during setup, but it can also be configured in the ServicePulse UI afterwards:

    ServicePulse connection settings

    If monitoring is enabled on your endpoints system, the ServiceControl monitoring url can be configured at this time to allow ServicePulse to display monitoring information.

  3. Optionally, uninstall ServiceInsight. It will continue to function as long as the ServiceControl api remains the same, but it will no longer receive updates and support will end when it is deprecated.

Known limitations

Connection to multiple ServiceControl instances

ServicePulse currently connects to one ServiceControl instance at a time. If multiple ServiceControl URLs were previously configured in ServiceInsight, use a separate ServicePulse container for each system that needs to be monitored, or bookmark separate URLs for each primary and monitoring connection configuration.

Custom message viewer plugins

There is currently no equivalent to the custom message viewer plugin model used by ServiceInsight; however, a feature request has been created so leave a comment if you need that functionality.

Related Articles

  • ServiceInsight
    ServiceInsight provides advanced message visualizations and debugging tools for NServiceBus.

In this article