Skip to content

Commit 77e27ba

Browse files
authored
Merge pull request #80877 from xurui203/patch-25
Update event-hubs-capture-overview.md
2 parents 31bed14 + f853e9f commit 77e27ba

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

articles/event-hubs/event-hubs-capture-overview.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -49,6 +49,8 @@ Note that the date values are padded with zeroes; an example filename might be:
4949
https://mystorageaccount.blob.core.windows.net/mycontainer/mynamespace/myeventhub/0/2017/12/08/03/03/17.avro
5050
```
5151

52+
In the event that your Azure storage blob is temporarily unavailable, Event Hubs Capture will retain your data for the data retention period configured on your event hub and back fill the data once your storage account is available again.
53+
5254
### Scaling to throughput units
5355

5456
Event Hubs traffic is controlled by [throughput units](event-hubs-scalability.md#throughput-units). A single throughput unit allows 1 MB per second or 1000 events per second of ingress and twice that amount of egress. Standard Event Hubs can be configured with 1-20 throughput units, and you can purchase more with a quota increase [support request][support request]. Usage beyond your purchased throughput units is throttled. Event Hubs Capture copies data directly from the internal Event Hubs storage, bypassing throughput unit egress quotas and saving your egress for other processing readers, such as Stream Analytics or Spark.
@@ -133,6 +135,8 @@ Apache Avro has complete Getting Started guides for [Java][Java] and [Python][Py
133135

134136
Event Hubs Capture is metered similarly to throughput units: as an hourly charge. The charge is directly proportional to the number of throughput units purchased for the namespace. As throughput units are increased and decreased, Event Hubs Capture meters increase and decrease to provide matching performance. The meters occur in tandem. For pricing details, see [Event Hubs pricing](https://azure.microsoft.com/pricing/details/event-hubs/).
135137

138+
Note that Capture does not consume egress quota as it is billed separately.
139+
136140
## Integration with Event Grid
137141

138142
You can create an Azure Event Grid subscription with an Event Hubs namespace as its source. The following tutorial shows you how to create an Event Grid subscription with an event hub as a source and an Azure Functions app as a sink: [Process and migrate captured Event Hubs data to a SQL Data Warehouse using Event Grid and Azure Functions](store-captured-data-data-warehouse.md).

0 commit comments

Comments
 (0)