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
Copy file name to clipboardExpand all lines: articles/azure-vmware/logs-via-logic-app.md
+4-5Lines changed: 4 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Send VMware syslogs to log management server using Azure Logic Apps
3
3
description: Learn how to use Azure Logic Apps to collect and send VMware syslogs from your Azure VMware Solution private cloud to any log management service of your choice.
4
4
ms.topic: how-to
5
5
ms.service: azure-vmware
6
-
ms.date: 3/21/2025
6
+
ms.date: 4/8/2025
7
7
ms.custom: engagement-fy25
8
8
9
9
#Customer intent: As an Azure service administrator, I want to use Azure Logic Apps to send VMware syslogs from my Azure VMware Solution private cloud to my preferred log management service for centralized logging and analysis.
@@ -31,7 +31,6 @@ Make sure you have an Azure VMware Solution private cloud set up that is streami
31
31
32
32
:::image type="content" source="media/logs-to-logic-app/logs-to-logic-app-2.png" alt-text="Screenshot showing which hosting option of Azure Logic Apps to select." border="false" lightbox="media/logs-to-logic-app/logs-to-logic-app-2.png":::
33
33
34
-
35
34
3. Enter the Subscription you intend to use, the Resource Group chosen to house this instance. Give it a name and select a region. The default Windows plan is **Workflow Standard WS1 (210 total ACU, 3.5 Gb memory, 1 vCPU)** which should be enough to handle log volumes from large workloads. This can always be adjusted later, as needed. After filing these details, select **Review + create**.
36
35
37
36
:::image type="content" source="media/logs-to-logic-app/logs-to-logic-app-3.png" alt-text="Screenshot showing the fields that need to be populated when creating an Azure Logic App." border="false" lightbox="media/logs-to-logic-app/logs-to-logic-app-3.png":::
@@ -58,15 +57,15 @@ Make sure you have an Azure VMware Solution private cloud set up that is streami
58
57
59
58
:::image type="content" source="media/logs-to-logic-app/logs-to-logic-app-8.png" alt-text="Screenshot showing the Event Hubs connection portion of the Azure VMware Solution template." border="false" lightbox="media/logs-to-logic-app/logs-to-logic-app-8.png":::
60
59
61
-
a. In a separate brower tab, open the Event Hub instance that contains the log messages. Select **Settings**, then click on **Shared access policies**. Select **RootManagerSharedAccessKey** and click on the copy icon next to **Primary connection string**.
60
+
a. In a separate brower tab, open the Event Hub instance that contains the log messages. Select **Settings**, then click on **Shared access policies**. Select **RootManagerSharedAccessKey** and click on the copy icon next to **Primary connection string**.
62
61
63
62
:::image type="content" source="media/logs-to-logic-app/logs-to-logic-app-9.png" alt-text="Screenshot showing the Primary connection string on Azure Event Hub." border="false" lightbox="media/logs-to-logic-app/logs-to-logic-app-9.png":::
64
63
65
-
b. Navigate back to the browser tab with the Logic App and paste what you just copied into the **Connection String** field. Click **Add Connection**.
64
+
b. Navigate back to the browser tab with the Logic App and paste what you just copied into the **Connection String** field. Click **Add Connection**.
66
65
67
66
:::image type="content" source="media/logs-to-logic-app/logs-to-logic-app-10.png" alt-text="Screenshot showing the pasting of the Primary connection string on Azure Logic Apps template." border="false" lightbox="media/logs-to-logic-app/logs-to-logic-app-10.png":::
68
67
69
-
c. If added successfully, the Status for the Event Hub should read **Connected**. At this point, click **Next** to proceed forward.
68
+
c. If added successfully, the Status for the Event Hub should read **Connected**. At this point, click **Next** to proceed forward.
0 commit comments