diff --git a/README.md b/README.md index 1fe63e84dd0..21d9212cacc 100644 --- a/README.md +++ b/README.md @@ -224,14 +224,14 @@ Calls to action are defined in `calls-to-action.yaml`. ### An example header for an article -In the following example, whenever the URLs `/servicecontrol/sc-si` or `/servicecontrol/debugging-servicecontrol` are being requested, the given article will be rendered. +In the following example, whenever the URLs `/servicecontrol/sc-sp` or `/servicecontrol/debugging-servicecontrol` are being requested, the given article will be rendered. ```yaml --- -title: ServiceInsight Interaction -summary: 'Using ServiceInsight Together' +title: ServicePulse Interaction +summary: 'Using ServicePulse Together' redirects: -- servicecontrol/sc-si +- servicecontrol/sc-sp - servicecontrol/debugging-servicecontrol related: - servicecontrol/installation diff --git a/home.md b/home.md index 2678676fa95..2cd8896c8b1 100644 --- a/home.md +++ b/home.md @@ -121,19 +121,19 @@ span.blue { margin-top: 30px; } -.products .col-xs-12.col-md-4 { +.products .col-xs-12.col-md-6 { padding: 0; } -.products .col-xs-12.col-md-4:nth-child(2) { - padding: 0 15px; +.products .col-xs-12.col-md-6:nth-child(2) { + padding: 0 0 0 15px; } -.products .col-xs-12.col-md-4 ul { +.products .col-xs-12.col-md-6 ul { padding-left: 15px; } -.products .col-xs-12.col-md-4 ul a { +.products .col-xs-12.col-md-6 ul a { color: rgb(0, 114, 156); font-weight: bold; } @@ -265,29 +265,7 @@ span.blue {
-
-
- ServiceInsight -
-
-
-

-

Complete under-the-hood visualization of a system's behavior

-

- -

All ServiceInsight articles


