Jonas Kunz

Accidently copied the wrong metric, here is the "system_cpu_usage" metric output by the OC-Agent: ``` # HELP system_cpu_usage last value of the recent cpu usage for the whole system [cores]...

Hi @LeePui , It indeed looks like a dependency problem induced by your other agent. In the agent version 1.27.0 we upgraded bytebuddy from version `1.11.22` to `1.12.1`. Which bytebuddy...

You problem might also be resolved by upgrading the elastic-agent to at least `1.34.0`. This version contains a change (#2728) which should isolate the elastic agent from any dependencies your...

Hey @DJRickyB , this indeed looks incorrect. Just to be sure: All of the spans shown in the screenshot are inferred, correct? E.g. none are instrumented via the `trace_methods` configuration?...

Closing as ASM has to stay in sync with the version provided by bytebuddy (which still is 9.3).

Hey @aydasraf, I had another look at our code, the error handling of Micrometer `Meter`s there already seems fine. We loop over all `Meter`s to collect their values. We catch...

In that case there unfortunately isn't really anything we can do on the agent side. You could only disable the causing micrometer metric as @jackshirazi suggested. Other than that I...

I'm closing this issue for now, as I don't see anything we can do here. Feel free to reopen if required.

Perfect! Thanks for the fast response.

I suspect this issue also applies to log reformatting and log correlation. IINM, we don't handle multi-service deployments within the same JVM there yet. I think the correct solution would...