The Particular throughput tool can be installed locally and run against a production system to discover the throughput of each endpoint in a system over a period of time.
This article details how to collect endpoint and throughput data using data from ServiceControl. Refer to the throughput counter main page for information how to install/uninstall the tool or for other data collection options.
The tool should be used with a supported version of ServiceControl.
Do not attempt to install ServiceControl just to run the throughput tool on an MSMQ or Azure Storage Queues system. In order to successfully collect any data, every system endpoint must be modified to send data to the new ServiceControl installation or there will be no data to collect. Instead, reach out to a licensing specialist to suggest alternate ways to estimate the system throughput needed for licensing.
Running the tool
Once installed, execute the tool with the URLs for the ServiceControl and monitoring APIs.
If the tool was installed as a .NET tool:
throughput-counter servicecontrol [options] --serviceControlApiUrl http://localhost:33333/api/ --monitoringApiUrl http://localhost:33633/
Or, if using the self-contained executable:
Particular.EndpointThroughputCounter.exe servicecontrol [options] --serviceControlApiUrl http://localhost:33333/api/ --monitoringApiUrl http://localhost:33633/
Because ServiceControl contains, at maximum, the previous 1 hour of monitoring data, the tool will query the ServiceControl API 24 times with a one-hour sleep period between each attempt in order to capture a total of 24 hours worth of data.
For endpoints that do not have monitoring enabled, the tool will fall back to querying message audit data to determine how many messages have been processed each hour.
Options
| Option | Description |
|---|---|
--serviceControlApiUrl | Required – The URL of the ServiceControl API. In the ServiceControl Management Utility, find the instance identified as a ServiceControl Instance and use the value of the URL field, as shown in the screenshot below. |
--monitoringApiUrl | Required – The URL of the Monitoring API. In the ServiceControl Management Utility, find the instance identified as a Monitoring Instance and use the value of the URL field, as shown in the screenshot below. |
--queueNameMasks | Masks sensitive information in the generated report. See masking private data. |
--customerName | Sets the customer name. If not provided, the tool will prompt for the information. Example: --customerName "Particular Software" |
--unattended | Will not prompt for user input, so that the tool can be used from environments such as a continuous integration system. |
--skipVersionCheck | Will not perform the check, for use in environments when outgoing network access creates alerts. |
This screenshot shows how to identify the instance types and locate the required URLs:
What the tool does
The tool will send HTTP requests to both the ServiceControl primary instance and the ServiceControl monitoring instance.
Primary instance
The following requests will be sent to the primary instance:
<PrimaryUrl> <PrimaryUrl>/ endpoints <PrimaryUrl>/ configuration/ remotes <PrimaryUrl>/ endpoints/ {EndpointName}/ audit-count
Monitoring instance
The following requests will be sent to the monitoring instance:
<MonitoringUrl> <MonitoringUrl>/ monitored-endpoints?history=60