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/automation/how-to/region-mappings.md
+13-11Lines changed: 13 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,14 +6,16 @@ ms.service: automation
6
6
ms.subservice: process-automation
7
7
author: mgoedtel
8
8
ms.author: magoedte
9
-
ms.date: 05/20/2019
9
+
ms.date: 04/23/2020
10
10
ms.topic: conceptual
11
11
manager: carmonm
12
12
---
13
13
14
14
# Workspace mappings
15
15
16
-
When enabling solutions like Update Management, Change Tracking and Inventory, or Start/Stop VMs during off hours, only certain regions are supported for linking a Log Analytics workspace and an Automation account. This mapping only applies to the Automation account and the Log Analytics workspace. The resources reporting to your Automation account or Log Analytics workspace can reside in other regions.
16
+
When enabling Update Management, Change Tracking and Inventory, or Start/Stop VMs during off-hours, only certain regions are supported for linking a Log Analytics workspace and an Automation account in your subscription. This mapping only applies to the Automation account and the Log Analytics workspace. The Log Analytics workspace and Automation account must be in the same subscription, but can be in different resource groups deployed to the same region.
17
+
18
+
For further information, see [Log Analytics workspace and Automation account](../azure-monitor/insights/solutions.md#log-analytics- workspace-and-automation-account).
17
19
18
20
## Supported mappings
19
21
@@ -44,44 +46,44 @@ The following table shows the supported mappings:
44
46
45
47
## Unlink workspace
46
48
47
-
If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to remove the Update Management, Change Tracking and Inventory, and Start/Stop VMs during offhours solutions if you are using them. If you do not remove them, you can't complete the unlinking operation. Review the article for the particular solution you've imported to understand the steps required to remove it.
49
+
If you decide that you no longer want to integrate your Automation account with a Log Analytics workspace, you can unlink your account directly from the Azure portal. Before proceeding, you first need to remove Update Management, Change Tracking and Inventory, and Start/Stop VMs during off-hours if you are using them. If you do not remove them, you can't complete the unlinking operation. Review the article for each that you're enabling in order to understand the steps required to remove it.
48
50
49
-
After you remove these solutions, you can perform the following steps to unlink your Automation account.
51
+
After you remove them, you can perform the following steps to unlink your Automation account.
50
52
51
53
> [!NOTE]
52
-
> Some solutions including earlier versions of the Azure SQL monitoring solution might have created automation assets and might need to be removed prior to unlinking the workspace.
54
+
> Some solutions including earlier versions of the Azure SQL monitoring solution might have created Automation assets and might need to be removed prior to unlinking the workspace.
53
55
54
56
1. From the Azure portal, open your Automation account. On the Automation account page, select **Linked workspace** under **Related Resources**.
55
57
56
58
2. On the Unlink workspace page, click **Unlink workspace**. You receive a prompt verifying if you wish to continue.
57
59
58
60
3. While Azure Automation attempts to unlink the account your Log Analytics workspace, you can track the progress under **Notifications** from the menu.
59
61
60
-
4. If you used the Update Management solution, optionally you might want to remove the following items that are no longer needed after you remove the solution.
62
+
4. If you used Update Management, optionally you might want to remove the following items that are no longer needed after you remove it.
61
63
62
64
* Update schedules - Each has a name that matches an update deployment that you created.
63
65
* Hybrid worker groups created for the solution - Each has a name similar to `machine1.contoso.com_9ceb8108-26c9-4051-b6b3-227600d715c8`.
64
66
65
-
5. If you used the Start/Stop VMs during offhours solution, you can optionally remove the following items that aren't needed after you remove the solution.
67
+
5. If you used Start/Stop VMs during off-hours, you can optionally remove the following items that aren't needed after you remove it.
66
68
67
69
* Start and stop VM runbook schedules
68
70
* Start and stop VM runbooks
69
71
* Variables
70
72
71
-
Alternatively, you can unlink your workspace from your Automation account within the workspace.
73
+
Alternatively, you can unlink your workspace from your Automation account within the workspace.
72
74
73
75
1. In the workspace, select **Automation Account** under **Related Resources**.
74
76
2. On the Automation Account page, select **Unlink account**.
75
77
76
78
## Next steps
77
79
78
-
* Learn how to onboard Update Management and Change Tracking and Inventory solutions:
80
+
* Learn how to onboard Update Management and Change Tracking and Inventory:
79
81
80
82
* From a [virtual machine](../automation-onboard-solutions-from-vm.md)
81
83
* From your [Automation account](../automation-onboard-solutions-from-automation-account.md)
82
84
* When [browsing multiple machines](../automation-onboard-solutions-from-browse.md)
83
85
* From a [runbook](../automation-onboard-solutions.md)
84
86
85
-
* Learn how to onboard the Start/Stop VMs during offhours solution:
87
+
* Learn how to onboard the Start/Stop VMs during off-hours:
86
88
87
-
*[Deploy Start/Stop VMs during offhours](../automation-solution-vm-management.md)
89
+
*[Start/Stop VMs during off-hours overview](../automation-solution-vm-management.md)
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/solutions.md
+15-11Lines changed: 15 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,11 +5,12 @@ ms.subservice: logs
5
5
ms.topic: conceptual
6
6
author: bwren
7
7
ms.author: bwren
8
-
ms.date: 03/30/2020
8
+
ms.date: 04/23/2020
9
9
10
10
---
11
11
12
12
# Monitoring solutions in Azure Monitor
13
+
13
14
Monitoring solutions leverage services in Azure to provide additional insight into the operation of a particular application or service. This article provides a brief overview of monitoring solutions in Azure and details on using and installing them.
14
15
15
16
> [!NOTE]
@@ -22,6 +23,7 @@ You can add monitoring solutions to Azure Monitor for any applications and servi
Open the **Overview** page in Azure Monitor to display a tile for each solution installed in the workspace.
26
28
27
29
1. Go to the [Azure portal](https://ms.portal.azure.com). Search for and select **Monitor**.
@@ -33,7 +35,8 @@ Open the **Overview** page in Azure Monitor to display a tile for each solution
33
35
34
36
Monitoring solutions can contain multiple types of Azure resources, and you can view any resources included with a solution just like any other resource. For example, any log queries included in the solution are listed under **Solution Queries** in [Query explorer](../log-query/get-started-portal.md#load-queries) You can use those queries when performing ad hoc analysis with [log queries](../log-query/log-query-overview.md).
35
37
36
-
## List installed monitoring solutions
38
+
## List installed monitoring solutions
39
+
37
40
Use the following procedure to list the monitoring solutions installed in your subscription.
38
41
39
42
1. Go to the [Azure portal](https://ms.portal.azure.com). Search for and select **Solutions**.
@@ -47,9 +50,8 @@ Click on the name of a solution to open its summary page. This page displays any
Monitoring solutions from Microsoft and partners are available from the [Azure Marketplace](https://azuremarketplace.microsoft.com). You can search available solutions and install them using the following procedure. When you install a solution, you must select a [Log Analytics workspace](../platform/manage-access.md) where the solution will be installed and where its data will be collected.
54
56
55
57
1. From the [list of solutions for your subscription](#list-installed-monitoring-solutions), click **Add**.
@@ -61,6 +63,7 @@ Monitoring solutions from Microsoft and partners are available from the [Azure M
61
63

62
64
63
65
### Install a solution from the community
66
+
64
67
Members of the community can submit management solutions to Azure Quickstart Templates. You can install these solutions directly or download them templates for later installation.
65
68
66
69
1. Follow the process described in [Log Analytics workspace and Automation account](#log-analytics-workspace-and-automation-account) to link a workspace and account.
@@ -71,28 +74,29 @@ Members of the community can submit management solutions to Azure Quickstart Tem
71
74
6. You're prompted to provide information such as the resource group and location in addition to values for any parameters in the solution.
72
75
7. Click **Purchase** to install the solution.
73
76
74
-
75
77
## Log Analytics workspace and Automation account
78
+
76
79
All monitoring solutions require a [Log Analytics workspace](../platform/manage-access.md) to store data collected by the solution and to host its log searches and views. Some solutions also require an [Automation account](../../automation/automation-security-overview.md#automation-account-overview) to contain runbooks and related resources. The workspace and account must meet the following requirements.
77
80
78
81
* Each installation of a solution can only use one Log Analytics workspace and one Automation account. You can install the solution separately into multiple workspaces.
79
82
* If a solution requires an Automation account, then the Log Analytics workspace and Automation account must be linked to one another. A Log Analytics workspace may only be linked to one Automation account, and an Automation account may only be linked to one Log Analytics workspace.
80
-
* To be linked, the Log Analytics workspace and Automation account must be in the same resource group and region. The exception is a workspace in East US region and Automation account in East US 2.
83
+
* To be linked, the Log Analytics workspace and Automation account must be in the same subscription, but can be in different resource groups deployed to the same region. The exception is a workspace in East US region and Automation account in East US 2.
81
84
82
85
When you install a solution through the Azure Marketplace, you're prompted for a workspace and Automation account. The link between them is created if they aren't already linked.
83
86
84
87
### Verify the link between a Log Analytics workspace and Automation account
88
+
85
89
You can verify the link between a Log Analytics workspace and an Automation account using the following procedure.
86
90
87
91
1. Select the Automation account in the Azure portal.
88
-
1. Scroll to the **Related Resources** section of the menu.
89
-
1. If the **Workspace**setting is enabled, then this account is linked to a Log Analytics workspace. You can click on **Workspace** to view the details of the workspace.
92
+
1. Scroll to the **Related Resources** section of the menu and select **Linked workspace**.
93
+
1. If the **Workspace** is linked to an Automation account, then this page lists the workspace it is linked to. You can click on the name of the linked workspace listed and you are redirected to the overview page for that workspace.
90
94
91
95
## Remove a monitoring solution
92
-
To remove an installed solution, locate it in the [list of installed solutions](#list-installed-monitoring-solutions). Click on the name of the solution to open its summary page and then click on **Delete**.
93
96
97
+
To remove an installed solution, locate it in the [list of installed solutions](#list-installed-monitoring-solutions). Click on the name of the solution to open its summary page and then click on **Delete**.
94
98
95
99
## Next steps
96
-
* Get a [list of monitoring solutions from Microsoft](solutions-inventory.md).
97
-
* Learn how to [create queries](../log-query/log-query-overview.md) to analyze data collected by monitoring solutions.
98
100
101
+
* Get a [list of monitoring solutions from Microsoft](solutions-inventory.md).
102
+
* Learn how to [create queries](../log-query/log-query-overview.md) to analyze data collected by monitoring solutions.
0 commit comments