Azure Government is available to US government entities to purchase physically and network isolated instances of Azure Government from a Licensed Azure Government Service Provider or Partner with no up-front financial commitment or fee. Or, you can sign up for a free Azure Government Trial.
Important: The price in R$ is merely a reference; this is an international transaction and the final price is subject to exchange rates and the inclusion of IOF taxes and an eNF will not be issued.
Azure Germany is available to customers and partners doing business in the European Union (EU), European Free Trade Association (EFTA) and United Kingdom (UK), and provides data residency in Germany with additional levels of control and data protection. You can also sign up for a free Azure Germany trial.
Event Hubs, is designed to ingest millions of events per second so you can process and analyse massive amounts of data from connected devices and applications. See what else it does
|Ingress events||$- per million events||$- per million events||Included|
|Throughput unit (1 MB/s ingress, 2 MB/s egress)||$-||$-||Included|
|Message size||256 KB||256 KB||1 MB|
|Consumer groups||1 – Default||20||20|
|Maximum throughput units||20||20**||1 CU≈200|
|Brokered connections||100 included||1,000 included||100K included|
|Additional Brokered connections||–|
|Message Retention||1 day included||1 day included***||Up to 7 days included|
An ingress event is a unit of data of 64 KB or less. Each one is a billable event. Larger messages are billed in multiples of 64 KB. For example, 8 KB is billed as one event, but a 96 KB message is billed as two events.
Events consumed from an Event Hub, as well as management operations and “control calls” such as checkpoints, are not counted as billable ingress events, but accrue to the throughput unit allowance.
Throughput units are explicitly selected by the customer, either through the Azure portal or Event Hub management APIs. Throughput units apply to all Event Hubs in a namespace, and each throughput unit entitles the namespace to the following capabilities:
- Up to 1 MB per second of ingress events (= events sent into an Event Hub), but no more than 1,000 ingress events, management operations or control API calls per second.
- Up to 2 MB per second of egress events (= events consumed from an Event Hub).
- Up to 84 GB of event storage (sufficient for the default 24-hour retention period).
Throughput units are billed hourly, based on the maximum number of units selected during this hour.
If the total ingress throughput or the total ingress event rate across all Event Hubs in a namespace exceeds the aggregate throughput unit allowances, senders will get throttled and receive errors indicating that the ingress quota has been exceeded.
If the total egress throughput or the total event egress rate across all Event Hubs in a namespace exceeds the aggregate throughput unit allowances, receivers will get throttled and receive errors indicating that the egress quota has been exceeded. Ingress and egress quotas are enforced separately, so that no sender can cause event consumption to slow down, nor a receiver can prevent events from being sent into Event Hub.
Note that the throughput unit selection is independent of the number of Event Hub Partitions (sometimes referred to as shards in similar systems). While each Partition offers a maximum throughput of 1 MB per second, 1,000 events per second ingress, and 2 MB per second egress, there is no fixed charge for the partitions themselves. The charge is for the aggregate throughput units on all Event Hubs in a namespace. With this, customers can create enough Partitions to support the anticipated maximum load for their systems, without incurring any throughput unit charges until the Event load on the system actually requires higher throughput numbers, and without having to change the structure and architecture of their systems as the load on the system increases.
Example: Suppose you chose 8 throughput unit on a namespace and create a single Event Hub with 32 partitions. If all partitions in this Event Hub see even load, each partition gets approximately 0.25 MB/s ingress throughput for a total aggregate throughput of 8 MB/s. If a single partition sees a usage spike to 1 MB/s, while 8 other partitions only see half their peak load (0.125 MB/s), no throttling will occur. However, if the single partition spiked beyond 1 MB/s, it will get throttled due to the per-partition limit, even if the aggregate throughput of all partitions is below 8 MB/s.
Yes. Basic and Standard tier Namespaces can have a maximum of 20 throughput units. You can request a larger number of throughput units for a Standard tier by filing a support ticket. Note that the immediate availability of additional capacity above 20 throughput units per Azure Subscription is not assured. We recommend that customers anticipating a need for more than 20 throughput units of Event Hub capacity contact us to discuss requirements as early as possible in the planning cycle. Additional throughput units are available in blocks of twenty on a committed purchase basis.
We provide a maximum of a 7-day retention period upon general availability. Note that Event Hubs are not intended as a permanent data store. Retention periods > 24 hours are intended for scenarios where it is convenient to replay an event stream into the same systems, to for example train or verify a new machine learning model on existing data.
In many cases, yes. If the size of the total number of stored events exceeds the storage allowance for the number of selected throughput units (84 GB per throughput unit), the size that exceeds the allowance is charged at the regular Azure Blob storage rates. The storage allowance in each throughput unit covers all storage costs for retention periods of 24 hours (the default), even if the throughput unit is used to the maximum Ingress allowance.
The total size of all stored events, including any internal overhead for event headers or on disk storage structures in all Event Hubs in a namespace is measured throughout the day. At the end of the day, the peak storage size is calculated. The daily storage allowance is calculated based on the minimum number of throughput units that were selected during the day (each throughput unit provides an allowance of 84 GB). If the total size exceeds the daily storage allowance, the excess storage is billed using Azure blob storage rates (at the Locally Redundant Storage rate).
There are no connection charges for sending events using HTTP, regardless of the number of sending systems/devices. AMQP connections are metered, but the first 100 concurrent connections are free for every Basic Event Hubs namespace, and the first 1,000 concurrent connections per subscription are free for Standard Event Hubs. These allowances cover most receive scenarios and many service to service scenarios. Brokered Connections charges usually only become significant if you plan to use AMQP on a large number of clients, i.e. to achieve more efficient event streaming or to enable bi-directional communication (Internet of Things Command & Control scenarios). Please refer to the Service Bus Connections pricing information for details on what constitutes a Brokered Connection and how they are metered.
Event Hubs Capture is enabled when any Event Hub in the namespace has the Capture feature enabled. Capture is billed hourly per purchased throughput unit. As the throughput unit count is increased or decreased, Event Hubs Capture billing will reflect these changes in whole hour increments.
Event Hubs Capture does not affect egress rates for Event Hubs throughput units. You can still read at the full throughput unit rate of 2000 events per second/2 MBps per throughput unit.
Event Hubs Capture uses a storage account you provide on a schedule you provide. Because this is your storage account any usage charges for this storage account will be billed to your Azure subscription. The shorter your Capture Window the more frequent storage transactions will occur.