Merge branch 'master' into aliu/unleash

develop-docs/self-hosted/troubleshooting.mdx

@@ -163,7 +163,7 @@ docker compose run --rm -T postgres bash -c "apt update && apt install -y --no-i
 
 If the script above still does not clear up enough disk space, you can try the following in Postgres. This will lead to data loss in event details. _SENTRY_RETENTION_DAYS_ will need to be filled in manually.
 ```sql
-DELETE FROM public.nodestore_node WHERE "timestamp" < NOW() - INTERVAL '[SENTRY_RETENTION_DAYS]';
+DELETE FROM public.nodestore_node WHERE "timestamp" < NOW() - INTERVAL '[SENTRY_RETENTION_DAYS] DAY';
 VACUUM FULL public.nodestore_node;
 ```
 

docs/platforms/java/common/configuration/options.mdx

@@ -162,6 +162,14 @@ _(New in version 6.0.0)_
 
 </ConfigKey>
 
+<ConfigKey name="enable-backpressure-handling">
+
+Set this boolean to `false` to disable automatic downsampling of transactions while the system is under load. The `tracesSampleRate` is halved for every failing health check up to 10 times, (roughly 0.001% of the original `tracesSampleRate`). Any positive health check will reset `tracesSampleRate` to its original value. Health checks run in the background every 10 seconds, checking for queue drops and rate limiting. Note: Starting with version 7.8.0 backpressure handling has changed from opt-in to opt-out.
+
+_(New in version 7.1.0)_
+
+</ConfigKey>
+
 ## Integration Configuration
 
 For many platform SDKs integrations can be configured alongside it. On some platforms that happen as part of the `init()` call, in some others, different patterns apply.

docs/platforms/java/common/configuration/sampling.mdx

@@ -29,6 +29,8 @@ We recommend sampling your transactions for two reasons:
 
 Choose a sampling rate with the goal of finding a balance between performance and volume concerns with data accuracy. You don't want to collect _too_ much data, but you want to collect sufficient data from which to draw meaningful conclusions. If you’re not sure what rate to choose, start with a low value and gradually increase it as you learn more about your traffic patterns and volume.
 
+As of version 7.8.0 of the Java SDK Sentry will automatically downsample while the system is under load. Take a look at <PlatformLink to="/configuration/options/#enable-backpressure-handling"><PlatformIdentifier name="enable-backpressure-handling" /></PlatformLink> for more details or if you would like to opt out of this behaviour.
+
 ## Configuring the Transaction Sample Rate
 
 The Sentry SDKs have two configuration options to control the volume of transactions sent to Sentry, allowing you to take a representative sample:

docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx

@@ -3,6 +3,7 @@ title: BrowserProfiling
 description: "Capture profiling data for the Browser."
 notSupported:
   - javascript.cordova
+  - javascript.capacitor
   - javascript.node
   - javascript.aws-lambda
   - javascript.azure-functions

docs/platforms/javascript/common/configuration/integrations/featureflags.mdx

