You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As **Cloud-to-Cloud Event Hub source** supports logs, you can migrate your [ARM-based Azure Monitor Logs Collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source) (functions prefixed with SUMOAzureLogs). This source is available in all deployments, including FedRAMP.
11
+
As **Azure Event Hubs source** supports logs, you can migrate your [ARM-based Azure Monitor Logs Collection](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source) (functions prefixed with SUMOAzureLogs). This source is available in all deployments, including FedRAMP.
12
12
13
-
Cloud-to-Cloud sources have several advantages, including:
14
-
* Less overhead of maintenance and upgrades, since cloud-to-cloud sources are upgraded automatically for bug fixes.
15
-
* Lesser cost since the old collection method is used to create multiple resources such as storage accounts, application insights, and azure functions in your account while cloud-to-cloud sources are hosted in sumo logic infra. On the other hand, a cloud-to-cloud event hub source requires you to create only an event hub in your Azure account.
13
+
Azure Event Hubs source have several advantages, including:
14
+
* Less overhead of maintenance and upgrades, since Azure Event Hubs source are upgraded automatically for bug fixes.
15
+
* Lesser cost since the old collection method is used to create multiple resources such as storage accounts, application insights, and azure functions in your account while sources are hosted in Sumo Logic infra that requires you to create only an event hub in your Azure account.
16
16
17
17
## Step 1. Choose a migration strategy
18
18
19
19
Choose a migration strategy that is more convenient for you. Migration can be done in two ways:
20
20
21
21
### Strategy A. Existing event hub namespaces
22
22
23
-
If you want to continue using the existing **Event hubs namespaces** that are created by the ARM template, jump to the [Configuring Parameters](#step-2-configure-parameters-for-your-event-hub-cloud-to-cloud-sources) section in step 2.
23
+
If you want to continue using the existing **Event hubs namespaces** that are created by the ARM template, jump to the [Configuring Parameters](#step-2-configure-parameters-for-your-event-hub-sources) section in step 2.
24
24
25
25
The advantage of using the existing strategy is that you don’t have to recreate diagnostic settings in Azure Monitor for exporting the logs to the event hub.
26
26
@@ -30,15 +30,15 @@ You need to manually delete resources (starting with the prefix Sumo) and cannot
30
30
31
31
### Strategy B. Creating new event hub namespaces
32
32
33
-
If you want to create a new event hub namespace, see steps 1 to 3 in the [Vendor configuration](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source/#vendor-configuration) section. The advantage of using this strategy is you can simply delete the resource group where the ARM template was earlier deployed. This assumes you haven’t created any additional resources in the same resource group.
33
+
If you want to create a new event hub namespace, see steps 1 to 3 in the [Vendor configuration](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/#vendor-configuration) section. The advantage of using this strategy is you can simply delete the resource group where the ARM template was earlier deployed. This assumes you haven’t created any additional resources in the same resource group.
34
34
35
35
:::note
36
36
You need to first find out what all log types are exported to your event hub and recreate the diagnostic settings for the Azure services. Thus, we recommend creating new diagnostic settings for newer namespaces so that we can delete the older ones after verifying the new collection works without any latency.
37
37
:::
38
38
39
39
After choosing one of the above two strategies, you will now have an event hub namespace that has the logs flowing to it.
40
40
41
-
## Step 2. Configure parameters for your event hub cloud-to-cloud sources
41
+
## Step 2. Configure parameters for your event hub sources
42
42
43
43
1.**Create a shared access policy**. You can create it at the namespace level if you have multiple event hubs by selecting **Shared Access Policies** on the left menu of the **Event Hubs Namespace page**.<br/> 
44
44
2.**Create a consumer group**.
@@ -55,9 +55,9 @@ Creating **Consumer Groups** is needed only for the customers using the older ev
55
55
56
56
After completing the above steps, you will have **Azure Event Hubs Namespace**, **Event Hubs Instance Name**, **Shared Access Policy**, and **Consumer Group Name** - all four parameters are required for creating an event hub source.
For each of the event hubs present in your namespace, you need to create a cloud-to-cloud source. For more information, see [Creating Azure Event Hub Source](/docs/send-data/hosted-collectors/cloud-to-cloud-integration-framework/azure-event-hubs-source/#vendor-configuration) section.
60
+
For each of the event hubs present in your namespace, you need to create a Azure Event Hubs source. For more information, refer to the [Creating Azure Event Hub Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source).
61
61
62
62
:::note
63
63
We recommend giving the same source category so that your custom dashboards or apps require no changes. You can verify whether the data comes from your source using `1_source metadata`.
@@ -127,7 +127,7 @@ If your resource group contains only resources created by the older ARM template
127
127
128
128
## FAQ
129
129
130
-
#### After migrating to Cloud-to-Cloud, will the acquired data volume increase as compared to when configured with the previous ARM Template?
130
+
#### After migrating to Azure Event Hubs source, will the acquired data volume increase as compared to when configured with the previous ARM Template?
131
131
132
132
There won't be any change in data volume since these are the same logs we are just changing the collection method.
0 commit comments