edit readme

Author: HaoyL666

assets/kubernetes-example2.png

@@ -266,7 +266,7 @@ mongo.setQueryOnInterval = async config => {
       //   console.log(`${config.mode} metrics recorded in MongoDB`)
       // })
       .catch(err => console.log(`Error inserting ${config.mode} documents in MongoDB: `, err));
-  }, 40000);
+  }, config.interval);
 };
 
 mongo.getSavedMetricsLength = async (mode, currentMetricNames) => {

chronos_npm_package/controllers/mongo.js

@@ -23,30 +23,38 @@ Docker also ensures that the versions that worked well on dev are bundled up and
 
 For additional details on how Chronos works this example, please review the Docker section in the [Chronos NPM Package README](../../chronos_npm_package/README.md).
 
-## Steps to Run Example
 
+
+## Grafana API KEY
+
+1. Run docker compose command below (LN 64) to start your Grafana container before you can access your service account token.
+
+2. In your browser, go to `localhost:32000`, which will be the login page of grafana. Use `admin` as both username and password to login. You can change the password after login.
+
+3. Navigate to `Home -> Administration -> Service accounts`, then click `Add service account` to create an service account. Be sure to choose `Admin` as the role. Then click `Add service account token`, hit `generate`, you are done! Remember this token, you will be using this token to access Grafana HTTP API programmatically.
+
+## Steps to Run Example
 Peform the following steps in each of the _books_, _customers_, _frontend_, and _orders_ directories
 
-1. Add a `.env` file to _each_ folder with the following key/value pairs:
+1. Add a `.env` file to each of _books_, _customers_, _frontend_, and _orders_ folders with the following key/value pairs:
 
 - **NOTE**: Ensure that there are no quotes surrounding any of the keys and values.
 
-> > > New collaboration group - testing all 5 url added to each .env// --> testing now...<<<
-
 ```
 CHRONOS_DB = MongoDB or PostgreSQL
 CHRONOS_URI = The URI to the desired MongoDB or PostgreSQL database to save health metrics via Chronos
 BOOK_URI = A MongoDB URI for the bookserver microservice to use
 CUSTOMER_URI = A MongoDB URI for the customerserver microservice to use
 ORDER_URI = A MongoDB URI for the orderserver microservice to use
+CHRONOS_GRAFANA_API_KEY = Bearer [the access token you created in above section (Grafana API Key)]
 ```
 
 2.  Verify that `@chronosmicro/tracker` is a dependency in each of the _books_, _customers_, _frontend_, and _orders_ folders (see the `package.json` in each folder).
 
-    - If the @chronosmicro/tracker dependency is listed as a **remote** npm package (i.e. `"@chronosmicro/tracker": "^11.0.1"`) and you've ran `npm install`, no further work is needed continue to step 3.
+    - If the @chronosmicro/tracker dependency is listed as a **remote** npm package (i.e. `"@chronosmicro/tracker": "^12.0.1"`) and you've ran `npm install`, no further work is needed continue to step 3.  **However, confirm that the "@chronosmicro/tracker" you've installed from npm has the correct database names you will query later because the database automation will build from the npm installed version
 
     - If you have the dependency as
-      `"@chronosmicro/tracker": "file:./chronos_npm_package"`, which is a **local** file, make sure to change the version from `"file:./chronos_npm_package"` to `"^11.0.1"` and run npm install.
+      `"@chronosmicro/tracker": "file:./chronos_npm_package"`, which is a **local** file, make sure to change the version from `"file:./chronos_npm_package"` to `"^12.0.1"` and run npm install.
 
 3.  With the terminal navigated to the the _examples/docker_ folder, run the command:
 
@@ -56,9 +64,10 @@ ORDER_URI = A MongoDB URI for the orderserver microservice to use
 docker-compose -f docker-compose.yml up
 ```
 
-4. If you run into any issues regarding 'linux/amd64,linux/arm/v7,linux/arm64/v8' for cadvisor, navigate to the docker-compose.yml and find the cadvisor dictionary. Change "platform" to linux/arm64/v8 for M1 Chips and linux/amd64 for Intel Chips.
-
-If you run into any issues regarding versions/images cadvisor, navigate to the docker-compose.yml and find the cadvisor dictionary. Change "image" to `image: gcr.io/cadvisor/cadvisor:latest` to `image: gcr.io/cadvisor/cadvisor:v0.47.0`
+4. If you run into any issues regarding `linux/amd64,linux/arm/v7,linux/arm64/v8` for cadvisor, navigate to the docker-compose.yml and find the cadvisor dictionary and try the below solutions. 
+  1. Change `platform` to `linux/arm64/v8` for M1 Chips and `linux/amd64` for Intel Chips.
+  2. Change "image" to `image: gcr.io/cadvisor/cadvisor:latest` to `image: gcr.io/cadvisor/cadvisor:v0.47.0` 
+  3. Alternatively, use Docker Buildx to specify multi-platform.
 
 ###
 

examples/docker/README.md

@@ -71,7 +71,6 @@ docker build -t backend:1.0 .
 
 2. run `npm start` to start npm server.
 
-
 ## Deploy the Cluster
 1. `cd` into the launch folder and run the following commands to start the services and deployments described in the YAML files:
 ```
@@ -86,6 +85,10 @@ kubectl apply -f frontend.yml
 <p align="center">
   <img alt="Kubernetes containers created" src="../../assets/examples_kubernetes_created.png">
 </p>
+<p align="center">
+  <img alt="dashboards created" src="../../assets/kubernetes-example2.png">
+</p>
+(The second image is inside k8s_node-backend_node-backend-d597768c-6zm5j_default_46da04f8-99c6-4522-9141-6c05f8d5141d_0, it may take a while to show up in Docker desktop based on the scraping interval)
 
 
 Your microservice health metrics can now be viewed at the given `CHRONOS_URI` or, preferrably, in the Electron.js desktop application.
@@ -103,7 +106,7 @@ kubectl delete -f frontend.yml
 
 **Mac Users:** Alternative to running the above commands, `cd` into the *scripts* folder and run the `stopKuber.sh` script
 
-**Note**: The above part only teardown Prometheus and Kubernetes, it leaves Grafana running. This is because if you teardown Grafana, the next time you redeploy you will be login with a new account, the access token and dashboard you created within this account will lose.
+**Note**: The above part only teardown Prometheus and Kubernetes, it leaves Grafana running. This is because if you teardown Grafana, the next time you redeploy you will be login with a new account, the access token and dashboard you created within this account will be lost.
 
 To teardown grafana, run the following commands:
 ```

examples/kubernetes/README.md

@@ -3,7 +3,7 @@ require('dotenv').config();
 module.exports = {
   // General configuration
   microservice: 'kubernetesmetrics',
-  interval: 25000,
+  interval: 40000,
 
   // Mode Specific
   mode: 'kubernetes',