Update README.md

Author: kcantrel

Monitoring/monitor_fsxn_with_harvest_on_eks/README.md

@@ -18,62 +18,105 @@ Harvest Helm chart installation will result the following:
 * `Helm` - for resources installation.
 * An FSx for ONTAP file system deployed in the same VPC as the EKS cluster.
 * Existing `Secrets Manager`secret in the same region as the FSxN file system.
-* Existing `Prometheus` running on your EKS cluster.
-* Existing `Grafana` running on your EKS cluster.
-
-**NOTE:** You can install both Prometheus and Grafana using this [Helm chart](https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack).
 
 ### Deployment
-### User Input
 
-Parameter | Description | 
---- | --- | 
-fsxs.clusters.name | FSxN cluster name | 
-fsxs.clusters.managment_lif | FSxN for NetApp ONTAP filesystem management IP |
-fsxs.clusters.secretName | AWS Secrets Manager for FSxN credentials |
-fsxs.clusters.region | FSxN and AWS Secrets Manager region |
-fsxs.clusters.promPort | Which port harvest will be created and exposed to Promethues |
-promethues | Existing Promethues name for discovering |
+## Deployment of Prometheus and Grafana
+If you don't already have Prometheus and Grafana running in your EKS cluster, you can deploy both of them
+from the Prometheus community repository by using the following commands:
+
+:memo: **NOTE:** You need to make a substitution in the command below before running it.
+```bash
+helm repo add prometheus-community https://prometheus-community.github.io/helm-charts
+helm repo update
+helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace prometheus --create-namespace \
+  --set prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.resources.requests.storage=50Gi \
+  --set prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.storageClassName=<FSX-BASIC-NAS>
+```
+Where:
+* \<FSX-BASIC-NAS\> is the storage class you want to use.  If you don't care about persistent storage, you can omit the
+last two lines from the above command.
 
-### Integration with AWS Secrets Manager
+The above will create a 50Gib PVC for Prometheus to use. You can adjust the size as needed.
 
-The installation supports integration with AWS Secrets Manager. You can store your FSxN credentials by using existing or new AWS Secrets Manager. 
-Harvest will invoke script specified in the credentials_script path section which already mapped to Harvest container.
-Harvest uses ServiceAccount with permissions to fetch the secrets. 
-Credentails script expect to fetch `USERNAME`, `PASSWORD` values from Secrets Manager.
-ServiceAccount should be created during the installation with the sufficient permissions. 
+A successful installation should look like this:
+```
+$ helm install kube-prometheus-stack prometheus-community/kube-prometheus-stack --namespace prometheus --create-namespace \
+  --set prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.resources.requests.storage=50Gi \
+  --set prometheus.prometheusSpec.storageSpec.volumeClaimTemplate.spec.storageClassName=fsx-basic-nas
+NAME: kube-prometheus-stack
+LAST DEPLOYED: Fri Jul 26 22:57:04 2024
+NAMESPACE: prometheus
+STATUS: deployed
+REVISION: 1
+NOTES:
+kube-prometheus-stack has been installed. Check its status by running:
+  kubectl --namespace prometheus get pods -l "release=kube-prometheus-stack"
+
+Visit https://github.com/prometheus-operator/kube-prometheus for instructions on how to create & configure the Alertmanager and Prometheus instances using the Operator.
+```
+To check the status, you can run the following command:
+```bash
+kubectl get pods -n prometheus
+```
+The output should look something like this:
+```bash
+$ kubectl get pods -n prometheus
+NAME                                                        READY   STATUS    RESTARTS   AGE
+alertmanager-kube-prometheus-stack-alertmanager-0           2/2     Running   0          51s
+kube-prometheus-stack-grafana-86844f6b47-njw6n              3/3     Running   0          56s
+kube-prometheus-stack-kube-state-metrics-7c8d64d446-rj4tv   1/1     Running   0          56s
+kube-prometheus-stack-operator-85b765d6bc-ll5q2             1/1     Running   0          56s
+kube-prometheus-stack-prometheus-node-exporter-7rtbp        1/1     Running   0          56s
+kube-prometheus-stack-prometheus-node-exporter-ffckd        1/1     Running   0          56s
+prometheus-kube-prometheus-stack-prometheus-0               2/2     Running   0          50s
+```
 
