From 6ba94c0b96837b6de297278501f6560805ed5f0f Mon Sep 17 00:00:00 2001 From: Nick Gallegos Date: Fri, 13 Feb 2026 09:51:19 -0700 Subject: [PATCH 1/3] Document the hierarchical entities connection string parameter for 6.12.0 release --- servicecontrol/transports.md | 19 ++++++++++++------- 1 file changed, 12 insertions(+), 7 deletions(-) diff --git a/servicecontrol/transports.md b/servicecontrol/transports.md index 25603f49d42..15d83fefb93 100644 --- a/servicecontrol/transports.md +++ b/servicecontrol/transports.md @@ -63,14 +63,9 @@ As of versions 4.33.3 and 5.0.5 of ServiceControl, support for partitioned entit ### Enabling Hierarchical Entities -When [a hierarchy namespace prefix](/transports/azure-service-bus/configuration.md#entity-creation-hierarchy-namespace) is configured on endpoints, ServiceControl needs to be configured for the hierarchy namespace to monitor those endpoints. +As of version 6.12.0 of ServiceControl, support for hierarchical entities can be enabled by adding the following connection string parameter: -At a minimum, the error queue name needs the prefix prepended to the queue name, separated by a `/`. If monitoring or auditing are enabled, they also need to be modified. - -For example, given a hierarchy namespace of `my-hierarchy` and error, audit, and monitoring queues named `error`, `audit`, and `monitoring`: -- The [error queue name](/servicecontrol/servicecontrol-instances/configuration.md#transport-servicebuserrorqueue) would need to be set to `my-hierarchy/error`. -- The [audit queue name](/servicecontrol/audit-instances/configuration.md#transport-servicebusauditqueue) would need to be set to `my-hierarchy/audit`. -- The [monitoring queue name](/servicecontrol/monitoring-instances/configuration.md#transport-monitoringerrorqueue) would need to be set to `my-hierarchy/monitoring`. +* `HierarchyNamespace=` — Configures the transport to use [a hierarchy namespace prefix](/transports/azure-service-bus/configuration.md#entity-creation-hierarchy-namespace). The default value is `null`, which means no hierarchy namespace is used. This isolates the ServiceControl instance to the hierarchy, so an instance-per-hierarchy would be required to monitor multiple hierarchies. @@ -80,6 +75,16 @@ Endpoints configured with a hierarchy namespace will use error, audit, and monit 1. Configure ServiceControl error, audit, and monitoring instances as you would without using a hierarchy namespace. 2. For each hierarchy-specific error, audit, and monitoring queue that you wish to monitor centrally, configure [auto-forwarding for their corresponding queues in azure](https://learn.microsoft.com/en-us/azure/service-bus-messaging/enable-auto-forward#update-the-auto-forward-setting-for-an-existing-queue) to forward messages to the central error, audit, and monitoring queues. +#### Previous versions + +Previous versions of ServiceControl can still be configured on a per-hierarcy basis. At a minimum, the error queue name needs the prefix prepended to the queue name, separated by a `/`. If monitoring or auditing are enabled, they also need to be modified. + +For example, given a hierarchy namespace of `my-hierarchy` and error, audit, and monitoring queues named `error`, `audit`, and `monitoring`: +- The [error queue name](/servicecontrol/servicecontrol-instances/configuration.md#transport-servicebuserrorqueue) would need to be set to `my-hierarchy/error`. +- The [audit queue name](/servicecontrol/audit-instances/configuration.md#transport-servicebusauditqueue) would need to be set to `my-hierarchy/audit`. +- The [monitoring queue name](/servicecontrol/monitoring-instances/configuration.md#transport-monitoringerrorqueue) would need to be set to `my-hierarchy/monitoring`. + + ### Example connection string ```text From d84ed2b05d16405a089eb88faf860b92958b9e1e Mon Sep 17 00:00:00 2001 From: Nick Gallegos Date: Fri, 13 Feb 2026 10:04:03 -0700 Subject: [PATCH 2/3] Update ASBS ServiceControl example connection string --- servicecontrol/transports.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/servicecontrol/transports.md b/servicecontrol/transports.md index 15d83fefb93..928df5bc906 100644 --- a/servicecontrol/transports.md +++ b/servicecontrol/transports.md @@ -88,7 +88,7 @@ For example, given a hierarchy namespace of `my-hierarchy` and error, audit, and ### Example connection string ```text -Endpoint=sb://[namespace].servicebus.windows.net; SharedSecretIssuer=;SharedSecretValue=;QueueLengthQueryDelayInterval=;TopicName=;EnablePartitioning= +Endpoint=sb://[namespace].servicebus.windows.net; SharedSecretIssuer=;SharedSecretValue=;QueueLengthQueryDelayInterval=;TopicName=;EnablePartitioning=;HierarchyNamespace= ``` ## Azure Storage Queues From 766bdafda9289274a051281d7ffc70f41c045b37 Mon Sep 17 00:00:00 2001 From: Nick Gallegos Date: Fri, 13 Feb 2026 10:07:55 -0700 Subject: [PATCH 3/3] Spelling and capitalization tweaks --- servicecontrol/transports.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/servicecontrol/transports.md b/servicecontrol/transports.md index 928df5bc906..2797975bb41 100644 --- a/servicecontrol/transports.md +++ b/servicecontrol/transports.md @@ -73,11 +73,11 @@ This isolates the ServiceControl instance to the hierarchy, so an instance-per-h Endpoints configured with a hierarchy namespace will use error, audit, and monitoring queues prefixed with the hierarchy namespace. To monitor all hierarchies with a single ServiceControl installation: 1. Configure ServiceControl error, audit, and monitoring instances as you would without using a hierarchy namespace. -2. For each hierarchy-specific error, audit, and monitoring queue that you wish to monitor centrally, configure [auto-forwarding for their corresponding queues in azure](https://learn.microsoft.com/en-us/azure/service-bus-messaging/enable-auto-forward#update-the-auto-forward-setting-for-an-existing-queue) to forward messages to the central error, audit, and monitoring queues. +2. For each hierarchy-specific error, audit, and monitoring queue that you wish to monitor centrally, configure [auto-forwarding for their corresponding queues in Azure](https://learn.microsoft.com/en-us/azure/service-bus-messaging/enable-auto-forward#update-the-auto-forward-setting-for-an-existing-queue) to forward messages to the central error, audit, and monitoring queues. #### Previous versions -Previous versions of ServiceControl can still be configured on a per-hierarcy basis. At a minimum, the error queue name needs the prefix prepended to the queue name, separated by a `/`. If monitoring or auditing are enabled, they also need to be modified. +Previous versions of ServiceControl can still be configured on a per-hierarchy basis. At a minimum, the error queue name needs the prefix prepended to the queue name, separated by a `/`. If monitoring or auditing are enabled, they also need to be modified. For example, given a hierarchy namespace of `my-hierarchy` and error, audit, and monitoring queues named `error`, `audit`, and `monitoring`: - The [error queue name](/servicecontrol/servicecontrol-instances/configuration.md#transport-servicebuserrorqueue) would need to be set to `my-hierarchy/error`.