You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/platforms/javascript/guides/node/index.mdx
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ yarn add @sentry/node
33
33
34
34
## Configure
35
35
36
-
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application - otherwise, auto-instrumentation of these modules will _not_ work.
36
+
Sentry should be initialized as early in your app as possible. It is essential that you call `Sentry.init` before you require any other modules in your application — otherwise, auto-instrumentation of these modules will _not_ work.
37
37
38
38
Once this is done, Sentry's Node SDK captures unhandled exceptions as well as tracing data for your application.
39
39
@@ -43,7 +43,7 @@ Therefore, we recommend to create a file named `instrumentation.js` that imports
43
43
44
44
If you set a `tracesSampleRate`, performance instrumentation will automatically be enabled for you. See <PlatformLinkto="/performance/instrumentation/automatic-instrumentation">Automatic Instrumentation</PlatformLink> to learn about all the things that the SDK automatically instruments for you.
45
45
46
-
You can also manually capture performance data - see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
46
+
You can also manually capture performance data — see <PlatformLinkto="/performance/instrumentation/custom-instrumentation">Custom Instrumentation</PlatformLink> for details.
0 commit comments