Skip to content

Commit 648f05d

Browse files
authored
fix(js): Correct function names for startProfiler #11944
1 parent 139aef0 commit 648f05d

File tree

1 file changed

+3
-3
lines changed
  • docs/platforms/javascript/guides/node/profiling

1 file changed

+3
-3
lines changed

docs/platforms/javascript/guides/node/profiling/index.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -101,7 +101,7 @@ _(New in version 8.28.0)_
101101

102102
The current profiling implementation stops the profiler automatically after 30 seconds (unless you manually stop it earlier). Naturally, this limitation makes it difficult to get full coverage of your app's execution. We now offer an experimental continuous mode, where profiling data is periodically uploaded while running, with no limit on how long the profiler may run.
103103

104-
To get started with continuous profiling, you can start and stop the profiler directly with `Sentry.profiler.startProfiling` and `Sentry.profiler.stopProfiling`.
104+
To get started with continuous profiling, you can start and stop the profiler directly with `Sentry.profiler.startProfiler` and `Sentry.profiler.stopProfiler`.
105105

106106
<Note>
107107

@@ -116,11 +116,11 @@ Sentry.init({
116116
dsn: "___PUBLIC_DSN___",
117117
});
118118

119-
Sentry.profiler.startProfiling();
119+
Sentry.profiler.startProfiler();
120120

121121
// run some code here
122122

123-
Sentry.profiler.stopProfiling();
123+
Sentry.profiler.stopProfiler();
124124
```
125125

126126
These new APIs do not offer any sampling functionality—every call to start the profiler will run and start sending profiling data. If you are interested in reducing the amount of profiles that run, you must take care to do it at the callsites.

0 commit comments

Comments
 (0)