Corrupted imports due to the absence of `mongoimport` should be removed or Grafana GUI won't work

ROCm / rocprofiler-compute

Advanced Profiling and Analytics for AMD Hardware

https://rocm.docs.amd.com/projects/omniperf/en/latest/

MIT License

135 stars 49 forks source link

Corrupted imports due to the absence of `mongoimport` should be removed or Grafana GUI won't work #39

Closed FabioLuporini closed 1 year ago

FabioLuporini commented 1 year ago

Symptom: when I open a panel like "System info" or "System speed of light" the loading wheel at the top right keeps spinning forever and nothing gets displayed

coleramos425 commented 1 year ago

Could you provide some additional information to help me troubleshoot your issue?

Are you using your own Grafana instance or shared?
Have you uploaded any workloads to your MongoDB backend?
Is http://<hostname>:27018/ reachable?
Does Save & Test button described here indicate a successful connection?

FabioLuporini commented 1 year ago

my own Grafana instance
about to (see below)
yes
yes

I'm one step away from accomplishing the upload (had some issues yesterday because in my docker image mongoimport was still missing, so I had to tweak the Dockerfile, rebuild etc -- so I haven't tried the "full working version" yet). But: with Chrome, the loading wheel stops spinnign immediately and the tab clearly states, at the centre, "No data". With safari instead nothing gets displayed and all my clicks are like no-op. I don't know if it's an omniperf-dashboard specific issue or a more generic grafana framework issue, but somehow I thought it'd be useful to report it.

This was safari 15.2 on MacOS Monterey. Sorry about the lack of detail in the original post

FabioLuporini commented 1 year ago

You may close or rename, up to you: the symptom really was there, but the issue is a totally different one!

The issue was a corrupted import via omniperf database --import ... -- corrupted because when I attempted it, mongoimport was not available yet; so the import went through, despite some warnings. I ignored that run, but I left it there. Later on, I performed more runs and imported them -- this time successfully because mongoimport was available. However, nothing showed up in the GUI until I manually removed omniperf database --remove ... the corrupted import. Luckily I thought of that and tried it. Why Safari and Chrome would behave differently in presence of such a corrupted import is still a mistery to me.

coleramos425 commented 1 year ago

Okay. Thanks for sharing @FabioLuporini. While we do list mongoimport as a requirement in our docs,

we could do a better job of dependency checking here in case a user skips this step. Historically, corrupt data doesn't play nicely with the proxy server we use to forward info to our Grafana interface.