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
@@ -94,15 +94,15 @@ When the provider settings validation operation fails with the code ‘Prometheu
94
94
1. Try to restart the node exporter agent:
95
95
1. Go to the folder where you installed the node exporter (the file name resembles `node_exporter-*.*-amd64`).
96
96
1. Run `./node_exporter`.
97
-
1. Adding nohup and & to aboe command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
97
+
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.
98
98
1. Verify that the Prometheus endpoint is reachable from the subnet that you provided while creating the Azure Monitor for SAP solutions resource.
99
99
100
100
## Suggestions
101
101
102
102
### Enabling Node Exporter
103
103
104
104
1. Run `nohup ./node_exporter &` command to enable node_exporter.
105
-
1. Adding nohup and & to aboe command decouples the node_exporter from linux machine commandline. If not included node_exporter would stop when the commandline is closed.
105
+
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
106
107
107
### Setting up cron job to start Node exporter on VM restart
0 commit comments