Thanks for checking.
Yes, that’s what the problem is. Profiler stopped abruptly a long time back (with some error). And being a microservice deployed in Openshift, everytime we restart, it should appear as a new JVM which we should be able to profile (ideally). But the problem is, it is not allowing us to choose any other JVM from the dropdown, and it keeps showing this error whenever we choose Profiler (as was shared in screenshot).
Basically, it appears that the dashboard has got hung up with that 2 weeks old instance. For any new instance, we CAN see the JVM stats but CAN’T run a profiler (on any of the new JVMs).