Skip to content

Commit e3e3a27

Browse files
jpalacabparticular
andauthored
Add note about SP being required in the future (#6799)
* Add note about SP * Update nservicebus/usage/index.md Co-authored-by: Andreas Bednarz <[email protected]> * Update nservicebus/usage/index.md --------- Co-authored-by: Andreas Bednarz <[email protected]>
1 parent 8a62d7a commit e3e3a27

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

nservicebus/usage/index.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,15 +26,18 @@ The recommended method for measuring usage in an NServiceBus system is via Servi
2626

2727
This method requires ServicePulse version 1.40 or later, and ServiceControl version 5.4 or later. Additionally, if using RabbitMQ broker, version 3.10.0 or higher is required.
2828

29-
To learn more about this method, read the [ServicePulse Usage documentation](/servicepulse/usage.md).
29+
To learn more about this method, read the [ServicePulse Usage documentation](/servicepulse/usage.md).
30+
31+
> [!NOTE]
32+
> While customers are not required to use ServicePulse at this time, it will become a requirement for all active projects in the future.
3033
3134
## Standalone Endpoint Throughput tool
3235

3336
Customers who are not able to use ServicePulse can use the Endpoint Throughput tool to measure their system usage.
3437

3538
This is a standalone tool that is run on demand, and can typically be installed on a [user's workstation](/nservicebus/throughput-tool/faq.md#does-the-tool-need-to-run-on-my-production-server).
3639

37-
To learn more about this method, read the [Endpoint Throughput tool documentation](./../throughput-tool).
40+
To learn more about this method, read the [Endpoint Throughput tool documentation](./../throughput-tool).
3841

3942
## Requirements
4043

0 commit comments

Comments
 (0)