User indicators documentation (#7221)

Co-authored-by: Andreas Öhlund <[email protected]>

Author: cquirosj

nservicebus/transactional-session/index.md

@@ -83,6 +83,8 @@ It's recommended to not mix the processing of control messages with business mes
 - More accurate metrics: Metrics like critical time and queue length will accurately represent the performance of the control message processing and not be skewed by business messages
 - Simplified management: Knowing that the endpoint only processes control messages makes it possible to always retry all failed messages related to the endpoint via tools like ServicePulse
 
+When configuring endpoints for usage measurement in ServicePulse, mark dedicated transactional session processor endpoints with the appropriate [endpoint type indicator](/servicepulse/usage.md#setting-an-endpoint-type-endpoint-type-indicators).
+
 partial: remote-processor
 
 ## Transaction consistency

servicepulse/images/usage-endpoints-filter.png

@@ -57,10 +57,38 @@ This option will not be displayed for non-broker transports (e.g. MSMQ and Azure
 
 The usage summary may contain detected queues that should not be counted as part of a license with Particular Software.
 
-Once a report is submitted to Particular, it is reviewed and any system queues that should not be counted for licensing purposes are removed.
+Once a report is submitted to Particular, it is reviewed, and any system queues that should not be counted for licensing purposes are removed.
 
 In addition, the detected endpoints and broker queues screens provide an option to set the endpoint type, which specifies a reason as to why a queue should not be included in the licensing calculations. Any changes made to the endpoint type are automatically saved.
 
+### Endpoint type indicators
+
+The following endpoint type indicators are available to help categorize endpoints appropriately:
+
+#### NServiceBus Endpoint
+
+Known NServiceBus [endpoint](/nservicebus/endpoints/). These endpoints are included in licensing calculations as they represent active NServiceBus endpoints processing business messages.
+
+#### No longer in use
+
+NServiceBus endpoint that is no longer in use, usually this would have zero throughput. These endpoints are not included in licensing calculations since they are inactive.
+
+#### Transactional Session Processor Endpoint
+
+An [endpoint that is only processing transactional session control messages](/nservicebus/transactional-session/#design-considerations). These are [specialized endpoints](/nservicebus/transactional-session/#remote-processor) dedicated to handling the coordination of transactional sessions, and it is excluded during licensing calculations.
+
+#### Send-Only Endpoint
+
+An endpoint that [only sends](/nservicebus/hosting/#self-hosting-send-only-hosting) messages and does not process any messages. These endpoints have different licensing considerations since they don't process incoming messages.
+
+#### Planned to be decommissioned
+
+If the endpoint is planned to no longer be used in the next 30 days. These endpoints may be excluded from licensing calculations as they represent temporary infrastructure.
+
+#### Not an NServiceBus Endpoint
+
+Not an NServiceBus endpoint. These are broker queues or other messaging infrastructure that should not be included in NServiceBus licensing calculations.
+
 ### Bulk endpoint updates
 
 The filter option can be used for bulk updating of endpoints or queues matching a certain naming pattern.