In a recent post, I worked through setting up OpenTelemetry support in your Jakarta EE application. Since that time, I’ve put quite a bit of work into integrating that support, as teased in the post, into WildFly. In this post, I’d like to provide an update on what that WildFly support currently looks like, and put out a request for feedback.
To get started experimenting with my changes, you need to do one of two things:
As it stands now, it seems to work really well. In designing and implementing what I have so far, I’ve discussed things internally with other Red Hat engineers in the observability space, as well as with some in the CNCF Slack channel, but more input would be extremely helpful.
Are there features you’d like to see?
Are there any changes you’d like to see in the configuration?
Is there anything missing in the runtime support that you’d like to see?
Currently, the service name is the same for all applications deployed to a given WildFly instance. Is that acceptable? If not, if it’s technically possible, would a per-app service name be preferable?
Any and all feedback is welcome. You can always find me on Twitter or, better yet, comment on the issue in JIRA.