Skip to content

Commit 8cc3cab

Browse files
authored
Update azure-event-hubs-source.md
Removing IP restriction messaging. Improvements are made to support it.
1 parent 9624cb0 commit 8cc3cab

File tree

1 file changed

+0
-1
lines changed

1 file changed

+0
-1
lines changed

docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,6 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1616

1717
:::note
1818
- Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method supports a throughput limit of 1MB/s (86GB/day) per named Event Hub egress rate. If you require higher throughput, we recommend using the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source).
19-
- The only caveat is this Cloud-to-Cloud collection method supports IP restrictions and the [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/) does not. If you require higher throughput and have IP address restrictions on Event Hubs, consider splitting your Event Hubs into smaller namespaces, each staying within the 1MB/s (86GB/day) limit, and create a Cloud-to-Cloud collection method for each namespace.
2019
:::
2120

2221
<img src={useBaseUrl('img/send-data/azure-event-hub.svg')} alt="icon" width="40"/>

0 commit comments

Comments
 (0)