Exclude uri from otel tracing

[mcruzdev]

What

This pull request creates a new BuildItem that is used for drop uri from tracing when using quarkus-opentelemetry extension. The DropApplicationUrisBuildItem is generated from the scanning of the @Traceless annotation.

The @Traceless annotation is used with the jakarta.ws.rs.Path annotation. If annotated at class level all uri below will be ignored for tracing.

If your @Path annotation contains expression like @Path("/cars/{carId}") the extension will ignore all thing after cars using, e.g. cars*.

Why

You can see the issue below, or directly this Stackoverflow discussion.

Fixes #42659

[quarkus-bot]

Thanks for your pull request!

Your pull request does not follow our editorial rules. Could you have a look?

• description should not be empty, describe your intent or provide links to the issues this PR is fixing (using Fixes #NNNNN) or changelogs

_{This message is automatically generated by a bot.}

[quarkus-bot]

/cc @brunobat (opentelemetry), @radcortez (opentelemetry)

[mcruzdev]

First draft pull request. Feel free to add any suggestions!

cc: @brunobat

[brunobat]

I think this is moving in the right direction @mcruzdev.
I think you should add a property where you could add a list of strings with paths that can be ignored.
it you could add a test in quarkus-integration-test-opentelemetry it would be great.

[github-actions]

🎊 PR Preview 1b11ce1 has been successfully built and deployed to https://quarkus-pr-main-43885-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.