NServiceBusPerformanceCounters

This package provides HealthChecks to monitor the performance counters emitted by NServiceBus.

Install

Download the latest Wolfpack from codeplex...then you download & install this plug-in at a command line prompt in the Wolfpack installation folder with...
wolfpack.agent.exe /update:Wolfpack.Contrib.Checks.NServiceBusPerformanceCounters
Files installed...
  • \Wolfpack.Contrib.Checks.NServiceBusPerformanceCounters.dll
  • \Config\Checks\nservicebuscriticaltime.castle.config
  • \Config\Checks\nservicebussla.castle.config

NServiceBusCriticalTimeCounterCheck

The Critical Time counter monitors the age of the oldest message in the queue. This takes into account the whole chain from the message being sent on the client machine until successfully processed by the server.

You should define a SLA for each of your endpoints and use the CriticalTime counter to make sure that you're adhering to it. The Threshold is the maximum "age" of a message in the queue that is ok.

Configuration

1. Move the config files to one of the appropriate schedule subfolders of \Config\Checks...eg: \Config\Checks\EveryMinute. This will automagically bind this check to run "EveryMinute". You can create more subfolders, the only caveat is that they must correspond to a component named the same in the schedule.castle.config file. Recommendation is to run this check once a day.

2. To enable the check just set the "enabled" element value to "true".

Output

The output of this check is...

NServiceBusSLAViolationCounterCheck

The SLA Violation Counter acts as a early warning system that tells you the number of seconds left until the SLA for the particular endpoint is breached. The Threshold is the number of seconds until your SLA is breached.

Configuration

1. Move the config files to one of the appropriate schedule subfolders of \Config\Checks...eg: \Config\Checks\EveryMinute. This will automagically bind this check to run "EveryMinute". You can create more subfolders, the only caveat is that they must correspond to a component named the same in the schedule.castle.config file. Recommendation is to run this check once a day.

2. To enable the check just set the "enabled" element value to "true".

Output

The output of this check is...

Last edited Dec 21, 2012 at 9:29 PM by jimbobdog, version 4

Comments

No comments yet.