Skip to content

Commit 7fdb232

Browse files
authored
Update azure-logic-app.md
1 parent f064830 commit 7fdb232

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

docs/integrations/microsoft-azure/azure-logic-app.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -14,7 +14,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl';
1414

1515
For Azure Logic App, you can collect the following logs and metrics:
1616

17-
* **Workflow runtime diagnostic events**. To learn more about the different resource log category types and schemas collected for Azure Logic App, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/key-vault/general/monitor-key-vault-reference#resource-logs).
17+
* **Workflow runtime diagnostic events**. To learn more about the different resource log category types and schemas collected for the Azure Logic App, refer to the [Azure documentation](https://learn.microsoft.com/en-gb/azure/key-vault/general/monitor-key-vault-reference#resource-logs).
1818
* **Integration Account track events**. To learn more about the different tracking schemas for integration accounts, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/logic-apps/tracking-schemas-as2-x12-custom).
1919
* **Logic App Workflow Metrics**. These metrics are available in [Microsoft.Logic/Workflows](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-logic-workflows-metrics) namespace.
2020
* **Integration Account Metrics**. These metrics are available in [Microsoft.Logic/IntegrationServiceEnvironments](https://learn.microsoft.com/en-us/azure/azure-monitor/reference/supported-metrics/microsoft-logic-integrationserviceenvironments-metrics) namespace.
@@ -30,29 +30,29 @@ Azure service sends monitoring data to Azure Monitor, which can then [stream dat
3030

3131
You must explicitly enable diagnostic settings for each Logic App and integration account you want to monitor. You can forward logs to the same event hub provided they satisfy the limitations and permissions as described [here](https://learn.microsoft.com/en-us/azure/azure-monitor/essentials/diagnostic-settings?tabs=portal#destination-limitations).
3232

33-
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/LogicApp/Logs`, `Azure/LogicApp/Metrics`. The below setup instructions applies to both Consumption and Standard plan based Logic Apps.
33+
When you configure the event hubs source or HTTP source, plan your source category to ease the querying process. A hierarchical approach allows you to make use of wildcards. For example: `Azure/LogicApp/Logs`, `Azure/LogicApp/Metrics`. The setup instructions below apply to both Consumption and Standard plan-based Logic Apps.
3434

3535
### Configure metrics collection
3636

37-
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, on to an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
37+
In this section, you will configure a pipeline for shipping metrics from Azure Monitor to an Event Hub, onto an Azure Function, and finally to an HTTP Source on a hosted collector in Sumo Logic.
3838

3939
1. Create a hosted collector and tag the `tenant_name` field. You can get the tenant name using the instructions [here](https://learn.microsoft.com/en-us/azure/active-directory-b2c/tenant-management-read-tenant-name#get-your-tenant-name). <br/><img src={useBaseUrl('img/integrations/microsoft-azure/Azure-Storage-Tag-Tenant-Name.png')} alt="Azure Tag Tenant Name" style={{border: '1px solid gray'}} width="500" />
4040
1. [Configure an HTTP Source](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-1-configure-an-http-source).
4141
1. [Configure and deploy the ARM Template](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-2-configure-azure-resources-using-arm-template).
42-
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform below steps for each Logic App and integration account that you want to monitor.
43-
* Choose `Stream to an event hub` as destination.
42+
1. [Export metrics to Event Hub](/docs/send-data/collect-from-other-data-sources/azure-monitoring/collect-metrics-azure-monitor/#step-3-export-metrics-for-a-particular-resource-to-event-hub). Perform the steps below for each Logic App and integration account that you want to monitor.
43+
* Choose `Stream to an event hub` as the destination.
4444
* Select `AllMetrics`.
45-
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
45+
* Use the Event hub namespace created by the ARM template in Step 2 above. You can create a new Event hub or use the one created by the ARM template. You can use the default policy `RootManageSharedAccessKey` as the policy name.
4646

4747
### Configure logs collection
4848

4949
In this section, you will configure a pipeline for shipping diagnostic logs from Azure Monitor to an Event Hub.
5050

5151
1. To set up the Azure Event Hubs source in Sumo Logic, refer to [Azure Event Hubs Source for Logs](/docs/send-data/collect-from-other-data-sources/azure-monitoring/ms-azure-event-hubs-source/).
52-
2. To create the Diagnostic settings in Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/logic-apps/monitor-workflows-collect-diagnostic-data?tabs=consumption#add-a-diagnostic-setting) for Logic App resource and [this documentation](https://learn.microsoft.com/en-us/azure/logic-apps/monitor-b2b-messages-log-analytics#set-up-azure-monitor-logs) for integration accounts. Perform below steps for each Logic App that you want to monitor.
52+
2. To create the Diagnostic settings in the Azure portal, refer to the [Azure documentation](https://learn.microsoft.com/en-us/azure/logic-apps/monitor-workflows-collect-diagnostic-data?tabs=consumption#add-a-diagnostic-setting) for Logic App resource and [this documentation](https://learn.microsoft.com/en-us/azure/logic-apps/monitor-b2b-messages-log-analytics#set-up-azure-monitor-logs) for integration accounts. Perform the steps below for each Logic App that you want to monitor.
5353
* Choose `Stream to an event hub` as the destination.
54-
* Select `allLogs` for Logic App or `IntegrationAccountTrackingEvents` for integration account.
55-
* Use the Event hub namespace and Event hub name configured in previous step in destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
54+
* Select `allLogs` for the Logic App or `IntegrationAccountTrackingEvents` for the integration account.
55+
* Use the Event hub namespace and Event hub name configured in the previous step in the destination details section. You can use the default policy `RootManageSharedAccessKey` as the policy name.
5656

5757
## Troubleshooting
5858

0 commit comments

Comments
 (0)