@@ -37,7 +37,8 @@ If you are using an external feature flag provider, refer to the [supported list
 
 The Feature Flags integration allows you to manually track feature flag evaluations through an API.
 These evaluations are held in memory and sent to Sentry when an error occurs.
-**At the moment, we only support boolean flag evaluations.**
+**At the moment, we only support boolean flag evaluations.** This integration is available in
+Sentry SDK **versions 8.43.0 or higher.**
 
 _Import names: `Sentry.featureFlagsIntegration` and `type Sentry.FeatureFlagsIntegration`_
 

docs/platforms/javascript/common/configuration/integrations/launchdarkly.mdx

@@ -29,7 +29,8 @@ This integration only works inside a browser environment. It is only available f
 
 </Alert>
 
-The [LaunchDarkly](https://launchdarkly.com/) integration tracks feature flag evaluations produced by the LaunchDarkly SDK. These evaluations are held in memory, and in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.**
+The [LaunchDarkly](https://launchdarkly.com/) integration tracks feature flag evaluations produced by the LaunchDarkly SDK. These evaluations are held in memory, and in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** This integration is available in
+Sentry SDK **versions 8.43.0 or higher.**
 
 _Import names: `Sentry.launchDarklyIntegration` and `Sentry.buildLaunchDarklyFlagUsedHandler`_
 

docs/platforms/javascript/common/configuration/integrations/openfeature.mdx

@@ -29,7 +29,8 @@ This integration only works inside a browser environment. It is only available f
 
 </Alert>
 
-The [OpenFeature](https://openfeature.dev/) integration tracks feature flag evaluations produced by the OpenFeature SDK. These evaluations are held in memory, and in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.**
+The [OpenFeature](https://openfeature.dev/) integration tracks feature flag evaluations produced by the OpenFeature SDK. These evaluations are held in memory, and in the event an error occurs, sent to Sentry for review and analysis. **At the moment, we only support boolean flag evaluations.** This integration is available in
+Sentry SDK **versions 8.43.0 or higher.**
 
 _Import name: `Sentry.openFeatureIntegration` and `Sentry.OpenFeatureIntegrationHook`_
 

docs/platforms/javascript/common/feature-flags/index.mdx

@@ -26,7 +26,7 @@ description: With Feature Flags, Sentry tracks feature flag evaluations in your
 
 ## Prerequisites
 
-* You have the <PlatformLink to="/">JavaScript SDK installed</PlatformLink> (version 8.43.0 or higher).
+* You have the <PlatformLink to="/">JavaScript SDK installed</PlatformLink>.
 
 ## Enable Evaluation Tracking
 

docs/platforms/javascript/common/profiling/browser-profiling.mdx

@@ -0,0 +1,83 @@
+---
+title: Browser Profiling
+sidebar_order: 5000
+supported:
+  - javascript
+notSupported:
+  - javascript.bun
+  - javascript.cordova
+  - javascript.capacitor
+  - javascript.deno
+  - javascript.cloudflare
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.fastify
+  - javascript.gcp-functions
+  - javascript.hapi
+  - javascript.koa
+  - javascript.nestjs
+description: "Collect & view performance insights for JavaScript programs with Sentry's JavaScript Profiling integration."
+---
+
+<Note>
+
+Browser Profiling is currently in beta. Beta features are still in progress and may have bugs. We recognize the irony.
+
+</Note>
+
+The browser profiling integration is built using the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/) and will likely only move out of beta once the specification progresses and gains adoption. See [platform status](https://chromestatus.com/feature/5170190448852992).
+
+Note that since the profiling API is currently only exposed in Chromium, profiles collected only include that demographic. We hope that as the API gains adoption, other browsers will implement it as well.
+
+<PlatformContent includePath="profiling/index/why-profiling" />
+
+## Prerequisites
+
+To get started with JavaScript browser profiling, you'll need to:
+
+- Install the <PlatformSdkPackageName fallback="@sentry/browser"/> SDK, minimum version 7.60.0
+- Configure the document response header to include `Document-Policy: js-profiling`
+- Configure the SDK to use the `BrowserProfilingIntegration` and set `profilesSampleRate`
+
+## Step 1: Install the <PlatformOrGuideName/> SDK
+
+<PlatformSection notSupported={["javascript.electron"]}>
+
+Install our <PlatformOrGuideName/> SDK using either `yarn` or `npm`, the minimum version that supports profiling is **7.60.0**.
+
+</PlatformSection>
+
+<PlatformSection supported={["javascript.electron"]}>
+
+Install our Electron SDK using either `yarn` or `npm`, the minimum version that supports profiling is **4.16.0**.
+
+</PlatformSection>
+
+<PlatformContent includePath="profiling/automatic-instrumentation-intro" />
+
+## Step 2: Add Document-Policy: js-profiling header
+
+For the JavaScript browser profiler to start, the document response header needs to include a `Document-Policy` header key with the `js-profiling` value.
+
+<PlatformContent includePath="profiling/automatic-instrumentation-headers" />
+
+## Step 3: Configure the <PlatformOrGuideName/> SDK
+
+Configuration should happen as early as possible in your application's lifecycle. Once this is done, Sentry's JavaScript SDK will capture all unhandled exceptions and transactions.
+
+<PlatformContent includePath="profiling/automatic-instrumentation-setup" />
+
+## The Difference Between DevTools & Sentry's JavaScript Browser Profiler
+
+What does Sentry's JavaScript browser profile offer that Chrome DevTools does not?
+
+- Sentry's JavaScript profiler runs in production and captures real user data, showing real-world performance. DevTools runs locally and only shows profiles of what's running on your machine.
+- Sentry runs at a lower sampling rate of 100Hz with a 10ms sample period versus a sampling rate of 1000Hz and a 1ms sample period for DevTools.
+- Sentry supports deobfuscation, making it so that all the function names in your code are correct. Typically, when you run JavaScript code, it's minified, meaning that all the function names are replaced with machine-generated abbreviations.
+
+Please note, that since the browser profiling API is currently only implemented in Chromium-based browsers, the profiles collected with Sentry's JavaScript browser profiling will inherently be biased toward that demographic. This is something that you'll need to consider if you're basing your decisions on the data collected.
+
+We hope that as the Javascript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository.

docs/platforms/javascript/common/profiling/index.mdx

@@ -1,72 +1,13 @@
 ---
 title: Set Up Profiling
 sidebar_order: 5000
-supported:
-  - javascript
+description: "Collect & view performance insights for JavaScript programs with Sentry's Profiling integrations. Get started with browser and Node.js profiling to understand your application's performance."
 notSupported:
   - javascript.bun
   - javascript.cordova
+  - javascript.capacitor
   - javascript.deno
   - javascript.cloudflare
-description: "Collect & view performance insights for JavaScript programs with Sentry’s JavaScript Profiling integration. Get started with browser profiling here."
 ---
 
-<Note>
-
-Browser Profiling is currently in beta. Beta features are still in progress and may have bugs. We recognize the irony.
-
-</Note>
-
-The browser profiling integration is built using [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/) and will likely only move out of beta once the specification progresses and gains adoption. See platform [status](https://chromestatus.com/feature/5170190448852992).
-
-Note that since the profiling API is currently only exposed in Chromium, profiles collected only include that demographic. This is obvious, but should not be forgotten when analyzing the data collected. We hope that as the API gains adoption, other browsers will implement it as well.
-
-<PlatformContent includePath="profiling/index/why-profiling" />
-
-## Prerequisites
-
-To get started with JavaScript browser profiling, you'll need to:
-
-- Install the <PlatformSdkPackageName fallback="@sentry/browser"/> SDK, minimum version 7.60.0
-- Configure the document response header to include `Document-Policy: js-profiling`
-- Configure the SDK to use the `BrowserProfilingIntegration` and set `profilesSampleRate`
-
-## Step 1: Install the <PlatformOrGuideName/> SDK
-
-<PlatformSection notSupported={["javascript.electron"]}>
-
-Install our <PlatformOrGuideName/> SDK using either `yarn` or `npm`, the minimum version that supports profiling is **7.60.0**.
-
-</PlatformSection>
-
-<PlatformSection supported={["javascript.electron"]}>
-
-Install our Electron SDK using either `yarn` or `npm`, the minimum version that supports profiling is **4.16.0**.
-
-</PlatformSection>
-
-<PlatformContent includePath="profiling/automatic-instrumentation-intro" />
-
-## Step 2: Add Document-Policy: js-profiling header
-
-For the JavaScript browser profiler to start, the document response header needs to include a `Document-Policy` header key with the `js-profiling` value.
-
-<PlatformContent includePath="profiling/automatic-instrumentation-headers" />
-
-## Step 3: Configure the JavaScript SDK
-
-Configuration should happen as early as possible in your application's lifecycle. Once this is done, Sentry's JavaScript SDK will capture all unhandled exceptions and transactions.
-
-<PlatformContent includePath="profiling/automatic-instrumentation-setup" />
-
-## The Difference Between DevTools & Sentry's JavaScript Browser Profiler
-
-What does Sentry's JavaScript browser profile offer that Chrome DevTools does not?
-
-- Sentry JavaScript profiler runs in production and captures real user data, showing real-world performance. DevTools runs locally on your machine and only shows profiles of what's running on your machine.
-- Sentry runs at a lower sampling rate of 100Hz with a 10ms sample period versus a sampling rate of 1000Hz and a 1ms sample period for DevTools.
-- Sentry supports deobfuscation, making it so that all the function names in your code are correct. Typically, when you run JavaScript code, it's minified, meaning that all the function names are replaced with machine-generated abbreviations.
-
-Please note, that since the browser profiling API is currently only implemented in Chromium-based browsers, the profiles collected with Sentry's JavaScript browser profiling will inherently be biased toward that demographic. This is something that you'll need to consider if you're basing your decisions on the data collected.
-
-We hope that as the Javascript browser profiling API gains adoption, other browsers will implement it as well. If you find the browser profiling feature helpful and would like to see it gain further adoption, please consider supporting the spec at the official WICG repository.
+<PageGrid />

docs/platforms/javascript/guides/nestjs/profiling/index.mdx → docs/platforms/javascript/common/profiling/node-profiling.mdx

@@ -1,7 +1,22 @@
 ---
-title: Set Up Profiling
+title: Node Profiling
 sidebar_order: 5000
 description: "Learn more about how to configure our Profiling integration and start profiling your code."
+supported:
+  - javascript.nextjs
+  - javascript.sveltekit
+  - javascript.remix
+  - javascript.astro
+  - javascript.node
+  - javascript.aws-lambda
+  - javascript.azure-functions
+  - javascript.connect
+  - javascript.express
+  - javascript.fastify
+  - javascript.gcp-functions
+  - javascript.hapi
+  - javascript.koa
+  - javascript.nestjs
 ---
 
 By default, Sentry error events will not get trace context unless you configure the scope with the transaction, as illustrated in the example below.
@@ -14,43 +29,25 @@ If you're adopting Profiling in a high-throughput environment, we recommend test
 
 ## Installation
 
-<Note>
-
 Node profiling is available starting in `@sentry/profiling-node` version `0.3.0`.
-You have to have the `@sentry/nestjs` package installed.
-
-</Note>
-
-```bash {tabTitle:npm}
-npm install @sentry/nestjs @sentry/profiling-node --save
-```
-
-```bash {tabTitle:yarn}
-yarn add @sentry/nestjs @sentry/profiling-node
-```
-
-```bash {tabTitle:pnpm}
-pnpm add @sentry/nestjs @sentry/profiling-node
-```
+You have to have the <PlatformSdkPackageName fallback="@sentry/node"/> (minimum version `7.44.1`) package installed.
 
 ## Enabling Profiling
 
-To enable profiling, import `@sentry/profiling-node`, add `ProfilingIntegration` to your `integrations`, and set the `profilesSampleRate`.
-
+To enable profiling, add `@sentry/profiling-node` to your imports and set up `nodeProfilingIntegration` in your Sentry config.
 
-```javascript
-const Sentry = require("@sentry/nestjs");
+```javascript {diff}
 const { nodeProfilingIntegration } = require("@sentry/profiling-node");
 
 Sentry.init({
   dsn: "___PUBLIC_DSN___",
   integrations: [
     // Add our Profiling integration
-    nodeProfilingIntegration(),
++   nodeProfilingIntegration(),
   ],
   tracesSampleRate: 1.0,
-  // Set sampling rate for profiling - this is relative to tracesSampleRate
-  profilesSampleRate: 1.0,
++  // Set sampling rate for profiling - this is relative to tracesSampleRate
++  profilesSampleRate: 1.0,
 });
 
 // Profiling happens automatically after setting it up with `Sentry.init()`.