Azure Service Bus Integration
Queue and topic metrics, dead-letter monitoring, and message throughput for Azure Service Bus. Detect DLQ accumulation and consumer lag before they cascade into application failures.
How It Works
Create a Service Principal
Register an Azure Service Principal with Monitoring Reader on your Service Bus namespace resource group. TigerOps reads queue depth, message counts, and throughput from Azure Monitor.
Enable Namespace Diagnostics
Turn on Diagnostic Settings for your Service Bus namespace to stream OperationalLogs and VNetAndIPFilteringLogs to Log Analytics. Enable the AllMetrics category for real-time metric ingestion.
Map Queues and Topics
In TigerOps, list the queues, topics, and subscriptions you want to track. TigerOps automatically discovers all entities in the namespace but you can scope monitoring to critical paths only.
Configure Dead-Letter Alerts
Set dead-letter count thresholds per queue and subscription. TigerOps fires alerts as soon as dead-letter messages accumulate and includes message body previews to speed up investigation.
What You Get Out of the Box
Queue & Topic Depth Tracking
Active message counts, scheduled message counts, and transfer dead-letter counts per queue, topic, and subscription. Spot queue depth growth before it causes consumer timeouts.
Dead-Letter Monitoring
Real-time dead-letter count alerts with message age, reason code distribution, and first-seen timestamps. TigerOps groups DLQ messages by error reason to surface the most impactful failures.
Message Throughput Metrics
Incoming and outgoing message rates per entity, byte throughput, and request counts across Send, Receive, and Complete operations. Detect throughput drops before they cause SLA breaches.
Server Errors & Throttling
Server error rates, throttled request counts, and namespace quota utilization. Identify when your Service Bus tier is under-provisioned and upgrade before errors reach consumers.
Message Lock Expiry Tracking
Lock renewal failure rates and message lock expiry counts per queue. High expiry rates signal slow consumers or processing bottlenecks that cause messages to be redelivered.
AI Consumer Lag Correlation
TigerOps AI links Service Bus queue depth growth to downstream consumer service metrics — CPU, memory, and error rates — identifying whether the backlog is caused by slow processing or consumer failures.
Enable Service Bus Diagnostics
Stream namespace metrics and operational logs to Log Analytics for full Service Bus visibility in TigerOps.
#!/bin/bash
# TigerOps — Azure Service Bus integration setup
NAMESPACE="my-servicebus-namespace"
RESOURCE_GROUP="my-resource-group"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
SB_RESOURCE="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.ServiceBus/namespaces/${NAMESPACE}"
# Enable Diagnostic Settings
az monitor diagnostic-settings create \
--name tigerops-servicebus \
--resource "${SB_RESOURCE}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[{"category":"AllMetrics","enabled":true,"retentionPolicy":{"days":30,"enabled":true}}]' \
--logs '[
{"category":"OperationalLogs", "enabled":true},
{"category":"VNetAndIPFilteringLogs", "enabled":true},
{"category":"RuntimeAuditLogs", "enabled":true},
{"category":"ApplicationMetricsLogs", "enabled":true}
]'
# Create Service Principal for TigerOps
az ad sp create-for-rbac \
--name tigerops-servicebus-reader \
--role "Monitoring Reader" \
--scopes "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}"
echo "Service Bus diagnostics enabled for namespace: ${NAMESPACE}"Common Questions
Does TigerOps support both Basic and Standard/Premium Service Bus tiers?
Yes. TigerOps monitors all Service Bus tiers. Premium tier namespaces get additional metrics including messaging unit utilization and isolation-level resource consumption. Dead-letter queues are available on Standard and Premium tiers only.
How does TigerOps monitor dead-letter queues?
TigerOps reads the DeadLetterMessageCount metric from Azure Monitor for each queue and subscription. When the count exceeds your configured threshold, an alert fires with the dead-letter reason code distribution to help you diagnose root cause quickly.
Can TigerOps track session-enabled queues?
Yes. For session-enabled queues, TigerOps tracks active session count, session message counts, and sessions with locked messages. Abandoned sessions that accumulate unprocessed messages are surfaced as anomalies.
What is the polling frequency for Service Bus metrics?
Azure Monitor emits Service Bus metrics at 1-minute granularity. TigerOps ingests these metrics in near-real-time through the Azure Monitor Metrics API and evaluates alert thresholds every 60 seconds.
How do I monitor forwarding chains across topics and queues?
TigerOps builds a message flow graph from your Service Bus namespace topology. You can visualize forwarding chains and see end-to-end message latency from a topic publish to final queue consumption.
Never Miss a Dead-Letter Accumulation Again
Queue depth, DLQ monitoring, and AI consumer lag analysis for Azure Service Bus. Connect in 5 minutes.