-
Notifications
You must be signed in to change notification settings - Fork 126
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
Appmetrics crashes Node if required after initializing honeycomb-beeline #616
Comments
It appears that the call to |
So am I right in thinking you want to instrument only part of your Node application, excluding
|
@mattcolegate I reached this edge case in a project that was already using Honeycomb instrumentation. Is it impossible to have two instrumentation tools working without this type of conflict? I would like to benefit from the application-level instrumentation Appmetrics enables while still getting the visualization tools Honeycomb provides. |
Also to answer your question directly, yes, I would like to exclude |
What is wrong
Requiring appmetrics any point after calling
require('honeycomb-beeline')()
causes this nasty stack:What is expected
Appmetrics loads without showing
FATAL ERROR
and NodeJS does not exit as a result.Additional info
You can use the following Node application to reproduce the issue:
test.js
package.json
Note that placing the
require('appmetrics')
aboverequire('honeycomb-beeline')()
line does not cause an error, and Node executes as expected.The text was updated successfully, but these errors were encountered: