Skip to content

Latest commit

 

History

History
35 lines (27 loc) · 1.79 KB

performance-counters.md

File metadata and controls

35 lines (27 loc) · 1.79 KB
title summary reviewed component redirects related
Windows Performance Counters
Monitoring through the use of Windows performance counters.
2024-01-26
PerfCounters
nservicebus/monitoring-nservicebus-endpoints
nservicebus/operations/monitoring-endpoints
nservicebus/operations/fail-or-hang-during-performance-counter-setup
nservicebus/operations/performance-counters
nservicebus/operations
nservicebus/recoverability
nservicebus/operations/auditing
transports/msmq/management-using-powershell
samples/performance-counters

When a system is broken down into multiple processes - each with its own queue - it allows identifying which process is the bottleneck by examining how many messages (on average) are in each queue. However, it is not possible to know how long messages are waiting in each queue - which is the primary indicator of a bottleneck - without knowing the rate of messages coming into each queue, and the rate at which messages are being processed from each queue.

Note

The NServiceBus.Metrics.PerformanceCounters package is only available for Windows. Newer projects may benefit more from monitoring via OpenTelemetry.

The Windows Performance Counters package provides additional performance counters to better understand how long it takes for messages to flow through queues, not just the number of messages in the queue.

Since all performance counters in Windows are exposed via Windows Management Instrumentation (WMI), it is very straightforward to pull this information into the existing monitoring infrastructure.

partial: note

partial: counters

partial: installing

Note

Send-only endpoints are currently not supported since they don't receive messages.