Azure Event Hubs Namespace
Does ZopNight manage Azure Event Hubs Namespace?
Event Hubs namespaces reserve capacity by the hour (throughput units on Standard, processing units on Premium), billed whether events flow or not. ZopNight captures tier and throughput configuration via Resource Graph, compares 60 days of ingress and egress volume from Azure Monitor, and surfaces throughput rightsizing on over-provisioned namespaces.
Rules that fire on Azure Event Hubs Namespace
At a glance
| Field | Value |
|---|---|
| Scheduling notes | discovery and cost visibility only. |
Event Hubs is Azure’s big-data event-streaming service, billed by throughput units (Standard) or processing units (Premium) reserved per hour. Over-provisioned throughput on quiet namespaces is its main waste pattern.
Reserved throughput is the Event Hubs meter
An Event Hubs namespace reserves capacity per hour: throughput units on the Standard tier, processing units on Premium. The reservation bills around the clock at whatever count is configured, and event volume only matters when it exceeds the reservation. Under-use never shows up on the invoice except as waste. Auto-inflate can raise throughput units automatically to absorb a spike, but nothing walks them back down afterward; the ratchet turns one way.
Ingress and egress volume as the evidence
Discovered via Azure Resource Graph with tier and throughput configuration. Azure Monitor metrics over a 60-day lookback show ingress and egress volume, Cost Management billing attributes spend, and throughput rightsizing surfaces in review. Namespaces are not schedulable, since an event stream switched off overnight loses whatever producers emit while it is dark. Matching the reserved unit count to observed volume is where the saving actually is.
Quiet namespaces holding peak capacity
Waste concentrates in three shapes. Namespaces whose throughput units were raised for a launch or a backfill and never lowered once it passed. Premium processing units kept in non-production environments where Standard would comfortably carry the load. And dead namespaces from decommissioned pipelines, still reserving units every hour with no producers left on the other end. Two months of volume metrics cleanly separates all three from the namespaces genuinely earning their reservation.
Namespace tier and units in the portal
Azure portal → Event Hubs lists namespaces with their pricing tier. A namespace’s Scale settings show the current throughput or processing units, and the Overview charts for incoming and outgoing messages show whether that reservation has recently done any work.