Skip to content

Commit 6627bcd

Browse files
committed
preliminary adds
1 parent 90af9f0 commit 6627bcd

File tree

2 files changed

+55
-0
lines changed

2 files changed

+55
-0
lines changed

articles/azure-vmware/index.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -223,6 +223,8 @@ additionalContent:
223223
url: using-run-command.md
224224
- text: Configure VMware Syslogs
225225
url: configure-vmware-syslogs.md
226+
- text: Send syslogs to log management solutions via Azure Logic Apps
227+
url: logs-via-logic-app.md
226228
- text: Configure Alerts
227229
url: configure-alerts-for-azure-vmware-solution.md
228230
- text: Arc-enabled Azure VMware Solution
Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
title: Send VMware syslogs to log management server using Azure Logic Apps
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+
ms.topic: how-to
5+
ms.service: azure-vmware
6+
ms.date: 3/21/2025
7+
ms.custom: engagement-fy25
8+
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.
10+
11+
---
12+
13+
# Send VMware syslogs to log management server using Azure Logic Apps
14+
15+
Azure Logic Apps enables you to automate workflows by integrating various Azure services and third-party applications. You can use Logic Apps to collect and forward VMware syslogs from your Azure VMware Solution private cloud to any log management service of your choice. This allows for centralized log storage, analysis, and monitoring across your preferred tools.
16+
17+
In this article, learn how to configure an Azure Logic Apps workflow to capture VMware syslogs and send them to your chosen log management service.
18+
19+
## Prerequisites
20+
21+
Make sure you have an Azure VMware Solution private cloud set up that is streaming its syslogs to an Azure Event Hubs instance. For more information, see
22+
[Configure VMware syslogs - Stream to Microsoft Azure Event Hubs](https://learn.microsoft.com/en-us/azure/azure-vmware/configure-vmware-syslogs#stream-to-microsoft-azure-event-hubs).
23+
24+
## Create an Azure Logic Apps instance
25+
26+
1. From your Azure Portal, select **Create a resource**, then search for **Logic App**. Find the one called **Logic App**, select **Create**, then click **Logic App**.
27+
28+
2. Select the Hosting plan that makes the most sense for your consumption needs. In most cases, the **Workflow Service Plan** should suffice.
29+
30+
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 Pricing plan is **Workflow Standard WS1 (210 total ACU, 3.5 Gb memory, 1 vCPU)** which should handle large workloads. This can always adjust this later, as needed. After filing these details, select **Review + create**.
31+
32+
4. Review the details of the Logic App instance. Select **Create**. This will initialize the deployment of the Logic App instance. Once complete, the deployment status will read "Your deployment is complete".
33+
34+
35+
## Set up the Azure Logic App workflow
36+
37+
1. Once deployed, navigate to the Logic App instance. Select **Workflows**, then click on **Workflows**.
38+
39+
2. Select **Add**, then click on **Add from Template**. This will take you to the template catalog available in Azure Logic Apps.
40+
41+
3. In here, search for **Azure VMware Solution**. Click on the option called **Azure VMware Solution: Export private cloud logs to log management solution**.
42+
43+
4. On the right hand pane, select **Use this template** at the bottom of the screen. Give the workflow a name and select **Stateful** for State type.
44+
45+
5. Next, connect the Event Hub that houses the Azure VMware Solution logs to this Logic App instance. To do so, click **Connect**. Provide a name for Connection Name, Authentication Type will remain Access Key. For Connection String, you need to retrieve the Connection String from the Event Hub instance you intend to use.
46+
a. In a separate brower tab, open the Event Hub instance that contains the log messages.
47+
b. Select **Settings**, then click on **Shared access policies**.
48+
c. Select **RootManagerSharedAccessKey** and click on the copy icon next to **Primary connection string**.
49+
d. Navigate back to the browser tab with the Logic App and paste what you just copied into the **Connection String** field. Click **Add Connection**, then click **Next**.
50+
e. Add the name of the event hub instance under **Event hub name**. The exact name of the Event hub can be found under **Entities**, then **Event Hubs** in your Event Hub tab.
51+
f. Add the URI of the log server you intend to use under **Log destination URI**. Click **Next**, then click **Create**. This will now save the workflow
52+
53+

0 commit comments

Comments
 (0)