-
Notifications
You must be signed in to change notification settings - Fork 404
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
Send heroku router stats like in other languages #108
Comments
We're discussing this right now, and we'll be adding this somewhere between soon and very soon. Thanks for bringing this up! |
That's great, thanks a lot! Will definitely candidate it if you need beta testers ! |
Agreed this is needed. We have a simple and stable app that has very consistent app server response times. So while the app server looks like its performing great we really have no idea how long requests are taking because we have no insight into how long they were in the router queue before they hit our app. This makes if very difficult to scale appropriately. |
👍 |
Looks like this was added in 1.8.1. I haven't be able to test it yet. https://docs.newrelic.com/docs/release-notes/agent-release-notes/nodejs-release-notes/node-agent-181 |
@tehnrd excellent! |
…/graphql-koa-dataloader/app/semver-6.3.1 chore(deps): bump semver from 6.3.0 to 6.3.1 in /graphql-koa-dataloader/app
…6e3d57ccad14666379 [Snyk] Security upgrade newrelic from 10.0.0 to 10.3.1
package.json: do not bundle versioned tests
If I'm not mistaken, the Node.js agent doesn't support frontend queueing stats like the Ruby one, via the x-request-start header.
That would be extremely helpful to debug heroku issues!
Thanks,
The text was updated successfully, but these errors were encountered: