-
Notifications
You must be signed in to change notification settings - Fork 400
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Express with custom router #115
Comments
Take a look at the instructions for using the API to name transactions. You'll want to either use rules to rename URLs to paths, or figure out how to monkeypatch There are a thousand routers on npm, and it's pretty unlikely we'll auto-instrument most of them, but if you're interested in seeing support for Thanks for getting in touch, and I hope my answers are useful! |
…/code-level-metrics/express/word-wrap-1.2.4 chore(deps-dev): bump word-wrap from 1.2.3 to 1.2.4 in /code-level-metrics/express
Release v7.0.0
…/async-2.6.4 Bump async from 2.6.3 to 2.6.4
Added workflow to prepare release
Added workflow to prepare release
In my app I'm using Express with a catch-all route, that then gets interpreted by https://github.com/kieran/barista. So all my requests show up in New Relic as
GET *
.What possibility do I have to instrument the router or to help newrelic figure out the route actual route being used?
The text was updated successfully, but these errors were encountered: