-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Misleading "Tracing extension 'startTransaction' has not been added." message #8361
Comments
Hi, can you share your Sentry.init() code. Thanks! |
Apologies, I really thought that was irrelevant here 🙂 import * as Sentry from '@sentry/node';
Sentry.init({
// dsn & stuff
defaultIntegrations: false,
tracesSampleRate: 1,
integrations: [
new Sentry.Integrations.FunctionToString(),
new Sentry.Integrations.ContextLines(),
new Sentry.Integrations.LinkedErrors(),
],
}); |
Can you doublecheck that you're calling Sentry.init() before you're calling |
Just checked again, we do |
Or, actually, I was missing an environment variable.
|
I am sorry, let's repurpose this issue 🙂 |
This issue has gone three weeks without activity. In another week, I will close it. But! If you comment or otherwise update it, I will reset the clock, and if you label it "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
I am seeing this misleading error message too, and yes, it resulted from the failure to call Sentry.init(). |
Tracking in #8624 |
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/node
SDK Version
7.55.2
Issue
Calling
Sentry.startTransaction()
without callingSentry.init()
first yields the following note:Most often,
Sentry.init
was not called, and the above message is slightly misleading 🙂The text was updated successfully, but these errors were encountered: