René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"✨ Add support for filtering requests to APIS defined with JAX-RS","articleBody":"\u003c!--\r\nWelcome to the Hypertrace repo!\r\n\r\n- Please be respectful and considerate of others when commenting on issues.\r\n- Please search for existing issues in order to make sure we don't have duplicate bugs/feature requests.\r\n- If you have a question please ask it on our Slack chat https://join.slack.com/t/hypertrace/shared_invite/zt-hgjlblic-Tq2_N4sHJj4RMqx5nirS9w instead of creating an issue.\r\n- Please provide as much information as possible so we all understand the issue.\r\n--\u003e\r\n\r\n## Use Case\r\nWe should support filtering requests made to APIs defined with the JAX-RS API, just as we do for the Java EE Servlet API. \r\n\r\n## Proposal\r\nI think it will likely make sense to leverage similar strategies for instrumenting JAX-RS resources as is done by OpenTelemetry (in [these](https://github.com/open-telemetry/opentelemetry-java-instrumentation/tree/b4cab9ba365aab67e52d0ac1d4c24d54f4712604/instrumentation/jaxrs/jaxrs-2.0) modules). We'll likely be able to do the bulk of the work according to the JAX-RS API with minor tweaks here and there for each JAX-RS implementation we want to support.\r\n\r\n## Questions to address (if any)\r\nThe specific use case I'm trying to help solve is a Jersey JAX-RS web application running on Jetty leveraging Dropwizard. It's possible it could make sense to add support for this use case by targeting Jetty internals like we do for Netty, which is another solution worth considering \r\n","author":{"url":"https://github.com/ryandens","@type":"Person","name":"ryandens"},"datePublished":"2021-05-24T22:19:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/320/javaagent/issues/320"}