Commands icon
If icon
SlackIncomingWebhook icon
Schedule icon

Microsoft Azure Event Hubs Ingress and Egress Throttled Requests Sentinel

Monitors Azure Event Hubs namespace for ingress and egress throttled requests to prevent message drop and consumer lag.

Categories
CloudInfrastructure

How it works

This workflow connects to the Azure CLI container using an Azure Service Principal and queries Azure Monitor metrics for ThrottledRequests against the specified Event Hubs namespace. In Azure Event Hubs, requests are throttled when ingress or egress rates exceed allocated Throughput Units (Standard tier) or Processing Units (Premium tier). When throttled events are detected, the workflow parses the telemetry with jq and routes an urgent incident alert to Slack.

What you get

  • Real-time detection of data streaming bottlenecks and rate-limiting.
  • Prevents silent telemetry loss or message queuing backlogs.
  • Actionable capacity alerts indicating when to scale Throughput Units.

Who it's for

  • Event Streaming and Kafka Platform Engineers running Azure Event Hubs.
  • Cloud Infrastructure and SRE teams managing real-time data pipelines.

Why orchestrate this with Kestra

  • Automated Multi-Cloud Telemetry: Periodically poll Azure Monitor alongside AWS, GCP, and Kafka workloads.
  • Zero-Friction Authentication: Authenticate seamlessly using Kestra secrets for Service Principal credentials.
  • Instant Alert Routing: Direct formatted incident notifications to on-call response channels.

Prerequisites

  • Azure Service Principal with Monitoring Reader role on the target resource group.
  • Secrets AZURE_CLIENT_ID, AZURE_CLIENT_SECRET, AZURE_TENANT_ID, and SLACK_WEBHOOK configured in Kestra.

Quick start

  1. Import the blueprint into your Kestra instance.
  2. Provide your Azure Subscription ID, Resource Group, and Event Hubs Namespace name.
  3. Trigger the flow manually or enable the periodic schedule.

How to extend

  • Add an automated auto-scale step to dynamically increase Throughput Units via Azure CLI when throttling persists.
  • Correlate with downstream consumer group lag metrics.

Links

See How

New to Kestra?

Use blueprints to kickstart your first workflows.