OpenTelemetry Service Name Configuration

[Roland Spindelbalker-Davila]

Hi,

we are once again trying to preliminary upgrade to the latest WildFly version (30.0.0.Beta1 at the time) and when checking the traces reported by OpenTelemetry we noticed that the set service name (https://docs.wildfly.org/29/wildscribe/subsystem/opentelemetry/index.html#attr-service-name) is ignored.

I dug a bit deeper, and it seems that it is related to https://issues.redhat.com/browse/WFLY-17156. Starting from this, the service name is always overwritten with the deployment name.

Has this been done on purpose, and if so, are there plans to support overwriting the service name again, or not?

Thanks for looking into the issue

Roland Spindelbalker-Davila

[Brian Stansberry]

Hi Roland.

Thanks for the report. Can you file a JIRA at https://issues.redhat.com/projects/WFLY for this?  "OpenTelemetry" component. This sounds like a bug. The attribute exists and is not marked in the management API as deprecated with some text explaining why it might not work, so it seems there's a bug.

I have no idea what the fix would be, i.e. whether it would be to make it work or to properly document that it doesn't. But a JIRA would start the process of figuring that out.

Best regards,

Brian

[Roland Spindelbalker-Davila]

Done, thank you :D

https://issues.redhat.com/browse/WFLY-18631

[Brian Stansberry]

Thanks!