Event Hubs namespace nothing is publishing to
An Event Hubs namespace with no events in or out over the window, holding no retained data and no capture backlog.
Why it happens
An Event Hubs namespace bills its base unit hourly on every tier: a Dedicated capacity unit is about $5,000 a month, a Premium processing unit about $750, a Standard throughput unit about $22 and a Basic one about $11, charged whether or not a single event is published. A namespace cannot be stopped, so the only way to stop the charge is to delete it, and that destroys every event hub and consumer group along with any events still retained. The rule reports a namespace only when nothing was published or read across the whole window, when the hubs are holding no data, and when nothing is waiting to be written to storage by Capture. A namespace can retain events for up to 90 days on Premium, so one that has been silent for a week can still be holding data, and that is reported as a reason not to act rather than ignored.
What the agent does about it
An Event Hubs namespace with no events in or out over the window, holding no retained data and no capture backlog.
It will not fix this one
It reports this and takes no action. A check only earns the right to change something once the action behind it can re-read live state before it fires and knows the way back.
Related checks
Service Bus namespace nothing is sending to
A Service Bus namespace with no messages in or out over the window and nothing left sitting in its queues.
Idle virtual machine
A running VM whose CPU and network have been near zero for the whole window.
Oversized virtual machine
A running VM whose sustained peak fits comfortably inside the next size down.