+### Integration with AWS Secrets Manager
+
+This Harvest installation supports integration with AWS Secrets Manager. To use it store your FSxN credentials into a
+Secrets Manager secret. Harvest will invoke the script specified in the credentials_script path section which is already
+mapped in Harvest container. The credentails_script will fetch the secret and set the credentials based on its content.
+It expects the secret string to be a json structure with a `username` and `password` keys. For example:
+```json
+{
+  "username": "fsxadmin",
+  "password": "fsxadmin-password"
+}
+```
+A ServiceAccount should be created during the installation with the sufficient permissions to fetch the secrets.
 
 ### Monitoring multiples FSxN
 
-The Helm chart supports monitoring multiple FSxNs.
-You can add multiples FSxNs by configure it on `values.yaml`:
+The Helm chart supports monitoring multiple FSxNs. You can add multiples FSxNs by configure it on `values.yaml`.
 For example: 
 ```
 fsxs:
   clusters:
-    - name: fsx1
+    - name: <fsx1>
       managment_lif: <FSx1_Management_LIF>
       promPort: 12990
       secretName: <FSx1_secret_name>
       region: <FSx1_region>
-    - name: fsx2
+    - name: <fsx2>
       managment_lif: <FSx2_Management_LIF>
       promPort: 12991
       secretName: <FSx2_secret_name>
       region: <FSx2_region>
 ```
+Of course replace the strings within the <> with your own values.
+
 **NOTE:** Each FSxN cluster should have unique port number for promPort.
 
 ### Installation
-Install Harvest helm chart from this GitHub repository. The custom Helm chart includes:
+Download the Harvest helm chart from this GitHub repository found in the 'harvest' directory. The custom Helm chart includes:
 * `deplyment.yaml` - Harvest deployment using Harvest latest version image
 * `harvest-config.yaml` - Harvest backend configuration
 * `harvest-cm.yaml` -  Environment variables configuration for credentails script.
 * `service-monitor.yaml` - Promethues ServiceMonitor for collecting Harvest metrics.
 
 1. **Create AWS Secrets Manager for FSxN credentials**
-If you don't already have an AWS Secrets Manager secret for your FSxN credentials, you can create one using the AWS CLI.
+If you don't already have an AWS Secrets Manager secret with your FSxN credentials, you can create one using the AWS CLI.
 ```
 aws secretsmanager create-secret \
   --region <REGION> \
@@ -105,8 +148,9 @@ The following IAM policy can be used to grant the all permissions required by Ha
     ],
     "Version": "2012-10-17"
 }
-
 ```
+Of course replace the strings within the <> with your own values.
+
 You can use the following command to create the policy:
 
 POLICY_ARN=$(aws iam create-policy --policy-name harvest_read_secrets --policy-document file://harvest-read-secrets-policy.json --query Policy.Arn --output text)
@@ -134,7 +178,8 @@ Once the deployment is complete, Harvest should be listed as a target on Prometh
 
 ### Import FSxN CloudWatch metrics into your monitoring stack using YACE
 AWS provides FSx for ONTAP metrics which cannot be collected by Harvest. Therefore, we recommend to
-use yet-another-exporter (by Prometheus community) for collecting metrics from CloudWatch. See [YACE](https://github.com/nerdswords/helm-charts) for more information.
+use yet-another-exporter (by Prometheus community) for collecting metrics from CloudWatch.
+See [YACE](https://github.com/nerdswords/helm-charts) for more information.
 
 #### Installation #### 
 1. **Create ServiceAccount with permissions to AWS CloudWatch**
@@ -174,8 +219,7 @@ POLICY_ARN=$(aws iam create-policy --policy-name yace-exporter-policy --policy-d
 
 2. **Create ServiceAccount**:
 
-**note**: namespace should be already exists\
-if not exist use the following command: 
+**note**: namespace should be already exists if not exist use the following command: 
 ```
 kubectl create ns <NAMESPACE>
 ```