-
Notifications
You must be signed in to change notification settings - Fork 9
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
[issue] possible issue with opentelemetry on deployment #811
Comments
Hi @matoni109, thanks for notifying us of this issue! It looks like the same issue to me too. Looks like the fix has not been released yet in the OpenTelemetry packages. You can disable the fs instrumentation from our end for now by configuring the // appsignal.cjs
const { Appsignal } = require("@appsignal/nodejs");
new Appsignal({
// ...
disableDefaultInstrumentations: ["@opentelemetry/instrumentation-fs"]
}); |
For the AppSignal team: let's wait until the next release is out and test if it's fixed by that. |
Thanks @tombruijn, We will wait for the next release, and then try and push to staging then, we couldn't get this to replicate in local dev. |
Waiting for an OpenTelemetry release with the fix |
We're going to remove the fs instrumentation by default in issue #845 until this is resolved. |
Closing this issue because it is archived on its parent project. |
We removed the instrumentation default in package version 3.0.7. Please upgrade and let us know if it still happens. |
Hello appSignal 👋,
Just trying to bump to your
v3
node package, but I'm getting below which I think might be inherited from this issue over at OpenTelemetry:The text was updated successfully, but these errors were encountered: