Skip to content

Commit c586461

Browse files
committed
Fix broken links
1 parent bc5a51a commit c586461

File tree

2 files changed

+3
-6
lines changed

2 files changed

+3
-6
lines changed

articles/logic-apps/logic-apps-exception-handling.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,8 +3,6 @@ title: Handle errors and exceptions in workflows
33
description: How to handle errors and exceptions that happen in automated tasks and workflows created by using Azure Logic Apps.
44
services: logic-apps
55
ms.suite: integration
6-
author: dereklee
7-
ms.author: deli
86
ms.reviewer: estfan, laveeshb, azla
97
ms.topic: how-to
108
ms.custom: engagement-fy23

articles/sentinel/monitor-automation-health.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -105,19 +105,18 @@ For **Playbook was triggered**, you may see the following statuses:
105105
106106
## Get the complete automation picture
107107
108-
Microsoft Sentinel's health monitoring table allows you to track the triggering of playbooks, but to monitor what happens inside your playbooks and their results when they're run, you must also turn on **Azure Logic Apps diagnostics**.
108+
Microsoft Sentinel's health monitoring table allows you to track the triggering of playbooks, but to monitor what happens inside your playbooks and their results when they're run, you must also [turn on diagnostics in Azure Logic Apps](../logic-apps/monitor-workflows-collect-diagnostic-data.md) to ingest the following events to the *AzureDiagnostics* table:
109109
110-
By [enabling Azure Logic Apps diagnostics](../logic-apps/monitor-workflows-collect-diagnostic-data.md#set-up-azure-monitor-logs), you'll ingest the following events to the *AzureDiagnostics* table:
111110
- {Action name} started
112111
- {Action name} ended
113112
- Workflow (playbook) started
114113
- Workflow (playbook) ended
115114
116115
These added events will give you additional insights into the actions being taken in your playbooks.
117116
118-
### Turn on Logic Apps diagnostics
117+
### Turn on Azure Logic Apps diagnostics
119118
120-
For each playbook you are interested in monitoring, [follow these steps](../logic-apps/monitor-workflows-collect-diagnostic-data.md#set-up-azure-monitor-logs). Make sure to select **Send to Log Analytics workspace** as your log destination, and choose your Microsoft Sentinel workspace.
119+
For each playbook you are interested in monitoring, [enable Log Analytics for your logic app](../logic-apps/monitor-workflows-collect-diagnostic-data.md). Make sure to select **Send to Log Analytics workspace** as your log destination, and choose your Microsoft Sentinel workspace.
121120
122121
### Correlate Microsoft Sentinel and Azure Logic Apps logs
123122

0 commit comments

Comments
 (0)