Roy Li

Glad to see we are not alone. We are seeing the same behavior, plus after 10ish days it will stop sending metrics totally. See details in https://github.com/open-telemetry/opentelemetry-java-contrib/issues/861

The other behavior is the following metrics stuck in number "454211". Does anyone have this experience before? otelcol_receiver_accepted_metric_points{receiver="jmx",service_instance_id="***",service_name="refinery",service_version="v0.3.0",transport="grpc"} 454211

Found the following error 2023-05-09T19:19:58.474Z debug subprocess/subprocess.go:287 java.lang.OutOfMemoryError: Java heap space {"kind": "receiver", "name": "jmx", "pipeline": "metrics"}

Thanks for taking a look at this @trask. This OutOfMemoryError only shows up when I set the collection_interval to 1s. Since the waiting time is long(from 10 hours to 10...

I can try but it is still kind of a workaround. One more info, I am running the receiver in aws kubernetes as a sidecar container. And this situation is...

Thanks @smamidala1 , will follow #926

Thanks @dehaansa !