Current auto-instrumentation support for metrics

[SohamSankhe]

Hello,

I was exploring the use of Otel javaagent v1.16.0 for metrics and I could not find any documentation that lists all the available out of the box metrics. The document with 'list of supported third party libraries' seems to be mostly for tracing instrumentation.

Looking at the code, I see metrics related auto-instrumentation in below areas:
JVM runtime, system, DB connection pool, http client/server, rpc client/server, kafka clients.

Seeing that metrics was recently marked as Stable, I am assuming this is all the javaagent provides as of now.

Can you please confirm this?
And is there any documentation I can follow to track progress in this area for my future requirements.

[Roiocam]

i am not sure this answer is help... it is my own opinion

on document website this page mark metrics (api, sdk, protocol) is stable. that is not meaning there is many out of the box metrics for library.

In my understanding, this means that the APIs, SDKs for metrics collection are stable enough for Library developers or who want to impl observability to migrate the original solution to OpenTelemetry.

it is just like Docker Container Infrastructure is stable software, but you have to build your own image then you can run it.

[mateuszrzeszutek]

Hey @SohamSankhe ,

I was exploring the use of Otel javaagent v1.16.0 for metrics and I could not find any documentation that lists all the available out of the box metrics. The document with 'list of supported third party libraries' seems to be mostly for tracing instrumentation.

The list of supported libraries contains all libs that we instrument in any way -- be it traces, metrics, or logs. Would it make sense for you if we added a column saying which telemetry signal an instrumentation produces?

[tuhao1020]

@mateuszrzeszutek #6532
seems no metrics for daemon threads too

[gabrielgiussi]

@tuhao1020 I saw you did a mistake and gc was working fine for you after fixing that, what was it?

[tuhao1020]

@gabrielgiussi it's working now

[gabrielgiussi]

But did you change something like bumping the version or something like that?

[tuhao1020]

I do nothing and it was back to normal 😄

[gabrielgiussi]

@mateuszrzeszutek

Would it make sense for you if we added a column saying which telemetry signal an instrumentation produces?

It think it would be nice, I'm not seeing any kafka/jetty metrics after adding the agent but I don't know if they are not provided or it is something else in my configuration (because I'm also not seeing gc metrics and I understand those are exported).
I do see some metrics collected by the agent, e.g.

process_runtime_jvm_cpu_utilization
process_runtime_jvm_memory_committed
process_runtime_jvm_threads_count
http_client_response_size
http_client_duration