Azure Event Hubs Integration
Partition throughput, consumer offset lag, and capture metrics for Azure Event Hubs. Detect TU exhaustion and consumer lag growth before your event pipeline falls behind.
How It Works
Create Service Principal
Register an Azure Service Principal with Monitoring Reader on your Event Hubs namespace resource group. TigerOps pulls partition-level throughput and consumer group metrics from Azure Monitor.
Enable Namespace Diagnostics
Configure Diagnostic Settings on the Event Hubs namespace to stream ArchiveLogs, OperationalLogs, and AllMetrics to a Log Analytics workspace for real-time ingestion.
Configure Consumer Groups
Add your consumer group names in TigerOps. The integration tracks per-partition sequence number lag for each consumer group and surfaces imbalanced consumer assignments.
Set Throughput Alerts
Define Throughput Unit (TU) consumption thresholds and consumer lag SLOs. TigerOps alerts before quota exhaustion and predicts when you need to add TUs based on growth trends.
What You Get Out of the Box
Partition Throughput Metrics
Incoming bytes, incoming messages, outgoing bytes, and outgoing messages per partition and per event hub. Identify unbalanced partitions that become throughput bottlenecks.
Consumer Offset Lag
Per-partition sequence number lag for each consumer group with historical trend analysis. TigerOps alerts when lag growth rate predicts an SLO breach before it occurs.
Capture Metrics
Event Hubs Capture file write success rates, capture backlog size, and time-to-capture latency. Monitor your capture pipeline to ensure no events are lost to storage.
Throttled Request Tracking
ThrottledRequests count and quota utilization per namespace. Understand when Throughput Units are exhausted and plan capacity increases before producers are throttled.
Namespace-Level Quotas
Throughput Unit utilization, active connections, and message retention window monitoring. TigerOps forecasts TU exhaustion based on current traffic growth rates.
AI Lag Root Cause Analysis
When consumer lag spikes, TigerOps AI correlates the event with producer throughput changes, consumer group errors, or partition rebalance events to identify the true root cause.
Event Hubs Diagnostic Settings
Enable namespace metrics and archive logs for full Event Hubs visibility in TigerOps.
#!/bin/bash
# TigerOps — Azure Event Hubs integration setup
NAMESPACE="my-eventhubs-namespace"
RESOURCE_GROUP="my-resource-group"
WORKSPACE_ID="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.OperationalInsights/workspaces/tigerops-workspace"
EH_RESOURCE="/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}/providers/Microsoft.EventHub/namespaces/${NAMESPACE}"
# Enable all Event Hubs diagnostic categories
az monitor diagnostic-settings create \
--name tigerops-eventhubs \
--resource "${EH_RESOURCE}" \
--workspace "${WORKSPACE_ID}" \
--metrics '[{"category":"AllMetrics","enabled":true,"retentionPolicy":{"days":30,"enabled":true}}]' \
--logs '[
{"category":"ArchiveLogs", "enabled":true},
{"category":"OperationalLogs", "enabled":true},
{"category":"AutoScaleLogs", "enabled":true},
{"category":"KafkaCoordinatorLogs","enabled":true},
{"category":"EventHubVNetConnectionEvent","enabled":true}
]'
# Grant TigerOps Service Principal Monitoring Reader
az role assignment create \
--assignee "${TIGEROPS_SP_CLIENT_ID}" \
--role "Monitoring Reader" \
--scope "/subscriptions/${SUBSCRIPTION_ID}/resourceGroups/${RESOURCE_GROUP}"
echo "Event Hubs diagnostics enabled for namespace: ${NAMESPACE}"Common Questions
Does TigerOps support Event Hubs Dedicated clusters?
Yes. TigerOps monitors Standard, Premium, and Dedicated Event Hubs clusters. Dedicated clusters expose additional capacity unit metrics that TigerOps tracks alongside the standard namespace metrics.
How does TigerOps track consumer offset lag for Event Hubs?
TigerOps reads the IncomingMessages and OutgoingMessages metrics from Azure Monitor and computes lag as the difference between producer and consumer sequence numbers per partition. This approach works for all SDK consumers including Apache Kafka protocol consumers.
Does TigerOps support the Kafka protocol endpoint on Event Hubs?
Yes. Azure Event Hubs exposes a Kafka-compatible endpoint for Standard and Premium tiers. TigerOps can monitor Event Hubs used as a Kafka broker replacement using the same consumer lag tracking mechanism.
How does capture monitoring work?
When Event Hubs Capture is enabled, TigerOps monitors the CapturedMessages and CapturedBytes metrics alongside the CaptureBacklog metric that shows how many events are waiting to be written to storage. Capture write failures are surfaced as alerts.
Can I monitor multiple namespaces in one TigerOps workspace?
Yes. TigerOps supports monitoring multiple Event Hubs namespaces, across different Azure subscriptions and regions, in a single workspace. Dashboards can be filtered by namespace, region, or custom tags.
Keep Your Event Hubs Pipeline Running at Full Speed
Partition throughput, consumer lag, and capture monitoring for Azure Event Hubs. Connect in 5 minutes.