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
Azure Monitor SCOM Managed Instance provides a cloud-based alternative for Operations Manager users providing monitoring continuity for cloud and on-premises environments across the cloud adoption journey.
17
+
18
+
>[!NOTE]
19
+
>- Linux monitoring is supported only via Managed Gateways.
20
+
>- Azure and Arc-enabled Linux machines aren't supported.
21
+
22
+
With SCOM Managed Instance, you can monitor Linux workloads that are on-premises and behind a gateway server. At this stage, we don't support monitoring Linux VMs hosted in Azure. For more information, see [How to monitor on-premises Linux VMs](/system-center/scom/manage-deploy-crossplat-agent-console).
Azure Monitor SCOM Managed Instance provides a cloud-based alternative for Operations Manager users providing monitoring continuity for cloud and on-premises environments across the cloud adoption journey.
18
17
19
18
## SCOM Managed Instance Agent
20
19
21
20
In Azure Monitor SCOM Managed Instance, an agent is a service that is installed on a computer that looks for configuration data and proactively collects information for analysis and reporting, measures the health state of monitored objects like an SQL database or logical disk, and executes tasks on demand by an operator or in response to a condition. It allows SCOM Managed Instance to monitor Windows operating systems and the components installed on them, such as a website or an Active Directory domain controller.
22
21
22
+
## Support for Azure and Off-Azure workloads
23
+
24
+
One of the most important monitoring scenarios is that of on-premises (off-Azure) workloads that unlock SCOM Managed Instance as a true **Hybrid monitoring solution**.
25
+
26
+
The following are the supported monitoring scenarios:
27
+
28
+
|Type of endpoint|Trust|Experience|
29
+
|---|---|---|
30
+
|Line of sight on-premises agent|Trusted|OpsConsole|
31
+
|Line of sight on-premises agent|Untrusted|Managed Gateway and OpsConsole|
32
+
|No Line of sight on-premises agent|Trusted/Untrusted|Managed Gateway and OpsConsole|
33
+
34
+
SCOM Managed Instance users will be able to:
35
+
36
+
- Set up and manage Gateways seamlessly from SCOM Managed Instance portal on Arc-enabled servers.
37
+
- Set high availability at Gateway plane for agent failover as described in [Designing for High Availability and Disaster Recovery](/system-center/scom/plan-hadr-design).
38
+
23
39
## Supported scenarios
24
40
25
41
The following are the supported monitoring scenarios:
26
42
27
-
- Azure and Arc-enabled VMs
28
-
- On-premises agents that have Line of sight connectivity to Azure
29
-
- On-premises agents with no Line of sight connectivity (must use managed Gateway) to Azure
43
+
- On-premises virtual machines with no Line of sight connectivity (must use managed Gateway) to Azure
44
+
- On-premises virtual machines that have Line of sight connectivity to Azure
30
45
31
46
## Prerequisites
32
47
33
48
Following are the prerequisites required on desired monitoring endpoints:
34
49
35
-
1. Ensure to Allowlist the following Azure URL on the desired monitoring endpoints:
36
-
`*.workloadnexus.azure.com`
37
-
2. Confirm the Line of sight between SCOM Managed Instance and desired monitoring endpoints by running the following command. Obtain LB DNS (Load balancer DNS) information by navigating to SCOM Managed Instance > **Overview** > **Properties** > **Load balancer** > **DNS Name**.
50
+
1. Confirm the Line of sight between SCOM Managed Instance and desired monitoring endpoints by running the following command. Obtain LB DNS (Load balancer DNS) information by navigating to SCOM Managed Instance > **Overview** > **Properties** > **Load balancer** > **DNS Name**.
3. Ensure to install [.NET Framework 4.7.2](https://support.microsoft.com/topic/microsoft-net-framework-4-7-2-offline-installer-for-windows-05a72734-2127-a15d-50cf-daf56d5faec2) or higher on desired monitoring endpoints.
43
-
4. Ensure TLS 1.2 or higher is enabled.
55
+
2. Ensure to install [.NET Framework 4.7.2](https://support.microsoft.com/topic/microsoft-net-framework-4-7-2-offline-installer-for-windows-05a72734-2127-a15d-50cf-daf56d5faec2) or higher on desired monitoring endpoints.
56
+
3. Ensure TLS 1.2 or higher is enabled.
44
57
45
58
To Troubleshooting connectivity problems, see [Troubleshoot issues with Azure Monitor SCOM Managed Instance](/system-center/scom/troubleshoot-scom-managed-instance?view=sc-om-2022&preserve-view=true).
46
59
60
+
## Install SCOM Managed Instance Gateway
61
+
62
+
Managed Gateway can be installed on Arc-enabled servers enabling it to relay monitoring data from air-gapped and network isolated servers to SCOM Managed Instance.
63
+
64
+
To install SCOM Managed Instance gateway, follow these steps:
65
+
66
+
1. Sign in to the [Azure portal](https://portal.azure.com/). Search and select **SCOM Managed Instance**.
67
+
2. On the **Overview** page, under **Manage**, select **SCOM managed instances**.
68
+
3. On the **SCOM managed instances** page, select the desired SCOM managed instance.
69
+
4. On the desired SCOM managed instance **Overview** page, under **Manage**, select **Managed Gateway**.
70
+
5. On the **Managed Gateways** page, select **New Managed Gateway**.
71
+
72
+
:::image type="content" source="media/monitor-off-azure-vm-with-scom-managed-instance/new-managed-gateway-inline.png" alt-text="Screenshot that shows new managed gateway." lightbox="media/monitor-off-azure-vm-with-scom-managed-instance/new-managed-gateway-expanded.png":::
73
+
74
+
**Add a Managed Gateway** page opens listing all the Azure arc virtual machines.
75
+
76
+
>[!NOTE]
77
+
>SCOM Managed Instance Managed Gateway can be configured on Arc-enabled machines only.
78
+
79
+
:::image type="content" source="media/monitor-off-azure-vm-with-scom-managed-instance/add-managed-gateway-inline.png" alt-text="Screenshot that shows add a managed gateway option." lightbox="media/monitor-off-azure-vm-with-scom-managed-instance/add-managed-gateway-expanded.png":::
80
+
81
+
6. Select the desired virtual machine and then select **Add**.
82
+
83
+
:::image type="content" source="media/monitor-off-azure-vm-with-scom-managed-instance/add-inline.png" alt-text="Screenshot that shows Add managed gateway." lightbox="media/monitor-off-azure-vm-with-scom-managed-instance/add-expanded.png":::
84
+
85
+
7. On the **Add Monitored Resources** window, review the selections and select **Add**.
### Configure monitoring of servers via SCOM Managed Instance Gateway
108
+
109
+
To configure monitoring of air-gapped and network isolated servers through Managed Gateway, follow the steps mentioned in [Install an agent on a computer running Windows by using the Discovery Wizard](/system-center/scom/manage-deploy-windows-agent-console#install-an-agent-on-a-computer-running-windows-by-using-the-discovery-wizard) section. Download and install agent from [here](https://go.microsoft.com/fwlink/?linkid=2251996).
110
+
111
+
>[!NOTE]
112
+
>Operations Manager Console is required for this action. For more information, see [Connect the Azure Monitor SCOM Managed Instance to Ops console](/system-center/scom/connect-managed-instance-ops-console?view=sc-om-2022&preserve-view=true).
113
+
47
114
## Install agent for Windows virtual machine
48
115
49
116
To install agent for Windows virtual machine, [download](https://go.microsoft.com/fwlink/?linkid=2251996) and follow these steps.
@@ -70,7 +137,7 @@ Follow these steps to deploy the SCOM Managed Instance agent with the Agent Setu
70
137
71
138
6. On the **Destination Folder** page, leave the installation folder set to the default, or select **Change** and type a path, and select **Next**.
72
139
73
-
7. On the **Agent Setup Options** page, you can choose whether you want to **connect the agent to Operations Manager**.
140
+
7. On the **Agent Setup Options** page, you can choose whether you want to **connect the agent to Operations Manager**.
74
141
75
142
8. On the **Management Group Configuration** page, do the following:
76
143
@@ -89,10 +156,9 @@ Follow these steps to deploy the SCOM Managed Instance agent with the Agent Setu
89
156
90
157
11. When the **Completing the Microsoft Monitoring Agent Setup Wizard** page appears, select **Finish**.
91
158
92
-
## Install Managed Gateway
159
+
## Configure monitoring of on-premises servers
93
160
94
-
To install Managed Gateway, [download the Gateway software](https://go.microsoft.com/fwlink/?linkid=2251997) and follow [these steps](/system-center/scom/deploy-install-gateway-server?view=sc-om-2022&tabs=InstallGatewayServer&preserve-view=true).
95
-
96
-
## Monitor Linux machine
161
+
To configure monitoring of on-premises servers that have direct connectivity (VPN/ER) with Azure, follow the steps mentioned in [Install an agent on a computer running Windows by using the Discovery Wizard](/system-center/scom/manage-deploy-windows-agent-console#install-an-agent-on-a-computer-running-windows-by-using-the-discovery-wizard) section.
97
162
98
-
With SCOM Managed Instance, you can monitor Linux workloads that are on-premises and behind a gateway server. At this stage, we don't support monitoring Linux VMs hosted in Azure. For more information, see [How to monitor on-premises Linux VMs](/system-center/scom/manage-deploy-crossplat-agent-console).
163
+
>[!NOTE]
164
+
>Operations Manager Console is required for this action. For more information, see [Connect the Azure Monitor SCOM Managed Instance to Ops console](/system-center/scom/connect-managed-instance-ops-console?view=sc-om-2022&preserve-view=true).
0 commit comments