-
Bug
-
Resolution: Done
-
Blocker
-
None
If you check the "12.5. Configuring the opentelemetry subsystem" paragraph in Using-JBoss-EAP-XP-5.0.pdf
(preview of existing XP5 documentation) and the other opentelemetry related content, it looks that it needs to be updated;
E.g.
embed-server
/extension=org.wildfly.extension.opentelemetry:add
/subsystem=opentelemetry:add
reload
/subsystem=opentelemetry:write-attribute(name=exporter-type, value=jaeger)
{
"outcome" => "failed",
"failure-description" => "WFLYOTELEXT0013: The 'jaeger' exporter is no longer supported. Please update the system to use otlp.",
"rolled-back" => true
}
Most probably the whole chapter 12 needs to be reviewed in light of the XP5 upgrade; for example in "12.6. Using Jaeger to observe the OpenTelemetry traces for an application" we are still using jaeger which, as the command above suggests, is no longer supported:
$ docker run -d --name jaeger \ -e COLLECTOR_ZIPKIN_HOST_PORT=:9411 \ -p 5775:5775/udp \ -p 6831:6831/udp \ -p 6832:6832/udp \ -p 5778:5778 \ -p 16686:16686 \ -p 14268:14268 \ -p 14250:14250 \ -p 9411:9411 \ jaegertracing/all-in-one:1.29
We can use https://github.com/jbossas/eap-quickstarts/tree/xp-5.0.x/opentelemetry-tracing as inspiration and also the Micrometer paragraph might be useful for the "otel-collector" part;
- documents
-
-
- Closed
-
- is cloned by
-
-
- New
-