Loading...

XML

Word

Printable

Type: Bug
Resolution: Duplicate
Priority: Major
Fix Version/s: None
Affects Version/s: 28.0.0.Final, 28.0.1.Final, 29.0.0.Final, 29.0.1.Final, 30.0.0.Beta1
Component/s: OpenTelemetry
Labels:
None

Steps to Reproduce:
Hide

Configure the service-name attribute of the opentelemetry subystem

Do a traced call

Check the trace collector (e.g. Jaeger) => the configured service name is ignored, the deployment name is used instead
Show
Configure the service-name attribute of the opentelemetry subystem Do a traced call Check the trace collector (e.g. Jaeger) => the configured service name is ignored, the deployment name is used instead
[QE] How to address?:
---
[QE] Why QE missed?:
---

During a preliminary upgrade to the latest WildFly version (30.0.0.Beta1 at the time) and when checking the traces reported by OpenTelemetry it appeared that the set service name (https://docs.wildfly.org/29/wildscribe/subsystem/opentelemetry/index.html#attr-service-name) is ignored.
Digging a bit deeper revealed that this is related to https://issues.redhat.com/browse/WFLY-17156. As part of the changes done with this story, the service name is always overwritten with the deployment name.