Closed wdemis closed 4 months ago
Hi @wdemis
I tried to repro the issue using the attached sample Jersey app (created from the maven archetype -DarchetypeArtifactId=jersey-quickstart-grizzly2
) and the PATCH
method was reporting properly as WebTransaction/RestWebService/myresource (PATCH)
Can you provide a simple repro? There's obviously something different in your project that's not part of my simple app. Thanks! simple-service.zip
Closing. We'll need to have a viable repro app in order to investigate this further.
Transaction name does not seem to be set properly for PATCH requests when using Jersey
Description
We noticed that GET, PUT, POST, DELETE web request verbs will cause NewRelic to generate transactions with "name" set to:
WebTransaction/RestWebService/v1/actions/{actionId} (GET)
however the PATCH requests are being set to:WebTransaction/Servlet/jersey
Expected Behavior
The expectation is that all web requests return a consistent transaction name. For PATCH requests, we'd expect it to look similar to the other requests. In our case:
WebTransaction/RestWebService/v1/actions/{actionId} (PATCH)
Troubleshooting
We setup two basic web request handlers in a controller. We setup NewRelic to run locally so that we could monitor the logs while debugging. Controller code was:
Hitting both endpoints produces the following logs:
Steps to Reproduce
Create a jersey controller with a PATCH request handler. Hit endpoint and check NewRelic logs or Transactions table for transaction name.
Your Environment
Additional context
This resolved issue sure seems very similar; perhaps this was addressed for Spring and not Jersey?