Manage Forward To for Azure Service Bus Queues and Topic Subscriptions
Microsoft Azure Service Bus includes Forward To so you can decouple producers from downstream processing paths, route messages to dedicated processing queues, and simplify publisher logic when topology changes. This becomes critical in real production environments where Queue and Topic Subscription chains can hide bottlenecks and backlog buildup.
This page explains why Forward To exists, why monitoring forwarding chains is vital, and how to configure and operate the options in Nodinite for both Queue and Topic Subscription resources.
Understanding Forward To and Auto-forwarding
Forward To lets a source Queue or Topic Subscription automatically route messages to a target entity. In Azure Service Bus, this enables architecture patterns such as:
- Ingress queue to processing queue handoff
- Filtered Topic Subscription to specialized queue pipelines
- Operational isolation where one target queue is drained by a dedicated worker set
Without monitoring, forwarding can mask failures. Messages on an entity with Forward To set should drain to the forwarding target almost immediately. When active messages linger on the forwarding entity instead, the target may be missing, disabled, unavailable, or constrained by quota or maximum size limits.
The Nodinite Message Queueing Monitoring Agent provides:
- ✅ Unified monitoring behavior for Queue and Topic Subscription forwarding scenarios
- ✅ Auto-forwarding evaluation controls in Remote Configuration and the Edit thresholds action
- ✅ Resource-level status visibility when forwarding entities contain active messages
- ✅ Monitoring thresholds that help you detect stale or blocked forwarding paths early
Forwarding Flow and Evaluation Model
Diagram: Messages should drain from the forwarding entity to its Forward To target. When active messages remain, the selected Auto-forwarding evaluation option decides whether the Resource is OK (green), Warning (yellow), or Error (red), or whether your configured thresholds decide (blue). A quota, dead-letter, or configuration Error still takes precedence.
What You Configure and Why
| Where | Setting (as labeled in the UI) | Scope | Why it matters |
|---|---|---|---|
| Remote Configuration › Azure Service Bus › Queue Thresholds tab | Auto-forwarding evaluation (default) | Default for all monitored Queues | Decides the state of a Queue with Forward To set when active messages remain on it |
| Remote Configuration › Azure Service Bus › Topic Thresholds › Topic Subscription Defaults tab | Auto-forwarding evaluation (default) | Default for all monitored Topic Subscriptions | Ensures routed subscriptions are not silently failing downstream |
| Edit thresholds action on a Queue Resource › Auto-forwarding panel (Edit Thresholds) | Auto-forwarding evaluation | One specific Queue | Overrides the default for a single Queue during tuning or incident handling |
| Edit thresholds action on a Topic Subscription Resource › Auto-forwarding panel (Topic Subscription Edit Thresholds) | Auto-forwarding evaluation | One specific Topic Subscription | Overrides the default for a single Topic Subscription during tuning or incident handling |
Monitoring Behavior with Forwarding Entities
Start by reviewing how forwarding entities appear in Resources and how evaluated states differ by runtime condition. The Log Text column tells you why a forwarding entity has its state:
- Warning or Error: "Active messages exist even though the entity has a 'Forward To' property set; there may be a temporary issue with the 'Forward To' entity. Please ensure the target entity exists, is not disabled, is available and accessible, and that there are no quota limits or maximum queue size exceeded" (Topic Subscriptions say "maximum topic subscription size").
- OK: "Active message(s) exist on a 'Forward To' entity; treated as OK per the configured Auto-Forward level." This appears when the Auto-forwarding evaluation is Always OK.
Mixed statuses across forwarding entities
What you do: Inspect the view to identify which forwarding entities are healthy, warning, or error, then prioritize remediation by state severity.
Example of monitoring resources where active messages exist on forwarding entities with mixed statuses.
Forwarding entity with OK status
What you do: Validate the expected steady-state baseline where forwarding targets drain normally and thresholds remain within limits.
Example of monitoring resources where active messages exist on a forwarding entity and the evaluated status is OK.
Forwarding queues view
What you do: Focus on queue-based forwarding paths to verify target queues are available and not accumulating unexpected active messages.
Example of monitoring resources where active messages exist on forwarding queues.
Forwarding topic subscription view
What you do: Review Topic Subscription forwarding chains and confirm subscription-target routing does not create hidden backlog.
Example of monitoring resources where active messages exist on a forwarding topic subscription.
Remote Configuration and Threshold Options
Next, configure how forwarding behavior is evaluated globally and per entity.
Remote Configuration auto-forwarding options
What you do: Open Remote Configuration and select the auto-forwarding evaluation behavior that matches your operations policy.
The Auto-forwarding evaluation (default) setting defines how Nodinite evaluates an entity with Forward To set when active messages remain on it. The UI describes it as: "How an auto-forwarding queue is evaluated when active messages remain. Messages should drain to the forwarding target, so any that linger may indicate the target is unavailable. A quota, dead-letter, or configuration Error still takes precedence."
Auto-forwarding evaluation options
The dropdown includes four operational modes:
- Use configured thresholds: Evaluate the forwarding entity using your configured Warning and Error thresholds for age and count, like any other Queue or Topic Subscription.
- ✅ Always OK: Keep the state OK even when active messages remain on the forwarding entity.
- ⚠️ Raise Warning: Set the state to Warning when active messages remain on the forwarding entity.
- ❌ Raise Error: Set the state to Error when active messages remain on the forwarding entity.
Select One is only the placeholder in the Remote Configuration dropdown before you choose one of the four modes above; the Edit thresholds dialog lists only the four modes.
Note
Whatever option you choose, a quota, dead-letter, or configuration Error on the entity still takes precedence. Always OK doesn't hide those problems.
Example of the Auto-forwarding evaluation (default) dropdown in Remote Configuration, with Raise Warning selected.
Queue thresholds with auto-forwarding setting
What you do: Set Queue monitoring thresholds so active messages on forwarding targets trigger the expected warning or error behavior.
Example of queue threshold settings that include auto-forwarding configuration.
Topic Subscription remote configuration
What you do: Configure equivalent behavior for Topic Subscription forwarding to keep Queue and Topic Subscription operations aligned.
Example of remote configuration for a topic subscription with auto-forwarding options.
Topic Subscription option details (zoomed)
What you do: Use the detailed view to verify exact evaluation settings before you save and apply the configuration.
Example of an enhanced view of topic subscription auto-forwarding options in remote configuration.
Edit Action Views for Forward To
After configuring defaults, use the Edit thresholds action on a specific Resource for targeted adjustments. Both the Queue and the Topic Subscription Edit modal have an Auto-forwarding panel with the Auto-forwarding evaluation dropdown; the Resource details at the top also show the Forward to target. Each heading below gives the path to what the screenshot shows.
Queue › Actions › Edit thresholds (full Edit modal)
What you do: Open the Edit modal for a Queue with Forward To set and review the Forward to target in the Resource details together with the Auto-forwarding panel, next to the Allowed Timespan, Message Count, and Delivery Count panels.
The full Edit modal for a Queue whose Forward to target is target-q. The Auto-forwarding panel is at the bottom right.
Queue › Actions › Edit thresholds › Auto-forwarding panel › Auto-forwarding evaluation dropdown
What you do: Open the dropdown and choose one of the four options: Use configured thresholds, Always OK, Raise Warning, or Raise Error.
Close-up of the Auto-forwarding evaluation dropdown, with Raise Warning selected.
Queue › Actions › Edit thresholds › Auto-forwarding panel › help text
What you do: Read the help text below the dropdown to confirm what the selected option means before you click Save.
Close-up of the Auto-forwarding panel and its help text: a quota, dead-letter, or configuration Error still takes precedence.
Topic Subscription › Actions › Edit thresholds › Auto-forwarding panel
What you do: Open the Edit modal for a Topic Subscription and scroll down to the Auto-forwarding panel. It works the same as for a Queue; the help text reads "Controls how an auto-forwarding topic subscription is evaluated when active messages remain."
The bottom part of the Topic Subscription Edit modal, with the Auto-forwarding panel on the right and Raise Warning selected.