You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have few VM's in Compute Engine that are running Java applications on RHEL 8. I am able to monitor them over JMX and I would like to set up an alarm that when one of those processes dies, Google Monitoring would send out an alarm, that JMX port is down.
Describe the bug
I have set up a policy for workload.googleapis.com/jvm.threads.count for it. When I kill one of the processes, the opentelemetry-collector will hang like the JMX port is still up. There is a process java -Dorg.slf4j.simpleLogger.defaultLogLevel=info io.opentelemetry.contrib.jmxmetrics.JmxMetrics -config /tmp/jmx-config-3146301998.properties up and this seems to be feeding GCP this data. When I restart the google-cloud-ops-agent-opentelemetry-collector service on the server, the jvm.threads.count will drop and an alarm is being sent out
I have few VM's in Compute Engine that are running Java applications on RHEL 8. I am able to monitor them over JMX and I would like to set up an alarm that when one of those processes dies, Google Monitoring would send out an alarm, that JMX port is down.
Describe the bug
I have set up a policy for workload.googleapis.com/jvm.threads.count for it. When I kill one of the processes, the opentelemetry-collector will hang like the JMX port is still up. There is a process
java -Dorg.slf4j.simpleLogger.defaultLogLevel=info io.opentelemetry.contrib.jmxmetrics.JmxMetrics -config /tmp/jmx-config-3146301998.properties
up and this seems to be feeding GCP this data. When I restart the google-cloud-ops-agent-opentelemetry-collector service on the server, the jvm.threads.count will drop and an alarm is being sent out/tmp/jmx-config-3146301998.properties file:
To Reproduce
Steps to reproduce the behavior:
jvm.threads.count
, if metric is above 1, all is good, if metric is not over 1, send out an alarmgoogle-cloud-ops-agent-opentelemetry-collector.service
servicejvm.threads.count
drops in the Google Monitoring also and an alarm is triggeredExpected behavior
Alarm should be triggered without the
google-cloud-ops-agent-opentelemetry-collector.service
restartEnvironment (please complete the following information):
health-checks.log
logging-module.log
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: