CustomCheck results are sent to transports that are not configured

[kentdr]

Describe the bug

Description

The messaging bridge attempts to send CustomCheck results to transports that are not configured for custom checks causing an error to be logged.

Expected behavior

The messaging bridge only sends CustomCheck results to transports that are configured for custom checks.

Actual behavior

The messaging bridge attempts to send CustomCheck results to transports that do not have CustomChecks configured, resulting in an ArgumentException due to a null ServiceControl queue name.

Versions

2.2.0

Steps to reproduce

1. Write a custom check that will be executed when the messaging bridge starts
2. Configure one transport using ReportCustomChecksTo
3. Configure another transport without calling ReportCustomChecksTo
4. Start the bridge, and note the errors being logged when the custom check runs.

Relevant log output

fail: NServiceBus.TimerBasedPeriodicCheck[0] Custom check failed but can be retried. System.ArgumentNullException: Value cannot be null. (Parameter 'destination')

Additional Information

Workarounds

Possible solutions

Additional information

2.2.1 Release notes

[kentdr]

This bug has been fixed and was released with 2.2.1.