← Directory

ServiceControl-Audit

ServiceControl Audit is the audit instance of Particular ServiceControl, a monitoring component for NServiceBus distributed systems that records a complete…

  • Development
  • Monitoring & Logging
  • Tools & Utilities
ServiceControl Audit is the audit instance of Particular ServiceControl, a monitoring component for NServiceBus distributed systems that records a complete history of every message that flows through your platform. It stores that audit trail in a RavenDB-backed database, scales out to multiple audit instances for high message volume, and exposes the records over a HyperText Transfer Protocol (HTTP) API so you can search, inspect, and replay individual messages in ServicePulse and ServiceInsight. It suits teams running NServiceBus who need a durable, replayable message log for debugging and incident investigation.

Platform availability

Available on 1 of 9 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)

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 6 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 7 days ago

GitHub stars
60
Open issues
362
Last commit
2026-10-09
Latest release
6.21.2
Activity
declining

Checked 6 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 17 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create the instance with key settings Create the instance with a name, ports, install/database/log paths, message-queue connection string (how it reaches RabbitMQ), error queue (where failed messages go), and retention period. The example uses 44334 for the main port and 44335 for database maintenance, so set these before starting so the app has the right place to listen and store data. source
  • Fill in required auth settings If you enable authentication, enter the OpenID Connect authority (the URL of your identity provider) and the other required auth values. Leaving the authority blank makes the instance fail to start. source
  • Trust local HTTPS certificates If you use local HTTPS, install mkcert for your operating system and run mkcert -install. This adds the local certificate authority to the system trust store so browsers stop warning that the local site is unsafe. source

Fetched 16 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which ports should be set when creating a ServiceControl.Audit instance?

Set the instance ports before starting it, along with the install, database, and log paths. The example uses 44334 for the main port and 44335 for database maintenance.

What authentication setting must not be left blank when enabling OpenID Connect?

Enter the OpenID Connect authority and the other required authentication values. If the authority is blank, the instance fails to start.

What RavenDB version do new ServiceControl.Audit instances use from v4.26 onward?

New audit instances from v4.26 onward use RavenDB 5.4 instead of RavenDB 3.5. Upgrading and recreating an instance may be relevant when disk space is not freed after compacting.

Are Helm templates available for deploying ServiceControl.Audit on Kubernetes?

Helm template examples are available for deploying ServiceControl.Audit and related Particular Platform components on Kubernetes. They are intended to make installation and configuration easier.

Why might a newly installed ServiceControl.Audit v4.26.0 instance crash immediately after startup?

One instance crashed immediately after startup when installed with the audit -add PowerShell script using settings from an older instance.

Answers sourced from discuss.particular.net, discuss.particular.net, github.com, github.com, stackoverflow.com

Community

Collected 16 days ago - public community threads