Unable to View Metrics Tab

[adriankormier]

I'm trying to spin up the app and test it out before potentially iterating on it.

Steps to reproduce the behavior:
Followed the README instructions after installing Docker Desktop:

1. Cloned the repo
2. Ran npm install
3. docker compose up
4. npm run dev in separate terminal
5. navigated to localhost:4001/api/k8
6. Clicked the buttons one by one, waiting for green check mark before continuing.
7. Left terminal open and navigated to localhost:4000.
8. Signed Up and Signed In.
9. Navigated to Metrics Dashboard and was met with many errors. Primarily an error when fetching uid key and api key.

Expected Behavior:
Metrics tab to display currently running containers.

Screenshot:

Desktop (please complete the following information):

• OS: Windows 11 Home Edition
• Browser: Chrome

Additional context:
From what my team members have gathered, the issue seems to be with Grafana and Prometheus not installing correctly. They were able to get it running on iOS, but Linux and Windows have not worked so far.

The other tabs show the currently running containers and seem to be working correctly.

UPDATE:

After changing file permissions and ownership using the following:
"sudo chmod 777 data" and "sudo chown -R username:username data" from imageConfigs/grafana
"sudo chmod 777 promData" and "sudo chown -R username:username promData" from imageConfigs/prometheus

I am now seeing "NO DATA" on portions of the Metrics tab but I am able to see the majority of the information. It appears I am having errors in node-exporter, but have not figured those out yet.

[jaenixlee]

Hi Adrian,
Did you have a Kubernetes Cluster or minikube running?
If you do not have either of these running, there is no need to go through the Kubernetes set up.
Please let us know if you are still having this issue even without going through the Kubernetes set up.

[adriankormier]

Hi Jaeni! The main persisting issue that I had was that the metrics for the containers themselves did not display even after taking the steps above. I ultimately ended up using Windows instead of WSL to work on the project and that worked fine. The team I'm working with tried to debug the issue but didn't have any luck.