Add new explore folder (#10211)

* add new explore folder * Update docs/product/explore/index.mdx Co-authored-by: Liza Mock <[email protected]> * docs(browser): Add missing client param to startBrowserTracingPageLoadSpan (#10215) * Adjust Next.js manual setup docs to be in line with wizard (#10156) Co-authored-by: vivianyentran <[email protected]> * fix(apple): Remove new in version mentions (#10217) Remove new in version mentions for basic options for v 7.x that was released over 1.5 years ago * feat(ruby): Add new onboarding component (#10222) * rm banner for supabase workshop (#10225) * rm banner for supabase workshop * [getsentry/action-github-commit] Auto commit --------- Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com> * fix(issues): severity -> actionability (#10227) * update event detail mentions (#10187) * update event detail mentions * Update docs/product/performance/web-vitals/index.mdx * small tweaks to trace details page * Update docs/product/performance/transaction-summary.mdx Co-authored-by: vivianyentran <[email protected]> * Update docs/concepts/key-terms/tracing/distributed-tracing.mdx * Update docs/platforms/java/guides/spring/advanced-usage.mdx * Update docs/product/performance/resources.mdx Co-authored-by: vivianyentran <[email protected]> * Update docs/product/performance/web-vitals/index.mdx Co-authored-by: vivianyentran <[email protected]> * Update docs/concepts/key-terms/tracing/index.mdx * Update docs/product/performance/mobile-vitals/screen-loads.mdx * Update docs/product/performance/queries.mdx * add redirect * Update docs/concepts/key-terms/tracing/distributed-tracing.mdx * Update docs/platforms/java/guides/spring/advanced-usage.mdx * Update docs/product/performance/queries.mdx * Update docs/concepts/key-terms/tracing/index.mdx * Update docs/product/performance/mobile-vitals/screen-loads.mdx * Update docs/product/performance/transaction-summary.mdx * Update docs/product/performance/resources.mdx * Update docs/product/performance/web-vitals/index.mdx --------- Co-authored-by: vivianyentran <[email protected]> * Update trace view to trace details to reflect UI changes (#10201) Update this docs page to reflect the new name. * feat(python): Use onboarding feature toggles & dedup (#10166) * add missing import (#10214) * fix(node): Fix onboarding import hiding options (#10235) * Fix relay redirects (#10239) * Un-mark bun as beta, cleanup some stuff (#10234) * docs(react): correct import in React v8 migration docs (#10232) * Fix onboarding options jumping (#10236) * fix: don't add padding to onboarding options when they're sticking * delete console.log * fix typo * remove rounded corners from OnboardingOptionButtons --------- Co-authored-by: Stephanie Anderson <[email protected]> * Add section to source maps troubleshooting, suggesting to check source fetching setting (#10230) * Rchhabria/laravel updates (#10202) * laravel blurb * laravel blurb * Create .img * Delete docs/platforms/php/.img * added new forge imgaes * fixed file path * fixed file path * Cache instrumentation links (#10155) * fix: hide platforms with no cache custom instrumentation on cache instrumentation page * add node cache cache instrumentation redirect * add metrics section and update perf modules (#10209) --------- Co-authored-by: Liza Mock <[email protected]> Co-authored-by: Andrei <[email protected]> Co-authored-by: Luca Forstner <[email protected]> Co-authored-by: Philipp Hofmann <[email protected]> Co-authored-by: Neel Shah <[email protected]> Co-authored-by: elijames-codecov <[email protected]> Co-authored-by: getsantry[bot] <66042841+getsantry[bot]@users.noreply.github.com> Co-authored-by: Matt Duncan <[email protected]> Co-authored-by: Ivana Kellyerova <[email protected]> Co-authored-by: Johan Wänglöf <[email protected]> Co-authored-by: Francesco Novy <[email protected]> Co-authored-by: Stephanie Anderson <[email protected]> Co-authored-by: Rob Hannay <[email protected]> Co-authored-by: abdellah hariti <[email protected]> Co-authored-by: Rahul Chhabria <[email protected]>
getsentry · Jun 4, 2024 · 0e2b79c · 0e2b79c
1 parent 9f35518
commit 0e2b79c
Show file tree

Hide file tree

Showing 134 changed files with 182 additions and 135 deletions.
diff --git a/docs/cli/metrics.mdx b/docs/cli/metrics.mdx
@@ -4,7 +4,7 @@ sidebar_order: 5
 description: "Learn how Sentry's command line interface can be used for sending metrics."
 ---
 Metrics help you track and visualize the data points you care about, making it easier to monitor your application's health and identify issues.
-Learn more about [Metrics](/product/metrics).
+Learn more about [Metrics](/product/explore/metrics).
 
 ## Requirements
 - [Install](/product/cli/installation) the Sentry CLI (min v2.32.0).
@@ -35,7 +35,7 @@ sentry-cli send-metric increment -n "MyMetric" -u "MyUnit" -t "tag1:val1","tag2:
 ```
 
 The metric's name, unit, and tags will undergo normalization to only include supported characters.
-Learn more about [Limits and Restrictions](/product/metrics/#limits-and-restrictions).
+Learn more about [Limits and Restrictions](/product/explore/metrics/#limits-and-restrictions).
 
 ### Counters
 To increment a counter metric by one, you only need to provide the `--name` or `-n` parameter.

diff --git a/docs/concepts/key-terms/enrich-data/index.mdx b/docs/concepts/key-terms/enrich-data/index.mdx
@@ -64,7 +64,7 @@ For instance, the Discover query below displays all the errors (total of 143 eve
 
 ![Discover Query](./img/004.png)
 
-Learn more in [Discover](/product/discover-queries/).
+Learn more in [Discover](/product/explore/discover-queries/).
 
 ### Ownership Rules
 

diff --git a/docs/concepts/key-terms/key-terms.mdx b/docs/concepts/key-terms/key-terms.mdx
@@ -50,7 +50,7 @@ Each of these key features in [sentry.io](https://sentry.io) is represented by a
 
 - **Dashboards** - Provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more **Discover** or **Issues** queries. Learn more in the full [Dashboards documentation](/product/dashboards/).
 
-- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/discover-queries/).
+- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/explore/discover-queries/).
 
 - **Issues** - Displays information about grouped problems in your application. From here, you can go to the **Issue Details** page for a more granular view of any issue. Learn more in the full [Issues documentation](/product/issues/).
 

diff --git a/docs/concepts/key-terms/tracing/distributed-tracing.mdx b/docs/concepts/key-terms/tracing/distributed-tracing.mdx
@@ -243,4 +243,4 @@ Put simply: as a result of this head-based approach, where the decision is made
 
 ## Viewing Trace Data
 
-Through [Performance](/product/performance/) and [Discover](/product/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page.
+Through [Performance](/product/performance/) and [Discover](/product/explore/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page.
diff --git a/docs/concepts/key-terms/tracing/event-detail.mdx b/docs/concepts/key-terms/tracing/event-detail.mdx
diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx
@@ -50,7 +50,7 @@ Here are some examples of valid comparison operator searches:
 
 <Note>
 
-`OR` and `AND` search conditions are only available for [Discover](/product/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
+`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
 
 </Note>
 

diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx
@@ -4,7 +4,7 @@ description: "Learn more about searchable session replay properties."
 sidebar_order: 30
 ---
 
-[Session Replay](/product/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI.
+[Session Replay](/product/explore/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI.
 
 You can search by session replay properties on the **Replay** page.
 
@@ -102,7 +102,7 @@ The `title` of an element that was clicked. For example, `Save this comment` wou
 
 ### `count_dead_clicks`
 
-The number of [dead clicks](https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds) within a replay.
+The number of [dead clicks](https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds) within a replay.
 
 - **Type:** number
 
@@ -114,7 +114,7 @@ The number of errors within a replay.
 
 ### `count_rage_clicks`
 
-The number of [rage clicks](<https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
+The number of [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>) within a replay.
 
 - **Type:** number
 
@@ -132,7 +132,7 @@ The number of URLs that the user visited during a replay recording.
 
 ### `dead.selector`
 
-Similar to the `click.selector` search property, but only queries on [dead clicks](https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [dead clicks](https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 
@@ -216,7 +216,7 @@ The id of the project.
 
 ### `rage.selector`
 
-Similar to the `click.selector` search property, but only queries on [rage clicks](<https://docs.sentry.io/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
+Similar to the `click.selector` search property, but only queries on [rage clicks](<https://docs.sentry.io/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks>). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element `<span id="section-1" class="active" role="button"/>`. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported.
 
 - **Type:** string
 

diff --git a/docs/organization/integrations/session-replay/index.mdx b/docs/organization/integrations/session-replay/index.mdx
@@ -6,7 +6,7 @@ description: "Learn more about third-party session replay integrations."
 
 <Note>
 
-Looking for Sentry's built-in Session Replay product? Click <a class href="/product/session-replay/">here</a> to learn more.
+Looking for Sentry's built-in Session Replay product? Click <a class href="/product/explore/session-replay/">here</a> to learn more.
 
 </Note>
 

diff --git a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx
@@ -105,7 +105,7 @@ With this feature, the SDK differentiates between four different app start types
 - **Prewarmed cold start**
 - **Prewarmed warm start**
 
-You can filter for different app start types in [Discover](/product/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`.
+You can filter for different app start types in [Discover](/product/explore/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`.
 
 To enable prewarmed app start tracing:
 

diff --git a/docs/platforms/dotnet/common/profiling/index.mdx b/docs/platforms/dotnet/common/profiling/index.mdx
@@ -6,7 +6,7 @@ sidebar_order: 5000
 
 <PlatformContent includePath="profiling/index/preface" />
 
-With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments.
+With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments.
 
 <Note>
 

diff --git a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx
@@ -24,6 +24,6 @@ notSupported:
 
 _Import name: `Sentry.browserProfilingIntegration`_
 
-[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment.
+[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment.
 
 Read more about <PlatformLink to='/profiling'>setting up Profiling</PlatformLink>.
diff --git a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx
@@ -24,6 +24,6 @@ supported:
 
 _Import name: `Sentry.nodeProfilingIntegration`_
 
-[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment.
+[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment.
 
 Read more about <PlatformLink to='/profiling'>setting up Profiling</PlatformLink>.
diff --git a/docs/platforms/javascript/common/configuration/integrations/replay.mdx b/docs/platforms/javascript/common/configuration/integrations/replay.mdx
@@ -24,6 +24,6 @@ notSupported:
 
 _Import name: `Sentry.replayIntegration`_
 
-[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools.
+[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools.
 
 Read more about [setting up Session Replay](./../../../session-replay/).
diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx
@@ -21,7 +21,7 @@ description: "Learn how to enable Session Replay in your app if it is not alread
 
 <Include name="feature-stage-beta-session-replay.mdx" />
 
-[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools.
+[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools.
 
 By default, our Session Replay SDK masks all DOM text content, images, and user input, giving you heightened confidence that no sensitive data will leave the browser. To learn more, see <PlatformLink to="/session-replay/privacy">Session Replay Privacy</PlatformLink>.
 

diff --git a/docs/platforms/javascript/common/session-replay/troubleshooting.mdx b/docs/platforms/javascript/common/session-replay/troubleshooting.mdx
@@ -106,7 +106,7 @@ Sentry.replayIntegration({
 
 <Expandable title='I see the message: "A large number of mutations was detected (N). This can slow down the Replay SDK and impact your customers."'>
 
-The Sentry SDK attempts to minimize potential [performance overhead](/product/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change.
+The Sentry SDK attempts to minimize potential [performance overhead](/product/explore/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change.
 
 If you're seeing the "A large number of mutations was detected" message while watching a replay, it means that your page could be optimized. For example, a dropdown list with thousands of entries could be refactored so that rows are virtualized where only the visible rows are rendered in the DOM. Another potential solution is to paginate the results fetch more data as the user scrolls through it. The SDK has a <PlatformLink to="/session-replay/configuration/#mutation-limits">configuration</PlatformLink> that allows you to configure the limits before recording stops.
 </Expandable>

diff --git a/docs/platforms/php/common/profiling/index.mdx b/docs/platforms/php/common/profiling/index.mdx
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry PHP SDK version `3.15.0` and above.
 
 </Note>
 
-With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
+With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.

diff --git a/docs/platforms/php/guides/laravel/profiling/index.mdx b/docs/platforms/php/guides/laravel/profiling/index.mdx
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Laravel SDK version `3.3.0` and above
 
 </Note>
 
-With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
+With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.

diff --git a/docs/platforms/php/guides/symfony/profiling/index.mdx b/docs/platforms/php/guides/symfony/profiling/index.mdx
@@ -10,7 +10,7 @@ Profiling for PHP is supported with Sentry Symfony SDK version `4.7.0` and above
 
 </Note>
 
-With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
+With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments.
 
 Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer).
 The Excimer PHP extension supports PHP 7.2 and up.

diff --git a/docs/platforms/react-native/profiling/troubleshooting/index.mdx b/docs/platforms/react-native/profiling/troubleshooting/index.mdx
@@ -13,7 +13,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t
 
 ### Limitations
 
-Because profile samples are collected at a fixed sampling frequency, we recommend checking if profiling's [Performance Overhead](/product/profiling/performance-overhead) is acceptable for your use case. Note that
+Because profile samples are collected at a fixed sampling frequency, we recommend checking if profiling's [Performance Overhead](/product/explore/profiling/performance-overhead) is acceptable for your use case. Note that
 we're working on symbolication of the collected profiles which means that at the moment you'll see only function names but not resolved source file paths.
 
 As always, and especially since Profiling in React Native is an alpha feature, feedback is welcome on [Discord](https://discord.com/channels/621778831602221064/750735628932612096) or [GitHub](https://github.com/getsentry/sentry-react-native/issues/2668).
diff --git a/docs/pricing/index.mdx b/docs/pricing/index.mdx
@@ -54,7 +54,7 @@ Performance Units can be used towards multiple Performance event types, dependin
 | Event Type | Unit Value | |
 |---|---|---|
 | Transactions | 1 Unit | Sent by SDKs with only [Tracing](/product/sentry-basics/tracing/) enabled |
-| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/profiling/) enabled |
+| Transactions with Profiling | 1.3 Units | Sent by SDKs with both [Tracing](/product/sentry-basics/tracing/) & [Profiling](/product/explore/profiling/) enabled |
 
 | Total Performance Unit Volume | Team Prepaid | Team On-Demand | Business Prepaid | Business On-Demand |
 |---|---|---|---|---|