-
-
-
- Release notes -
-
- - -
+
ServiceControl
@@ -311,14 +289,14 @@ span.blue { -
+
ServicePulse

-

Real-time monitoring that is custom tailored to fit a distributed systems

+

Real-time monitoring with complete under-the-hood visualization of a distributed system's behavior

  • Monitoring Endpoints
    • diff --git a/platform/architecture-overview.png b/platform/architecture-overview.png index ff345d38d55..fac24ad1500 100644 Binary files a/platform/architecture-overview.png and b/platform/architecture-overview.png differ diff --git a/platform/index.md b/platform/index.md index 81551dd92f5..74ac9541e9b 100644 --- a/platform/index.md +++ b/platform/index.md @@ -11,11 +11,11 @@ Messaging is a great way to build loosely coupled, scalable, and reliable system The Platform's goal is to provide a set of tools that make it easier to build and maintain messaging systems. The tools are tailored to the common needs of messaging systems and 'just work', out of the box. They enable developers to focus on more important challenges, such as gaining a better understanding of their business domains. -The Particular Service Platform consists of [NServiceBus](/nservicebus), [ServiceControl](/servicecontrol), [ServicePulse](/servicepulse), and [ServiceInsight](/serviceinsight). +The Particular Service Platform consists of [NServiceBus](/nservicebus), [ServiceControl](/servicecontrol), and [ServicePulse](/servicepulse). ![Particular Service Platform architecture](architecture-overview.png) -The details of each component are discussed below. A Particular Service Platform-based system consists of several NServiceBus [endpoints](/nservicebus/endpoints/). Endpoints are logical entities that perform business operations. They communicate with each other using messages (via queues) and forward messages to ServiceControl for auditing. ServiceControl stores this audit trail and provides integration points for ServicePulse and ServiceInsight. ServicePulse provides monitoring and recoverability for production systems. ServiceInsight and ServicePulse provide debugging information and visualization of how the system works. +The details of each component are discussed below. A Particular Service Platform-based system consists of several NServiceBus [endpoints](/nservicebus/endpoints/). Endpoints are logical entities that perform business operations. They communicate with each other using messages (via queues) and forward messages to ServiceControl for auditing. ServiceControl stores this audit trail and provides integration points for ServicePulse. ServicePulse provides monitoring and recoverability for production systems. ServicePulse provides debugging information and visualization of how the system works. ## [NServiceBus](/nservicebus) - where it all begins @@ -25,16 +25,12 @@ include: nservicebus include: servicecontrol -## [ServicePulse](/servicepulse) - debug, retry and monitor +## [ServicePulse](/servicepulse) - debug, retry, monitor and visualize include: servicepulse -## [ServiceInsight](/serviceinsight) - visualization - -include: serviceinsight - ## Working with the platform -ServiceControl and ServicePulse are server applications. They should be deployed in each environment, for example: test, QA, and production. ServiceInsight is a client application. It should be deployed on a workstation and connected to ServiceControl in the appropriate environment. +ServiceControl and ServicePulse are server applications. They should be deployed in each environment, for example: test, QA, and production. When investigating problems or developing [custom checks](/monitoring/custom-checks/), it can be useful to have the Platform installed on a development machine. diff --git a/platform/installation.md b/platform/installation.md index 7f7e966f62b..9e7ddf5ba56 100644 --- a/platform/installation.md +++ b/platform/installation.md @@ -73,11 +73,3 @@ ServicePulse, along with ServiceControl, can be hosted in Visual Studio, with no #### Switch between ServiceControl Error instances When multiple ServiceControl Error instances are deployed, ServicePulse can be configured to switch between instances via the [ServicePulse UI connection management screen](/servicepulse/host-config.md#configuring-connections-via-the-servicepulse-ui). - -### ServiceInsight - -ServiceInsight can be installed using a dedicated [installation package](https://particular.net/downloads), which installs ServiceInsight as a Windows application. - -#### Switch between ServiceControl instances - -When multiple ServiceControl Error instances are deployed, the instance can be chosen using ServiceInsight's [Endpoint Explorer](/serviceinsight/#endpoint-explorer). diff --git a/platform/nservicebus.include.md b/platform/nservicebus.include.md index 183b6012ce7..4e3e9608491 100644 --- a/platform/nservicebus.include.md +++ b/platform/nservicebus.include.md @@ -76,7 +76,7 @@ NServiceBus is designed to work with the rest of the Particular Service Platform When a message fails to be processed, even after a number of retry strategies have been attempted, NServiceBus will forward the message to an [error queue](/nservicebus/recoverability/configure-error-handling.md) for manual investigation. Messages sent to the error queue are instrumented with headers containing details about the failure including a full exception stack trace. ServiceControl picks up messages from the error queue and makes them available in [ServicePulse](/servicepulse/). Once the root cause of the failure has been found and corrected, all messages caused by the same problem can be retried at once. -Additionally, each endpoint can send [heartbeat](/monitoring/heartbeats/), [health check](/monitoring/custom-checks/), and [performance metrics](/monitoring/metrics/) through the platform for visualization in ServicePulse, making it easy to see which endpoints are offline, which are ready to scale out, and which require manual intervention. Message visualizations available in [ServicePulse](/servicepulse/message-details.md#messages-with-audited-conversation-data) and [ServiceInsight](/serviceinsight/) make it easy to understand message flows and timing of a running NServiceBus system. +Additionally, each endpoint can send [heartbeat](/monitoring/heartbeats/), [health check](/monitoring/custom-checks/), and [performance metrics](/monitoring/metrics/) through the platform for visualization in ServicePulse, making it easy to see which endpoints are offline, which are ready to scale out, and which require manual intervention. Message visualizations available in [ServicePulse](/servicepulse/message-details.md#messages-with-audited-conversation-data) make it easy to understand message flows and timing of a running NServiceBus system. The [real-time monitoring demo](https://particular.net/real-time-monitoring) provides the ability to experience the Service Platform in action. The [Platform Sample package](/platform/platform-sample-package.md) provides the ability to demonstrate the Service Platform from within any .NET Project, without the need to install anything. diff --git a/platform/platform-sample-package.md b/platform/platform-sample-package.md index e155b781e38..258beee2e46 100644 --- a/platform/platform-sample-package.md +++ b/platform/platform-sample-package.md @@ -10,7 +10,7 @@ The [Platform Sample package](https://www.nuget.org/packages/Particular.Platform > [!WARNING] > The Platform Sample is not suited for production usage and should only be used for demonstrating the Platform during presentations or in samples. -The Platform Sample package includes instances of ServiceControl, ServiceControl Monitoring, and ServicePulse. They are all configured to use the [Learning Transport](/transports/learning/). Other transports are not supported by the Platform Sample package. At this time, ServiceInsight is not included in the Platform Sample package. +The Platform Sample package includes instances of ServiceControl, ServiceControl Monitoring, and ServicePulse. They are all configured to use the [Learning Transport](/transports/learning/). Other transports are not supported by the Platform Sample package. ## Installation @@ -52,7 +52,5 @@ snippet: ServicePulseDefaultRoute The [message replay tutorial](/tutorials/message-replay) is a sample that uses the Platform Sample package to view and retry failed messages. It shows how the Platform Sample package works from within an existing Visual Studio solution. -To use ServiceInsight with the sample, [download](https://github.com/Particular/serviceinsight/releases/latest) and install ServiceInsight. After starting ServiceInsight, connect to ServiceControl using the [Endpoint Explorer](/serviceinsight/#endpoint-explorer) at, for example, `http://localhost:49200/api`. - > [!NOTE] > The Platform Sample package will search for available ports and then display the ports being used. The actual ServiceControl port that needs to be used in the Endpoint Explorer can be seen in the output. diff --git a/platform/release-notes.md b/platform/release-notes.md index 9182714194b..540d9b27fcc 100644 --- a/platform/release-notes.md +++ b/platform/release-notes.md @@ -1,7 +1,7 @@ --- title: Platform Releases summary: Links to current and previous releases as well as release notes for the Particular Service Platform applications -reviewed: 2025-05-13 +reviewed: 2025-11-26 --- ## Applications and tools @@ -12,7 +12,6 @@ The Particular Service Platform source code, current and previous releases, and | | | | |:--- |:--- |:--- | | **NServiceBus** | [Releases](https://github.com/Particular/NServiceBus/tags) | [Release Notes](https://github.com/Particular/NServiceBus/releases)| -| **ServiceInsight** | [Releases](https://github.com/Particular/ServiceInsight/tags)|[Release Notes](https://github.com/Particular/ServiceInsight/releases)| | **ServicePulse** | [Releases](https://github.com/Particular/ServicePulse/tags)|[Release Notes](https://github.com/Particular/ServicePulse/releases)| | **ServiceControl** | [Releases](https://github.com/Particular/ServiceControl/tags)|[Release Notes](https://github.com/Particular/ServiceControl/releases)| diff --git a/platform/servicecontrol.include.md b/platform/servicecontrol.include.md index 319afc38515..db7ab188b6b 100644 --- a/platform/servicecontrol.include.md +++ b/platform/servicecontrol.include.md @@ -1,3 +1,3 @@ -ServiceControl is the backend for ServicePulse and ServiceInsight. It is a background process that collects useful information about an NServiceBus system. This includes messages that cannot be processed, their exceptions, and the ability to collect every message flowing through the system. It can also collect saga state changes, endpoint [heartbeats](/monitoring/heartbeats/), and perform [custom checks](/monitoring/custom-checks/). This information is exposed to [ServicePulse](/servicepulse) and [ServiceInsight](/serviceinsight) via an HTTP API. +ServiceControl is the backend for ServicePulse. It is a background process that collects useful information about an NServiceBus system. This includes messages that cannot be processed, their exceptions, and the ability to collect every message flowing through the system. It can also collect saga state changes, endpoint [heartbeats](/monitoring/heartbeats/), and perform [custom checks](/monitoring/custom-checks/). This information is exposed to [ServicePulse](/servicepulse) via an HTTP API. ServiceControl can also be configured to collect [detailed performance metrics](/monitoring/metrics/) for display in ServicePulse. \ No newline at end of file diff --git a/platform/third-party-licenses.md b/platform/third-party-licenses.md index e305b675397..68bb6923410 100644 --- a/platform/third-party-licenses.md +++ b/platform/third-party-licenses.md @@ -1,11 +1,10 @@ --- title: Third-party licenses summary: Licenses for third-party libraries used by the Particular Service Platform. -reviewed: 2024-11-29 +reviewed: 2025-11-26 related: - nservicebus/licensing - servicecontrol/license - - serviceinsight/license redirects: - nservicebus/upgrades/third-party-licenses ---