From 3e2366ede662aa49b2d63e2d320951a12b4fabcc Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Wed, 16 Oct 2024 14:52:12 +0530 Subject: [PATCH 1/3] IP restrictions Note added --- .../azure-monitoring/ms-azure-event-hubs-source.md | 3 ++- .../azure-event-hubs-source.md | 3 ++- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md index a86df1fe6e..29c4078b22 100644 --- a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md +++ b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md @@ -8,7 +8,8 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; import ForwardToSiem from '/docs/reuse/forward-to-siem.md'; :::note -For higher data ingestion speed and scalability, this collection method is preferred over our similar [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source). +- For higher data ingestion speed and scalability, this collection method is preferred over our similar [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source). +- Azure Event Hubs for Logs does not support IP restrictions. We recommend using the [Azure Event Hubs cloud-to-cloud source collection method](docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source) if you require higher throughput and have IP address restrictions on Event Hubs. ::: The Azure Event Hubs Source provides a secure endpoint to receive data from Azure Event Hubs. It securely stores the required authentication, scheduling, and state tracking information. diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md index 2affd90ebd..512683a026 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md @@ -15,7 +15,8 @@ import ForwardToSiem from '/docs/reuse/forward-to-siem.md'; import useBaseUrl from '@docusaurus/useBaseUrl'; :::note -Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method has a supported throughput limit of 1MB/S (86GB/day) for a named Event Hub egress rate. 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/) if you require higher throughput. 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, then we recommend splitting your Event Hubs into smaller namespaces keeping within the 1MB/S (86GB/day) limit and create this Cloud-to-Cloud collection method for each namespace. +- Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method has a supported throughput limit of 1MB/S (86GB/day) for a named Event Hub egress rate. 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/) if you require higher throughput. +- 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, then we recommend splitting your Event Hubs into smaller namespaces keeping within the 1MB/S (86GB/day) limit and create this Cloud-to-Cloud collection method for each namespace. ::: icon From 1f37634b17b4f039068e36958302559e25b77207 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Wed, 16 Oct 2024 15:15:04 +0530 Subject: [PATCH 2/3] Update docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md --- .../azure-monitoring/ms-azure-event-hubs-source.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md index 29c4078b22..f27a2bbdd8 100644 --- a/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md +++ b/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source.md @@ -9,7 +9,7 @@ import ForwardToSiem from '/docs/reuse/forward-to-siem.md'; :::note - For higher data ingestion speed and scalability, this collection method is preferred over our similar [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source). -- Azure Event Hubs for Logs does not support IP restrictions. We recommend using the [Azure Event Hubs cloud-to-cloud source collection method](docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source) if you require higher throughput and have IP address restrictions on Event Hubs. +- Azure Event Hubs for Logs does not support IP restrictions. We recommend using the [Azure Event Hubs cloud-to-cloud source collection method](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source) if you require higher throughput and have IP address restrictions on Event Hubs. ::: The Azure Event Hubs Source provides a secure endpoint to receive data from Azure Event Hubs. It securely stores the required authentication, scheduling, and state tracking information. From dfa8cd42cee9d33fa983035842bdf151cfe99e83 Mon Sep 17 00:00:00 2001 From: Jagadisha V <129049263+JV0812@users.noreply.github.com> Date: Thu, 17 Oct 2024 11:51:02 +0530 Subject: [PATCH 3/3] Update docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- .../azure-event-hubs-source.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md index 512683a026..8bddb1d833 100644 --- a/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md +++ b/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source.md @@ -15,8 +15,8 @@ import ForwardToSiem from '/docs/reuse/forward-to-siem.md'; import useBaseUrl from '@docusaurus/useBaseUrl'; :::note -- Collecting data from Azure Event Hubs using this Cloud-to-Cloud collection method has a supported throughput limit of 1MB/S (86GB/day) for a named Event Hub egress rate. 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/) if you require higher throughput. -- 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, then we recommend splitting your Event Hubs into smaller namespaces keeping within the 1MB/S (86GB/day) limit and create this Cloud-to-Cloud collection method for each namespace. +- 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). +- 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. ::: icon