Closed stevenhurd closed 8 months ago
@stevenhurd thanks for the enhancement request! We'll be reviewing this internally
@stevenhurd our team has agreed to pull this into our backlog. We cannot commit to a timeframe but as we plan work for future quarters, this will be considered. Thanks for the suggestion!
Jira CommentId: 218191 Commented by rkaran:
Hi, is there any timeline or ETA we can expect for this, surely there are many customers now on the newer versions who are requesting this?
Not at the moment.
We do not have this planned for the Jul-Sep quarter but we're discussing whether this is something we could explore in the quarter after that.
This issue was resolved in #1675, available in the latest agent release.
Is your feature request related to a problem? Please describe.
Currently, it doesn't appear that the New Relic Java Agent supports interface driven annotations for Spring controllers. For example, see the following:
interface
controller
Spring will pick this up (since Spring 5.1) and route the requests properly. The New Relic Agent, however, will ignore this controller class and not instrument it for Transactions.
This feature is necessary when using something like OpenAPI to generate server-side interfaces (published in an artifact). This allows us to keep the implementation and API definition in sync rather than relying on manually creating request mappings in our implementation.
Feature Description
Support for request mapping annotations at the interface level.
Describe Alternatives
The only alternatives are manually doing a
setTransactionName
in the implementation or copying the request mapping annotations.Additional context
Add any other context here.
Priority
Please help us better understand this feature request by choosing a priority from the following options: [Nice to Have, Really Want, Must Have, Blocker]