← Directory

ServicePulse

ServicePulse is a real-time production monitoring dashboard for distributed applications built on the Particular Service Platform.

  • Tools & Utilities
ServicePulse is a real-time production monitoring dashboard for distributed applications built on the Particular Service Platform. It tracks the health of message-processing endpoints, surfaces processing errors, and lets operators resend failed messages, giving teams a consolidated view of their NServiceBus system.

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.

65/100 Good

Maintained
100last commit 5 days ago
Popular
3241 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

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

GitHub stars
41
Open issues
193
Last commit
2026-10-07
Latest release
2.12.0
Activity
declining

Checked 5 days ago - source: GitHub (Particular/ServicePulse)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Tell ServicePulse where ServiceControl lives When installing, set --serviceControlUrl to ServiceControl's API web address (where ServicePulse fetches data) and --url to the web port you want to open in a browser. If these are missing or wrong, ServicePulse may start but not show any monitoring data, or you may not be able to reach it. source
  • Behind a proxy? Enable forwarded headers If ServicePulse sits behind a reverse proxy (a middleman web server), enable forwarded headers and tell ServicePulse to trust that proxy. Without this, redirects and logins can fail because it sees the proxy instead of the browser. source
  • Using HTTPS? Provide a valid certificate If you turn on HTTPS, point ServicePulse at your certificate file and password (the .pfx file that stores the HTTPS key), and set the HTTPS port if needed. Without a trusted certificate, browsers show security warnings and sign-in may break. source

Fetched 6 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Can ServicePulse be installed in IIS instead of its default hosting?

Yes. By default ServicePulse is installed as a Windows Service that self-hosts the web application, but it can also be installed manually in IIS.

Why might duplicate endpoints appear in ServicePulse after a redeployment?

This can happen when an endpoint is redeployed or updated to a different installation path, which is common with deployment managers like Octopus Deploy.

Can ServicePulse send failed messages for reprocessing?

Yes. It detects processing errors and can send failed messages for reprocessing.

Does ServicePulse provide real-time monitoring?

Yes. It provides real-time production monitoring for distributed applications.

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

Community

Collected 14 days ago - public community threads