I am trying to set up an alarm for instance over jmx, on paper it is simple, when jvm.threads.count is no more because the jmx port is not up, an alert will be sent out.
However, the Ops Agent will keep on showing that the same amount of threads are active when I kill the java process and the jmx port is not active anymore.
I also noticed that java -Dorg.slf4j.simpleLogger.defaultLogLevel=info io.opentelemetry.contrib.jmxmetrics.JmxMetrics -config /tmp/jmx-config-985726696.properties proxy is running on the VM, what is probably feeding jvm data to cloud monitoring. If I restart the Ops Agent when my java process is not running, the proxy will be reloaded and jmx connection is dropped, resulting in an alarm being sent out.
Is there any way to get the proxy to work so it would also acknowledge that the port is not running anymore without a restart of Ops Agent?
Tried with java 8 and 11, both had the same results
