ServiceControl-Monitoring

Overview

Particular Software ServiceControl Monitoring The 'particular/servicecontrol-monitoring' image is part of the Particular Service Platform, which includes the following images: - particular/servicecontrol-ravendb | The database used by the error/audit instances (https://docs.particular.net/servicecontrol/ravendb/containers) - particular/servicecontrol | The primary/error instance, which includes error handling and recoverability (https://docs.particular.net/servicecontrol/servicecontrol-instances/) - particular/servicecontrol-audit | The audit instance, which stores audit data, and can be scaled out to multiple audit instances (https://docs.particular.net/servicecontrol/audit-instances/) - particular/servicecontrol-monitoring | The monitoring instance, which tracks runtime information like throughput, queue length, and other metrics (https://docs.particular.net/servicecontrol/monitoring-instances/) - particular/servicepulse | The web application that provides a front end for recoverability and monitoring features (https://docs.particular.net/servicepulse/) A monitoring instance can be installed to collect and analyze metric data generated by the metrics plugin installed in NServiceBus endpoints. This data is exposed to ServicePulse via an HTTP API. Additional optional environment variables can be configured. See "https://docs.particular.net/servicecontrol/monitoring-instances/configuration".

Requirements

See "https://docs.particular.net/servicecontrol/monitoring-instances/deployment/containers" and "https://github.com/Particular/PlatformContainerExamples".

Runtime arguments

Network: bridge
Shell: sh
Privileged: false

Template configuration

TRANSPORTTYPEVariable

Determines the message transport used to communicate with message endpoints. See

CONNECTIONSTRINGVariable

Provides the connection information to connect to the chosen transport. The form of this connection string is different for every message transport. See

PARTICULARSOFTWARE_LICENSEVariable

The Particular Software license, which is most easily provided to a container as an environment variable (https://docs.particular.net/nservicebus/licensing/#license-management-environment-variable). The environment variable should contain the full multi-line contents of the license file. A license file can also be volume-mounted to the container. e.g. (/usr/share/ParticularSoftware/license.xml). If no license file is provided, a trial license will be automatically enabled.

ParticularPlatformFilesPathrw

An optionally shared folder used by all Particular Service Platform containers. The license file can be saved here and shared among all containers.

Target: /usr/share/ParticularSoftware/
Default: /mnt/cache/appdata/ParticularPlatform/

Canonical PortPorttcp

33633 is the canonical port exposed by the monitoring instance API within the container, though this port can be mapped to any desired external port.

Target: 33633
Default: 33633
Value: 33633

Links

Template Support Docker Hub Project

Details

Repository

particular/servicecontrol-monitoring:latest

Registry

https://hub.docker.com/r/particular/servicecontrol-monitoring

Last Updated2026-04-13

First Seen2025-08-05

Run ServiceControl-Monitoring on Unraid.

ServiceControl-Monitoring is listed in Community Apps for Unraid OS. Explore Unraid to build a flexible home server, NAS, or homelab.

Explore Unraid OS