Merge pull request #8185 from harness/rssnyder-patch-2

Update 2-configure-ecg-for-auto-stopping-rules.md

docs/cloud-cost-management/4-use-ccm-cost-optimization/1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/2-configure-ecg-for-auto-stopping-rules.md

@@ -17,26 +17,25 @@ When the ECG is configured to watch a workload, an AutoStopping Rule will not st
 
 By default, the AutoStopping Rule listens to HTTP/HTTPS traffic. On the other hand, a resource can be working on long-running background jobs like batch jobs. Nightly data updates or scheduled processing, for example. In this scenario, relying just on network traffic to detect resource idleness is not the ideal solution. For such scenarios, you can configure ECG for your AutoStopping Rules.
 
-
-### Metrics Watcher
+## Metrics Watcher
 
 Metrics watcher is used to detect idleness based on CPU and memory of the resource. If the CPU and memory values are below the configured limit, AutoStopping will detect that as idleness for the resource and stop it.
 
-
 ```
 [metrics]  
 cpu = "40"  
 memory = "5Gb"
 ```
-### Process Watcher
 
-Process watcher watches for the existence of processes that match the supplied condition. When a process with the matching condition is detected, AutoStopping will detect that as idleness for the resource and stop it.
+## Process Watcher
 
+Process watcher watches for the existence of processes that match the supplied condition. When a process with the matching condition is detected, AutoStopping will detect that as idleness for the resource and stop it.
 
 ```
 [process]  
 condition = "python*"
 ```
+
 ### Configure ECG
 
 You can configure either metrics or process watcher for your rule.
@@ -47,40 +46,69 @@ ECG is supported only for Unix-like machines. To install the agent,
 
 1. Download the ECG file from the S3 link:  
 [https://lightwing-downloads-temp.s3.ap-south-1.amazonaws.com/ecg/ecg_1.2.0_linux_amd64.zip](https://lightwing-downloads-temp.s3.ap-south-1.amazonaws.com/ecg/ecg_1.2.0_linux_amd64.zip)
-2. Unzip the file.
+
+```
+wget https://lightwing-downloads-temp.s3.ap-south-1.amazonaws.com/ecg/ecg_1.2.0_linux_amd64.zip
+```
+
+2. Unzip the file and navigate into the resulting folder
+
 ```
-unzip ecg_1.1.0_linux_amd64.zip
+unzip ecg_1.2.0_linux_amd64.zip
+cd ecg_1.2.0_linux_amd64
 ```
-3. Install the agent.
+
+3. Check the contents of the installation script, make it executable, and execute it as root
+
 ```
+cat install.sh
+chmod +x install.sh
 sudo ./install.sh
 ```
 
 #### Step 2: Specify the Configuration Details
 
 To configure ECG for your rule, provide the following configuration details:
 
-* **Account ID**: Account ID for which you want to enable ECG. You can copy the account ID from the Harness Manager. In Harness Manager's address bar, copy the **Harness account ID** from your Harness URL. The Harness account ID comes after `account` in the URL.  
+1. **Account ID**: Account ID for which you want to enable ECG. You can copy the account ID from the Harness Manager. In Harness Manager's address bar, copy the **Harness account ID** from your Harness URL. The Harness account ID comes after `account` in the URL.  
 
-For example in the following URL, the account ID is `1a2b3c`: `https://app.harness.io/#/account/1a2b3c`.
-* **Hostname of the AutoStopping Rule**: Hostname of the AutoStopping Rule for which you want to configure the ECG. You can copy the hostname from the [AutoStopping dashboard](../1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/autostopping-dashboard.md). To obtain the hostname, do the following:
-1. In **AutoStopping Rules**, in **Summary of Rules**, click the rule for which you want to configure the ECG.
-2. Copy the hostname.
-   
+For example in the following URL, the account ID is `1a2b3c`: `https://app.harness.io/ng/account/1a2b3c`.
+
+2. **Hostname of the AutoStopping Rule**: Hostname of the AutoStopping Rule for which you want to configure the ECG. You can copy the hostname from the [AutoStopping dashboard](../1-optimize-cloud-costs-with-intelligent-cloud-auto-stopping-rules/4-create-auto-stopping-rules/autostopping-dashboard.md). To obtain the hostname, do the following:
+  a. In **AutoStopping Rules**, in **Summary of Rules**, click the rule for which you want to configure the ECG.
+  b. Copy the hostname.
 
 ![](./static/configure-ecg-for-auto-stopping-rules-00.png)
 
+3. [optional] **process**: A regex for the process to watch for. For example, if the process you want to watch is a simple python script `python trainmodel.py` we could specify `trainmodel.py`:
 
-##### Example
+```
+[process]  
+condition = "Python*"  
+```
 
-Assume your long-running job is a simple Python script:
+4. [optional] **metrics**: A threshold for CPU and memory for determining "activity" on the instance. If you specify both, they will both need to be met to be concidered active.
+
+```
+[metrics]  
+cpu = "40"  
+memory = "2Gb"
+```
+
+*You will need to specify at least one of `[metrics]` or `[process]`.*
 
 
+#### Example
+
+Assume your long-running job is a simple Python script:
+
 ```
 > python trainmodel.py
 ```
-The following example shows how to configure `ecg` with the details:
 
+And your threshold for resource useage is 50% CPU and 1G memory.
+
+The following example shows how to configure `ecg` with the above details:
 
 ```
 # Configuration file for the ECG agent  
@@ -91,19 +119,19 @@ ruleHostName = "fluent-katydid-c6p67ucpv2dpsb76i66g.schedules-ce-dev.lightwingte
 # For process based heartbeats configure the below section.  
   
 [process]  
-condition = "Python*"  
+condition = "trainmodel.py"  
   
 # For metrics based heartbeats configure the below section.  
   
 #[metrics]  
-#cpu = "40"  
-#memory = "5Gb"
+#cpu = "50"  
+#memory = "1Gb"
 ```
+
 #### Step 3: Restart the ECG Process
 
 After making the configuration changes, restart the ECG process.
 
-
 ```
 sudo systemctl restart ecg
 ```