Skip to content

Commit e427276

Browse files
authored
revert performance API docs while we fix exports (#7766)
1 parent 9dab49f commit e427276

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

src/platforms/common/performance/instrumentation/custom-instrumentation.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -37,15 +37,15 @@ To capture transactions and spans customized to your organization's needs, you m
3737

3838
</Note>
3939

40-
<PlatformSection notSupported={["javascript", "node"]}>
40+
<PlatformSection notSupported={[" "]}>
4141

4242
<PlatformContent includePath="performance/enable-manual-instrumentation" />
4343

4444
<PlatformContent includePath="performance/add-spans-example" />
4545

4646
</PlatformSection>
4747

48-
<PlatformSection supported={["javascript", "node"]}>
48+
<PlatformSection supported={[" "]}>
4949

5050
To add custom performance data to your application, you need to add custom instrumentation in the form of spans. Spans are a way to measure the time it takes for a specific action to occur. For example, you can create a span to measure the time it takes for a function to execute.
5151

@@ -97,7 +97,7 @@ Sentry maintains a [list of well known span operations](https://develop.sentry.d
9797

9898
</PlatformSection>
9999

100-
<PlatformSection notSupported={["java", "native", "apple", "javascript", "node"]}>
100+
<PlatformSection notSupported={["java", "native", "apple"]}>
101101

102102
<PlatformContent includePath="performance/retrieve-transaction" />
103103

0 commit comments

Comments
 (0)