Replies: 4 comments
-
What's generating the metrics? |
Beta Was this translation helpful? Give feedback.
-
I think this is just a jvm metric that we're getting from auto-instrumentation. We do have these flags enabled so it could be one of these, however: ` ``OTEL_INSTRUMENTATION_AKKA_ACTOR_ENABLED: "true" |
Beta Was this translation helpful? Give feedback.
-
Can you tell me more about your setup? What libraries / frameworks are you using? What version of the otel java agent? The metric you're describing doesn't come from the standard JVM runtime metrics that the otel java agent provides. It may be coming from some instrumentation built directly into one of the libraries you depend on? |
Beta Was this translation helpful? Give feedback.
-
Hmm, that's interesting - because "CodeHeap 'non-profiled nmethods'" IS a JVM metric, it looks like it was added as of JDK 9 and gets enabled/disabled on these flags. So I'm guessing one of the flags I've got above - probably the Dropwizard Metrics one - is taking that JVM metric and these similar ones with |
Beta Was this translation helpful? Give feedback.
-
We recently upgraded to JDK 11 and I'm noticing that the various CodeHeap metrics now have an
'
in the name, and so the otel agent is complaining when it instantiates the metrics instruments, i.e.:[otel.javaagent 2024-03-11 18:06:53:001 +0000] [main] WARN io.opentelemetry.sdk.metrics.SdkMeter - Instrument name "memory.pools.CodeHeap-'non-profiled-nmethods'.usage" is invalid, returning noop instrument. Instrument names must consist of 63 or fewer characters including alphanumeric, _, ., -, and start with a letter. --
I can't be the first person to encounter this, but I'm not seeing a solution anywhere for all of these warnings. What's the method for dealing with these invalid instrument names?
Beta Was this translation helpful? Give feedback.
All reactions