Skip to content

Commit a648f92

Browse files
Merge pull request #232496 from AaronMaxwell/aaronmax-bulk-ms-author-update-3
removing authors set by docfx.json
2 parents 7ba16a8 + 818a33c commit a648f92

10 files changed

+7
-24
lines changed

articles/azure-monitor/alerts/alerts-troubleshoot-log.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: Troubleshoot log alerts in Azure Monitor | Microsoft Docs
33
description: Common issues, errors, and resolutions for log alert rules in Azure.
4-
author: yanivlavi
5-
ms.author: yalavi
64
ms.topic: conceptual
75
ms.date: 2/23/2022
6+
ms.reviewer: yalavi
87
---
98
# Troubleshoot log alerts in Azure Monitor
109

articles/azure-monitor/alerts/alerts-troubleshoot-metric.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: Frequently asked questions about Azure Monitor metric alerts
33
description: Common issues with Azure Monitor metric alerts and possible solutions.
4-
author: harelbr
5-
ms.author: harelbr
64
ms.topic: troubleshooting
75
ms.date: 8/31/2022
86
ms:reviwer: harelbr

articles/azure-monitor/alerts/alerts-troubleshoot.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: Troubleshooting Azure Monitor alerts and notifications
33
description: Common issues with Azure Monitor alerts and possible solutions.
4-
author: ofirmanor
5-
ms.author: ofmanor
64
ms.topic: reference
75
ms.date: 2/23/2022
86
ms.reviewer: ofmanor

articles/azure-monitor/alerts/alerts-understand-migration.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,7 @@ description: Understand how the alerts migration works and troubleshoot problems
44
ms.topic: conceptual
55
ms.custom: ignite-2022
66
ms.date: 2/23/2022
7-
ms.author: yalavi
8-
author: yalavi
7+
ms.reviewer: yalavi
98
---
109
# Understand migration options to newer alerts
1110

articles/azure-monitor/alerts/alerts-using-migration-tool.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,9 @@
11
---
22
title: Migrate Azure Monitor alert rules
33
description: Learn how to use the voluntary migration tool to migrate your classic alert rules.
4-
author: yanivlavi
5-
ms.author: yalavi
64
ms.topic: conceptual
75
ms.date: 2/23/2022
6+
ms.reviewer: yalavi
87
---
98
# Use the voluntary migration tool to migrate your classic alert rules
109

articles/azure-monitor/alerts/alerts-webhooks.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,6 @@
11
---
22
title: Call a webhook with a classic metric alert in Azure Monitor
33
description: Learn how to reroute Azure metric alerts to other, non-Azure systems.
4-
author: harelbr
5-
ms.author: harelbr
64
ms.topic: conceptual
75
ms.date: 2/23/2022
86
ms.reviewer: harelbr

articles/azure-monitor/alerts/itsmc-dashboard-errors.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: Connector status errors in the ITSMC dashboard
33
description: Learn about common errors that exist in the IT Service Management Connector dashboard.
44
ms.topic: conceptual
5-
author: nolavime
6-
ms.author: nolavime
75
ms.date: 2/23/2022
86
ms.reviewer: nolavime
97

articles/azure-monitor/alerts/itsmc-dashboard.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: Investigate errors by using the ITSMC dashboard
33
description: Learn how to use the IT Service Management Connector dashboard to investigate errors.
44
ms.topic: conceptual
5-
author: nolavime
6-
ms.author: nolavime
75
ms.date: 2/23/2022
86
ms.reviewer: nolavime
97

articles/azure-monitor/alerts/itsmc-resync-servicenow.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: How to manually fix ServiceNow sync problems
33
description: Reset the connection to ServiceNow so alerts in Microsoft Azure can again call ServiceNow
44
ms.topic: conceptual
5-
author: nolavime
6-
ms.author: nolavime
75
ms.date: 03/30/2022
86
ms.reviewer: nolavime
97

articles/azure-monitor/alerts/itsmc-troubleshoot-overview.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,8 +2,6 @@
22
title: Troubleshoot problems in ITSMC
33
description: Learn how to resolve common problems in IT Service Management Connector.
44
ms.topic: conceptual
5-
author: nolavime
6-
ms.author: nolavime
75
ms.date: 2/23/2022
86
ms.reviewer: nolavime
97

@@ -95,17 +93,17 @@ The following sections identify common symptoms, possible causes, and resolution
9593

9694
**Cause**: There can be several reasons for this:
9795

98-
* Templates are not shown as a part of the action definition dropdown and an error message is shown: "Can't retrieve the template configuration, see the connector logs for more information."
99-
* Values are not shown in the dropdowns of the default fields as a part of the action definition and an error message is shown: "No values found for the following fields: \<field names\>."
100-
* Incidents/Events are not created in ServiceNow.
96+
* Templates aren't shown as a part of the action definition dropdown and an error message is shown: "Can't retrieve the template configuration, see the connector logs for more information."
97+
* Values aren't shown in the dropdowns of the default fields as a part of the action definition and an error message is shown: "No values found for the following fields: \<field names\>."
98+
* Incidents/Events aren't created in ServiceNow.
10199

102100
**Resolution**:
103101
* [Sync the connector](itsmc-resync-servicenow.md).
104102
* Check the [dashboard](itsmc-dashboard.md) and review the errors in the section for connector status. Then review the [common errors and their resolutions](itsmc-dashboard-errors.md)
105103

106104
### In the incidents received from ServiceNow, the configuration item is blank
107105
**Cause**: There can be several reasons for this:
108-
* The alert is not a log alert. Configuration items are only supported by log alerts.
106+
* The alert isn't a log alert. Configuration items are only supported by log alerts.
109107
* The search results do not include the **Computer** or **Resource** column.
110108
* The values in the configuration item field do not match an entry in the CMDB.
111109

0 commit comments

Comments
 (0)