You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I’m always frustrated when trying to monitor applications built with the Hono JS framework using New Relic. As Hono is gaining popularity as a fast and minimalist web framework for JavaScript, it would be beneficial to have out-of-the-box support for tracing and performance monitoring in New Relic. Currently, there is no official support for Hono, making it challenging to integrate application and database traces seamlessly.
Feature Description
I would like to request official support for the Hono JS framework in the New Relic Node.js APM agent. This feature would allow users to automatically trace routes and middleware within Hono applications, as well as integrate seamlessly with database drivers for capturing detailed traces of application and database interactions. Ideally, this would include automatic instrumentation for Hono route handlers, response times, and error tracking, aligning with the existing support New Relic provides for other frameworks.
Describe Alternatives
The alternative at present is to use custom instrumentation via New Relic’s API, which requires significant setup and maintenance, especially for applications with multiple routes and database calls. Another alternative is to use OpenTelemetry for manual instrumentation, but this adds complexity and lacks the streamlined experience of using New Relic’s native support for other frameworks.
Additional context
As Hono continues to grow in adoption within the JavaScript ecosystem, official New Relic support would encourage developers to use New Relic as their APM provider with Hono applications. Support for Hono would also make New Relic more appealing to developers seeking lightweight, high-performance frameworks.
Priority
Really Want
This request highlights the growing need for Hono support and the advantages of integrating it into New Relic’s APM tool.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I’m always frustrated when trying to monitor applications built with the Hono JS framework using New Relic. As Hono is gaining popularity as a fast and minimalist web framework for JavaScript, it would be beneficial to have out-of-the-box support for tracing and performance monitoring in New Relic. Currently, there is no official support for Hono, making it challenging to integrate application and database traces seamlessly.
Feature Description
I would like to request official support for the Hono JS framework in the New Relic Node.js APM agent. This feature would allow users to automatically trace routes and middleware within Hono applications, as well as integrate seamlessly with database drivers for capturing detailed traces of application and database interactions. Ideally, this would include automatic instrumentation for Hono route handlers, response times, and error tracking, aligning with the existing support New Relic provides for other frameworks.
Describe Alternatives
The alternative at present is to use custom instrumentation via New Relic’s API, which requires significant setup and maintenance, especially for applications with multiple routes and database calls. Another alternative is to use OpenTelemetry for manual instrumentation, but this adds complexity and lacks the streamlined experience of using New Relic’s native support for other frameworks.
Additional context
As Hono continues to grow in adoption within the JavaScript ecosystem, official New Relic support would encourage developers to use New Relic as their APM provider with Hono applications. Support for Hono would also make New Relic more appealing to developers seeking lightweight, high-performance frameworks.
Priority
Really Want
This request highlights the growing need for Hono support and the advantages of integrating it into New Relic’s APM tool.
The text was updated successfully, but these errors were encountered: