ServiceControl Monitoring

ServiceControl Monitoring is the monitoring instance of the Particular Service Platform that tracks runtime metrics such as throughput, queue length, and…

  • Development
  • Monitoring & Logging
  • Tools & Utilities
ServiceControl Monitoring is the monitoring instance of the Particular Service Platform that tracks runtime metrics such as throughput, queue length, and endpoint health for operators of NServiceBus distributed systems.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

59/100 Fair

Maintained
100last commit 17 days ago
Popular
3660 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
2016 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 47 days ago

GitHub stars
60
Open issues
362
Last commit
2026-11-04
Latest release
6.22.1
Activity
declining

Checked 17 days ago - source: GitHub (Particular/ServiceControl)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 4 CPU core(s). ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set paths, ports, and queue details When creating the instance, fill in the database/log folders, the web UI port, and the RabbitMQ (message queue) connection details. If a required value is missing or a port is already in use, ServiceControl won't start or the UI won't be reachable. source
  • Fill in authentication values if enabled If you enable authentication, fill in the required login-service settings, such as the authority (the address of your login system) and audience. Without a valid authority, ServiceControl won't start and will show an authentication error. source
  • Trust local test certificates If you use the local HTTPS testing setup, install mkcert and run mkcert -install once. That adds the local certificate to your computer's trusted list, so browsers stop warning that the test site is unsafe. source

Fetched 54 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Why won't ServiceControl start or why is the web UI unreachable?

Check that the database/log folders, web UI port, and RabbitMQ connection details are set. A missing required value or a port already in use can prevent startup or make the UI unreachable.

What authentication settings are required if I enable authentication?

Fill in the required login-service settings, such as the authority, which is the address of your login system, and audience. Without a valid authority, ServiceControl won't start and shows an authentication error.

How do I stop browser warnings for the local HTTPS testing setup?

Install mkcert and run mkcert -install once. That adds the local certificate to your computer's trusted list, so browsers stop warning that the test site is unsafe.

Does the hosting and security guide cover the Monitoring instance?

Yes, it covers hosting and security options for ServiceControl, ServiceControl.Audit, and ServiceControl.Monitoring instances.

Answers sourced from docs.particular.net, github.com, github.com, github.com

Community

Collected 53 days ago - public community threads