opentelemetry and microprofile.telemetry subsystem not sending metrics to otlp endpoint.

[Christoffer A. Nilsen]

I'm having issues getting JVM metrics sent to my otlp endpoint.

Wildfly: 31

OTLP endpoint software: Elastic APM integration

After adding the opentelemetry subsystem to my standalone, I'm able to get spans for my REST endpoints.

When using the opentelemetry-api maven dependency I'm able to manually create span.

However, I want get metrics as well. After reading the Wildfly Admin Guide my understanding is that I need to add the microprofile.telemetry subsystem and enable it with otel.sdk.disabled=false if I want metrics, however I don't get any metrics.

At Wildfly startup something along the lines of: "MicroProfile Telemetry started..." is logged.

If I manually add the elastic-apm-agent.jar to JAVA_OPTS I automatically get metrics. But my understanding is that I should instead use the opentelemetry and microprofile.telemetry subsystem.

Any thoughts why I'm not getting metrics?

[Christoffer A. Nilsen]

An update...

After reading some more in the Wildfly Admin Guide it seems like I needed to add the micrometer subsystem to get JVM metrics.

Now I can see my metric documents in elastic, however Kibana Observability does not seem to support whatever format micrometer is producing (assuming otel).

Anyone know:

1. Does Kibana Observability support the format micrometer is producing?
2. Do I need microprofile.telemetry subsystem if I want to do Tracing and Metrics?
   1. What is the purpose of the microprofile.telemetry subsystem?

I'm thinking maybe Kibana Observability does not support OTEL out of the box, assuming micrometer subsystem produces OTEL standard when I'm using the OpenTelemetry Protocol. Maybe I have to use the elastic-apm-agent.

[Jason Lee]

1. The Micrometer subsystem does, indeed, push using OTLP, so your receiver will need to be able to consume that. I don't know if Kibana Observability does, though.
2. MicroProfile Telemetry (and the OpenTelemetry subsystem it builds on) provides observability support for metrics, tracing, and logs via the OpenTelemetry API (and wire protocol). If you're using Micrometer for metrics, and don't need tracing or logging, then you don't need this subsystem. If you DO need tracing, then this is relevant. Which subsystem to use depends on your application (e.g., which API -- Micrometer or OpenTelemetry -- the applications wants or what the developer prefers). As far as metrics are concerned, the two are functionally equivalent, roughly, and are offered as options for WildFly users.

Jason Lee

Principal Software Engineer

Red Hat JBoss EAP

Java Champion

--
You received this message because you are subscribed to the Google Groups "WildFly" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wildfly+u...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/wildfly/8b5574a1-4a89-41ab-ad7a-f1b946a59d59n%40googlegroups.com.