Michal Vavřík

Is this solved or on your radar @zhfeng @mmusgrov ?

> @michalvavrik I don't recall ever investigating it. You raised the issue so could you not retest it? If not then the transaction team are quite busy: @marcosgopen or @jmfinelli...

sorry @marcosgopen , I had very busy week, sure, there were breaking changes in the meanwhile and I completely forgot about QS PR. Should probably rebase it and resolve conflicts....

@mkouba It could be, but I won't know till I have closer look. Will let you know.

@mkouba Oh yeah, it's related. I'll fix this.

@dependabot rebase

What this issue describes is expected behavior. It comes from OpenTelemetry and there is nothing Quarkus can do about this: https://github.com/quarkusio/quarkus/pull/31356/files I suggested that if we want to verify details...

I mean I'd expect it to be method name or path https://opentelemetry.io/docs/specs/otel/trace/semantic_conventions/instrumentation/graphql/ depending on traced operation.

Re-thinking it - maybe there is some flexibility and we should check with upstream developers.

> @MikeEdgar I Confirm that YES i am using RolesAllowed annotation. > > Still seeing this issue as of 3.2.11 https://github.com/quarkusio/quarkus/pull/38231 wasn't backported to 3.2.11, so that's alright. Can you...