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
### Setting up cron job to start Node exporter on VM restart
59
+
60
+
1. If the target virtual machine is restarted/stopped, node exporter is also stopped, and needs to be manually started again to continue monitoring.
61
+
1. Run `sudo crontab -e` command to open cron file.
62
+
2. Add the command `@reboot cd /path/to/node/exporter && nohup ./node_exporter &` at the end of cron file. This starts node exporter on VM reboot.
63
+
64
+
```shell
65
+
# if you do not have a crontab file already, create one by running the command: sudo crontab -e
66
+
sudo crontab -l > crontab_new
67
+
echo"@reboot cd /path/to/node/exporter && nohup ./node_exporter &">> crontab_new
68
+
sudo crontab crontab_new
69
+
sudo rm crontab_new
70
+
```
71
+
58
72
## Prerequisites to enable secure communication
59
73
60
74
To [enable TLS 1.2 or higher](enable-tls-azure-monitor-sap-solutions.md), follow the steps [mentioned here](https://prometheus.io/docs/guides/tls-encryption/)
@@ -104,19 +118,6 @@ When the provider settings validation operation fails with the code ‘Prometheu
104
118
1. Run `nohup ./node_exporter &` command to enable node_exporter.
105
119
1. Adding nohup and & to above command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
106
120
107
-
### Setting up cron job to start Node exporter on VM restart
108
-
109
-
1. If the target virtual machine is restarted/stopped, node exporter is also stopped, and needs to be manually started again to continue monitoring.
110
-
1. Run `sudo crontab -e` command to open cron file.
111
-
1. Add the command `@reboot cd /path/to/node/exporter && nohup ./node_exporter &` at the end of cron file. This will start node exporter on VM reboot.
112
-
113
-
```shell
114
-
sudo crontab -l > crontab_new
115
-
echo"@reboot cd /path/to/node/exporter && nohup ./node_exporter &">> crontab_new
Copy file name to clipboardExpand all lines: articles/sap/monitor/quickstart-portal.md
+15-6Lines changed: 15 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,38 +26,47 @@ If you don't have an Azure subscription, create a [free](https://azure.microsoft
26
26
27
27
1. Sign in to the [Azure portal](https://portal.azure.com).
28
28
29
-
1. In Azure **Search**, select **Azure Monitor for SAP solutions**.
29
+
2. In Azure **Search**, select **Azure Monitor for SAP solutions**.
30
30
31
31
32
32
33
33
34
+
3. On the **Basics** tab, provide the required values.
35
+
1.**Workload Region** is the region where the monitoring resources are created, make sure to select a region that is same as your virtual network.
36
+
2.**Service Region** is where proxy resource gets created which manages monitoring resources deployed in the workload region. Service region is automatically selected based on your Workload Region selection.
37
+
3. For **Virtual Network** field select a virtual network, which has connectivity to your SAP systems.
38
+
4. For the **Subnet** field, select a subnet that has connectivity to your SAP systems. You can use an existing subnet or create a new subnet. Make sure that you select a subnet, which is an **IPv4/25 block or larger**.
39
+
5. For **Log Analytics Workspace**, you can use an existing Log Analytics workspace or create a new one. If you create a new workspace, it will be created inside the managed resource group along with other monitoring resources.
40
+
6. When entering **managed resource group** name, make sure to use a unique name. This name is used to create a resource group, which will contain all the monitoring resources. Managed Resource Group name cannot be changed once the resource is created.
34
41
35
-
1. On the **Basics** tab, provide the required values. If applicable, you can use an existing Log Analytics workspace.
36
-
42
+
<br/>
37
43
38
44
39
45
46
+
4. On the **Providers** tab, you can start creating providers along with the monitoring resource. You can also create providers later by navigating to the **Providers** tab in the Azure Monitor for SAP solutions resource.
47
+
5. On the **Tags** tab, you can add tags to the monitoring resource. Make sure to add all the mandatory tags in case you have a tag policy in place.
48
+
6. On the **Review + create** tab, review the details and click **Create**.
49
+
40
50
41
51
## Create Azure Monitor for SAP solutions (classic) monitoring resource
42
52
43
53
1. Sign in to the [Azure portal](https://portal.azure.com).
44
54
45
55
1. In Azure **Marketplace** or **Search**, select **Azure Monitor for SAP solutions (classic)**.
46
56
47
-
57
+
48
58
49
59
50
60
1. On the **Basics** tab, provide the required values. If applicable, you can use an existing Log Analytics workspace.
51
61
52
62
:::image type="content" source="./media/quickstart-portal/azure-monitor-quickstart-2.png" alt-text="Screenshot that shows configuration options on the Basics tab." lightbox="./media/quickstart-portal/azure-monitor-quickstart-2.png":::
53
63
54
-
When you're selecting a virtual network, ensure that the systems you want to monitor are reachable from within that virtual network.
64
+
When you're selecting a virtual network, ensure that the systems you want to monitor are reachable from within that virtual network.
55
65
56
66
> [!IMPORTANT]
57
67
> Selecting **Share** for **Share data with Microsoft support** enables our support teams to help you with troubleshooting. This feature is available only for Azure Monitor for SAP solutions (classic)
0 commit comments