We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
At Victor we use New Relic to allow us to get a deep understanding of how our code is performing in our deployed environments.
We want to use New Relics custom tracer functionality within our fortune instances to log a detailed breakdown of where time is being spent within a transaction, without embedding new relic as a dependency of fortune. https://docs.newrelic.com/docs/agents/nodejs-agent/supported-features/nodejs-custom-instrumentation#expanding-instrumentation
To achieve this we'll provide extension points at critical times within the lifecycle:
The text was updated successfully, but these errors were encountered:
Continuing the list:
Sorry, something went wrong.
No branches or pull requests
At Victor we use New Relic to allow us to get a deep understanding of how our code is performing in our deployed environments.
We want to use New Relics custom tracer functionality within our fortune instances to log a detailed breakdown of where time is being spent within a transaction, without embedding new relic as a dependency of fortune.
https://docs.newrelic.com/docs/agents/nodejs-agent/supported-features/nodejs-custom-instrumentation#expanding-instrumentation
To achieve this we'll provide extension points at critical times within the lifecycle:
The text was updated successfully, but these errors were encountered: