-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
JMX collected on one VM but not on another #738
Labels
Comments
I have another VM running Java 17 Temurin. Same IAM permissions (Logs & Metric writer), same opsagent config, same JMX args, no metrics get written:
|
Went through https://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/troubleshooting but to no avail. The JVM versions remains as the single thing that differs. |
This issue was marked stale due to lack of activity. It will be closed in 14 days. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I configured my app and ops-agent to collect JVM metrics and it worked just fine on the first VM. The exact same configuration won't work on another VM, however. The only difference is that the first runs Java 8 (openjdk version "1.8.0_292"), which is not supported according to the docs and the second runs Java 11 (openjdk version "11.0.11" 2021-04-20), which is supported (...)
Both run Debian 10.
Both output virtually the same merged config:
Both have the same JVM flags as well:
Plus I can tunnel to the second VM and attach my own jconsole to it and it works just fine. I restarted the ops-agent a couple times already.
To Reproduce
Steps to reproduce the behavior:
I don't know.
Expected behavior
Monitoring picks up JMX metrics.
Environment (please complete the following information):
Additional context
Is there any way for me to investigate further?
The text was updated successfully, but these errors were encountered: