Getting Started
Architecture
Service Platform
NServiceBus
Transports
Persistence
ServiceInsight
ServicePulse
ServiceControl
Monitoring
Shape the future
Samples

Deploying the MassTransit Connector

Component: ServiceControl

Overview

When MassTransit is used with the rest of the platform, there are in total 4 containers that need to be deployed:

  1. particular/servicecontrol
  2. particular/servicecontrol-ravendb
  3. particular/servicecontrol-masstransit-connector
  4. particular/servicepulse

The particular/servicecontrol and particular/servicecontrol-ravendb containers are used to ingest messages from the error queue.

The particular/servicecontrol-masstransit-connector container reads messages from the MassTransit system's error queues and moves them into the error queue to be ingested by ServiceControl.

The particular/servicepulse container exposes a web interface to allow users to retry failed messages back to the MassTransit system.

Getting started

The first step is to configure and deploy the particular/servicecontrol image, to do this follow this deployment guide.

After that, follow the instructions in Docker Hub on How to use this image.

Feedback