diff --git a/docs/platforms/javascript/common/agent-tracing/index.mdx b/docs/platforms/javascript/common/agent-tracing/index.mdx index c4389c231d7d6..d1fc39dffcac3 100644 --- a/docs/platforms/javascript/common/agent-tracing/index.mdx +++ b/docs/platforms/javascript/common/agent-tracing/index.mdx @@ -118,7 +118,6 @@ Pick your AI stack. Some libraries auto-instrument; others need a short setup "javascript.astro", "javascript.aws-lambda", "javascript.azure-functions", - "javascript.connect", "javascript.express", "javascript.fastify", "javascript.gcp-functions", diff --git a/docs/platforms/javascript/common/configuration/event-loop-block.mdx b/docs/platforms/javascript/common/configuration/event-loop-block.mdx index 0f29e92c06620..c5f7cd0440179 100644 --- a/docs/platforms/javascript/common/configuration/event-loop-block.mdx +++ b/docs/platforms/javascript/common/configuration/event-loop-block.mdx @@ -8,7 +8,6 @@ supported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/configuration/integrations/connect.mdx b/docs/platforms/javascript/common/configuration/integrations/connect.mdx deleted file mode 100644 index 063349091b6ad..0000000000000 --- a/docs/platforms/javascript/common/configuration/integrations/connect.mdx +++ /dev/null @@ -1,32 +0,0 @@ ---- -title: Connect -description: "Adds performance instrumentation for Connect. (default)" -supported: - - javascript.node - - javascript.connect - - javascript.hapi ---- - -For more information on setting up Sentry Connect support, see the [Connect Sentry documentation](/platforms/javascript/guides/connect/). - - - -This integration only works in the Node.js and Bun runtimes. - - - -_Import name: `Sentry.connectIntegration`_ - -This integration is enabled by default when performance monitoring is enabled. If you'd like to modify your default integrations, read [this](./../#modifying-default-integrations). - -The `connectIntegration` adds instrumentation for the Hapi framework to capture spans using [`@opentelemetry/instrumentation-connect`](https://www.npmjs.com/package/@opentelemetry/instrumentation-connect). - -```JavaScript -Sentry.init({ - integrations: [Sentry.connectIntegration()], -}); -``` - -## Supported Versions - -- `connect`: `^3.0.0` diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx index 0cc649fc82b9f..27ba43ac2a2e9 100644 --- a/docs/platforms/javascript/common/configuration/options.mdx +++ b/docs/platforms/javascript/common/configuration/options.mdx @@ -135,6 +135,7 @@ Sentry.init({ ``` Data you set explicitly (for example, via `Sentry.setUser()`) is always sent, regardless of `dataCollection`. + @@ -142,23 +143,23 @@ Data you set explicitly (for example, via `Sen Controls which categories of data the SDK collects automatically. All fields are optional. - By default the SDK collects rich debugging context (including user identity, request/response bodies, and generative AI content) and scrubs values whose keys match the built-in sensitive denylist (`auth`, `token`, `password`, and similar). +By default the SDK collects rich debugging context (including user identity, request/response bodies, and generative AI content) and scrubs values whose keys match the built-in sensitive denylist (`auth`, `token`, `password`, and similar). For more on what data Sentry collects and how to control it, see Data Management. -| Key | Type | Default | Description | -| --------------------- | ---------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------- | -| `userInfo` | `boolean` | `true` | Populate `user.*` fields (`id`, `email`, `username`, `ip_address`) from instrumentation. For example, the SDK infers the IP address from an incoming HTTP request. Data you set with `Sentry.setUser()` is always sent. | -| `cookies` | `CollectBehavior` | `true` | Collect cookies. Cookie names are always included. The SDK replaces the values of sensitive cookies with `[Filtered]`. | -| `httpHeaders` | `CollectBehavior \| { request?, response? }` | both `true` | Collect HTTP request and response headers. Pass one `CollectBehavior` for both directions, or use `{ request, response }` to control each direction. Header names are always included. | -| `httpBodies` | `HttpBodyCollectionTarget[]` | all types | Body types to collect: `"incomingRequest"`, `"outgoingRequest"`, `"incomingResponse"`, `"outgoingResponse"`. Set to `[]` to disable. | -| `urlQueryParams` | `CollectBehavior` | `true` | Collect URL query parameters. Parameter names are always included. The SDK replaces the values of sensitive parameters with `[Filtered]`. | -| `graphQL` | `{ document?, variables? }` | both `true` | `document`: Collect the GraphQL document (the query or mutation source text).

`variables`: Collect the variables that are passed to GraphQL operations.

The operation name and type are always collected. | -| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values. | -| `databaseQueryData` | `boolean` | `true` | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data.

The sanitized or parameterized query text (`db.query.text`) is **not** controlled by this option. Structural metadata, such as the database system, query summary, operation name, and table, is also **always** collected. | -| `queues` | `boolean` | `true` | Collect the arguments passed to tasks within queues. For Kafka, this is the message key. Structural metadata, such as the messaging system, the destination name, and the operation, is always collected. | -| `stackFrameVariables` | `boolean` | `true` | Capture local variable values in stack frames. | -| `frameContextLines` | `number` | `5` | Number of source code lines captured above and below each stack frame. | +| Key | Type | Default | Description | +| --------------------- | -------------------------------------------- | ----------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `userInfo` | `boolean` | `true` | Populate `user.*` fields (`id`, `email`, `username`, `ip_address`) from instrumentation. For example, the SDK infers the IP address from an incoming HTTP request. Data you set with `Sentry.setUser()` is always sent. | +| `cookies` | `CollectBehavior` | `true` | Collect cookies. Cookie names are always included. The SDK replaces the values of sensitive cookies with `[Filtered]`. | +| `httpHeaders` | `CollectBehavior \| { request?, response? }` | both `true` | Collect HTTP request and response headers. Pass one `CollectBehavior` for both directions, or use `{ request, response }` to control each direction. Header names are always included. | +| `httpBodies` | `HttpBodyCollectionTarget[]` | all types | Body types to collect: `"incomingRequest"`, `"outgoingRequest"`, `"incomingResponse"`, `"outgoingResponse"`. Set to `[]` to disable. | +| `urlQueryParams` | `CollectBehavior` | `true` | Collect URL query parameters. Parameter names are always included. The SDK replaces the values of sensitive parameters with `[Filtered]`. | +| `graphQL` | `{ document?, variables? }` | both `true` | `document`: Collect the GraphQL document (the query or mutation source text).

`variables`: Collect the variables that are passed to GraphQL operations.

The operation name and type are always collected. | +| `genAI` | `{ inputs?, outputs? }` | both `true` | `inputs`: Collect the content of generative AI inputs: system instructions, prompt messages, tool definitions, and tool call arguments.

`outputs`: Collect the content of generative AI outputs, such as completion text and tool call results.

Metadata, such as the model name and token counts, is always collected. Options set on an AI integration take precedence over these values. | +| `databaseQueryData` | `boolean` | `true` | Collect the data associated with database queries: bound query parameters, data payloads for write operations, and returned result data.

The sanitized or parameterized query text (`db.query.text`) is **not** controlled by this option. Structural metadata, such as the database system, query summary, operation name, and table, is also **always** collected. | +| `queues` | `boolean` | `true` | Collect the arguments passed to tasks within queues. For Kafka, this is the message key. Structural metadata, such as the messaging system, the destination name, and the operation, is always collected. | +| `stackFrameVariables` | `boolean` | `true` | Capture local variable values in stack frames. | +| `frameContextLines` | `number` | `5` | Number of source code lines captured above and below each stack frame. | The `cookies`, `httpHeaders`, and `urlQueryParams` categories accept a `CollectBehavior` value: @@ -599,7 +600,7 @@ If you want to disable trace propagation, you can set this option to `[]`. Controls which bindings on `env` receive tracing data over [RPC calls](https://developers.cloudflare.com/workers/runtime-apis/bindings/service-bindings/rpc/) to Durable Objects and other Workers. RPC has no headers, so the SDK appends the trace context as a trailing argument that an instrumented receiver strips again before your method runs. -String entries must match a binding name exactly, so `"DB"` matches `"DB"` but not `"MY_DB"`. Use a regular expression for pattern matching. +String entries must match a binding name exactly, so `"DB"` matches `"DB"` but not `"MY_DB"`. Use a regular expression for pattern matching. Setting this option, with any value, also lets the Worker continue a trace that arrives on an incoming RPC call. So a Worker that both calls and receives needs only this one option. Setting an empty array, the Worker is a receiver that propagates nothing, and an entry for a binding the Worker never calls is ignored. Because unused entries are harmless, one list can serve every Worker and Durable Object in a deployment. @@ -747,7 +748,7 @@ If set to `true`, the SDK adds the [W3C `traceparent` header](https://www.w3.org This header is attached in addition to the `sentry-trace` and `baggage` headers. Set this option to `true` if your backend services are instrumented with e.g. OpenTelemetry or other W3C Trace Context compatible libraries and you want to continue traces from the client. - + **Important:** Make sure that your backend services' CORS configuration allows the `traceparent` header. Otherwise, requests might be blocked. @@ -801,7 +802,8 @@ Instead, - **Note:** For Electron, metric options apply to the process where these options - are set. + **Note:** For Electron, metric options apply to the process where these + options are set. diff --git a/docs/platforms/javascript/common/configuration/transports.mdx b/docs/platforms/javascript/common/configuration/transports.mdx index 1a3ba82cc54a4..be8c17b03ceb6 100644 --- a/docs/platforms/javascript/common/configuration/transports.mdx +++ b/docs/platforms/javascript/common/configuration/transports.mdx @@ -12,7 +12,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/configuration/tree-shaking.mdx b/docs/platforms/javascript/common/configuration/tree-shaking.mdx index e3d50897086c4..80e20ba324f2d 100644 --- a/docs/platforms/javascript/common/configuration/tree-shaking.mdx +++ b/docs/platforms/javascript/common/configuration/tree-shaking.mdx @@ -269,7 +269,6 @@ This means that the `ClientOptions.integrations` property is the final array of + ## Requirements @@ -20,7 +20,7 @@ Once implemented, it'll allow you to get alerts and metrics to help you solve er - + ## Requirements diff --git a/docs/platforms/javascript/common/data-management/data-collected/index.mdx b/docs/platforms/javascript/common/data-management/data-collected/index.mdx index 8945a902a7a2f..a8e539c88932d 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -8,8 +8,6 @@ Sentry takes data privacy very seriously and has default settings in place that The category types and amount of data collected vary, depending on the integrations you've enabled in the Sentry SDK. This page lists data categories that the Sentry JavaScript SDK collects. - - You can control many of the categories listed here with the `dataCollection` option, which lets you opt in or out of each data category individually. The `sendDefaultPii` option is still supported, but deprecated as of version `10.54.0`. @@ -41,7 +39,8 @@ Without `dataCollection` (and with `sendDefaultPii` unset or `false`), user iden ### Local Device User - By default, the Sentry SDK doesn't send any information about the user currently logged-in to the device where the app is running. However, you should exercise caution when logging file system errors as paths may contain the current username. +By default, the Sentry SDK doesn't send any information about the user currently logged-in to the device where the app is running. However, you should exercise caution when logging file system errors as paths may contain the current username. + ## Users' IP Address and Location @@ -93,12 +92,44 @@ Sentry.init({ Without `dataCollection` (and with `sendDefaultPii` unset or `false`), Sentry only sends the body size inferred from the `content-length` header, not the body content itself. - - On the server-side, the incoming request body is captured by default. You can disable sending the incoming request body by configuring `ignoreIncomingRequestBody` in the HTTP Integration. + + On the server-side, the incoming request body is captured by default. You can + disable sending the incoming request body by configuring + `ignoreIncomingRequestBody` in the{" "} + + HTTP Integration + + . - When `dataCollection` is used, HTTP body collection is enabled by default, so Form Data can be sent with `captureActionFormDataKeys` in the Remix server-side configuration. When not using `dataCollection`, this requires the deprecated `sendDefaultPii: true`. + When `dataCollection` is used, HTTP body collection is enabled by default, so + Form Data can be sent with `captureActionFormDataKeys` in the Remix{" "} + + server-side configuration + + . When not using `dataCollection`, this requires the deprecated + `sendDefaultPii: true`. @@ -125,8 +156,34 @@ To disable source map upload, see the Source Maps The Sentry SDK does not send local variables in the error stack trace in client-side JavaScript SDKs. - - You can enable sending local variables by setting `includeLocalVariables: true` in the `Sentry.init()` call. This activates the Local Variables Integration. The integration is added by default in Node.js-based runtimes. + + You can enable sending local variables by setting `includeLocalVariables: + true` in the `Sentry.init()` call. This activates the{" "} + + Local Variables Integration + + . The integration is added by default in Node.js-based runtimes. ## Device, Browser, OS and Runtime Information @@ -136,20 +193,20 @@ By default, the Sentry SDK sends information about the device and runtime to Sen In browser environments, this information is obtained by the User Agent string. The User Agent string contains information about the browser, operating system, and device type. - In server-side environments, the Sentry SDK uses the `os` module to get information about the operating system and architecture. +In server-side environments, the Sentry SDK uses the `os` module to get information about the operating system and architecture. + The Sentry Electron SDK collects information about the device, such as the platform, architecture, available memory and version and build of your operating system or Linux distribution. - By default, the Additional Context Integration collects dimensions and resolution of the device screen. It can optionally collect the device's manufacturer and model name if the `deviceModelManufacturer` option is enabled. - - By default, the GPU Context Integration collects GPU information. It can optionally collect more detailed information if the `infoLevel` option is set to `complete`. +By default, the Additional Context Integration collects dimensions and resolution of the device screen. It can optionally collect the device's manufacturer and model name if the `deviceModelManufacturer` option is enabled. +By default, the GPU Context Integration collects GPU information. It can optionally collect more detailed information if the `infoLevel` option is set to `complete`. - + ## Session Replay @@ -160,18 +217,20 @@ By default, the Sentry SDK sends information about the device and runtime to Sen Session Replay also captures basic information about all outgoing fetch and XHR requests in your application. This includes the URL, request and response body size, method, and status code. If `networkDetailAllowUrls` are defined, the request and response body will be sent to Sentry as well. This can include PII data if the request or response body contains PII information. Console messages are also captured by default in Session Replay. To scrub console messages, you can use the `beforeAddRecordingEvent` option to filter console messages before they are sent to Sentry. + - ## Console Logs +## Console Logs - By default, the Sentry SDK sends JS console logs to Sentry as breadcrumbs which may contain PII data. +By default, the Sentry SDK sends JS console logs to Sentry as breadcrumbs which may contain PII data. - To disable sending console messages, set `console: false` in your `Sentry.breadcrumbsIntegration` config, see the Breadcrumbs documentation. +To disable sending console messages, set `console: false` in your `Sentry.breadcrumbsIntegration` config, see the Breadcrumbs documentation. ## Referrer URL By default, the Sentry SDK sends the referrer URL to Sentry. This is the URL of the page that linked to the current page. + @@ -180,6 +239,7 @@ By default, the Sentry SDK sends information about the device and runtime to Sen ## Stack Trace Context Lines By default, the Context Lines Integration is enabled. This integration sends the surrounding lines of code for each frame in the stack trace. This can include PII data if the code contains PII information. + @@ -225,9 +285,10 @@ By default, the Sentry SDK sends information about the device and runtime to Sen ## tRPC Context - When using `dataCollection`, tRPC input is collected by default because `httpBodies` includes `"incomingRequest"` by default. To disable it, set `dataCollection: { httpBodies: [] }` or use a list that excludes `"incomingRequest"`. +When using `dataCollection`, tRPC input is collected by default because `httpBodies` includes `"incomingRequest"` by default. To disable it, set `dataCollection: { httpBodies: [] }` or use a list that excludes `"incomingRequest"`. + +Without `dataCollection` (and with `sendDefaultPii` unset or `false`), tRPC input is not collected. You can still opt in per-middleware by setting `attachRpcInput: true` in the `Sentry.trpcMiddleware()` options, regardless of the global `dataCollection` setting. - Without `dataCollection` (and with `sendDefaultPii` unset or `false`), tRPC input is not collected. You can still opt in per-middleware by setting `attachRpcInput: true` in the `Sentry.trpcMiddleware()` options, regardless of the global `dataCollection` setting. @@ -253,34 +314,36 @@ Sentry.init({ ## LLM Inputs And Responses - When using AI integrations, metadata like model ID and used tokens is sent to Sentry. +When using AI integrations, metadata like model ID and used tokens is sent to Sentry. - The content of generative AI inputs (system instructions, prompt messages, tool definitions, and tool call arguments) and outputs (such as completion text and tool call results) might carry personal data. Whether it's recorded depends on your configuration: it's not recorded by default with `sendDefaultPii`, but when you use `dataCollection`, the `genAI` category records both inputs and outputs unless you opt out. Metadata like model ID and token counts is always collected. +The content of generative AI inputs (system instructions, prompt messages, tool definitions, and tool call arguments) and outputs (such as completion text and tool call results) might carry personal data. Whether it's recorded depends on your configuration: it's not recorded by default with `sendDefaultPii`, but when you use `dataCollection`, the `genAI` category records both inputs and outputs unless you opt out. Metadata like model ID and token counts is always collected. - Use the `dataCollection.genAI` option to control this. For example, opt out of recording AI message content while keeping the metadata: +Use the `dataCollection.genAI` option to control this. For example, opt out of recording AI message content while keeping the metadata: - ```JavaScript - Sentry.init({ - dsn: "___PUBLIC_DSN___", - dataCollection: { - genAI: { - inputs: false, - outputs: false, - }, +```JavaScript +Sentry.init({ + dsn: "___PUBLIC_DSN___", + dataCollection: { + genAI: { + inputs: false, + outputs: false, }, - }); - ``` + }, +}); +``` + - ## Window Titles +## Window Titles + +The Electron Breadcrumbs Integration can optionally capture the window titles for breadcrumbs related to windows events. These can potentially contain PII so are disabled by default but can be enabled via the `captureWindowTitles` option. - The Electron Breadcrumbs Integration can optionally capture the window titles for breadcrumbs related to windows events. These can potentially contain PII so are disabled by default but can be enabled via the `captureWindowTitles` option. +## Native Crashes - ## Native Crashes +At the time of a native crash, the stack of each thread is collected and sent to Sentry as part of the Minidump snapshot. This information is sent to Sentry by default, but dropped after processing the event in the backend. - At the time of a native crash, the stack of each thread is collected and sent to Sentry as part of the Minidump snapshot. This information is sent to Sentry by default, but dropped after processing the event in the backend. +These files are not stored by default, but you can [enable Minidump Storage](/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings. - These files are not stored by default, but you can [enable Minidump Storage](/platforms/native/guides/minidumps/enriching-events/attachments/#store-minidumps-as-attachments) in the Sentry organization or project settings. diff --git a/docs/platforms/javascript/common/enriching-events/request-isolation/index.mdx b/docs/platforms/javascript/common/enriching-events/request-isolation/index.mdx index f03d771f8d06f..b0502148775f2 100644 --- a/docs/platforms/javascript/common/enriching-events/request-isolation/index.mdx +++ b/docs/platforms/javascript/common/enriching-events/request-isolation/index.mdx @@ -6,7 +6,6 @@ supported: - javascript.node - javascript.eve - javascript.mastra - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi diff --git a/docs/platforms/javascript/common/install/commonjs.mdx b/docs/platforms/javascript/common/install/commonjs.mdx index 978d93e2ea363..a5901ff9b8415 100644 --- a/docs/platforms/javascript/common/install/commonjs.mdx +++ b/docs/platforms/javascript/common/install/commonjs.mdx @@ -4,7 +4,6 @@ sidebar_order: 9 description: "Learn about running Sentry in an CJS application." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi diff --git a/docs/platforms/javascript/common/install/esm-without-import.mdx b/docs/platforms/javascript/common/install/esm-without-import.mdx index a1a742bb750f5..68434dc2eb452 100644 --- a/docs/platforms/javascript/common/install/esm-without-import.mdx +++ b/docs/platforms/javascript/common/install/esm-without-import.mdx @@ -4,7 +4,6 @@ sidebar_order: 11 description: "Learn about running Sentry in an ESM application, without the --import flag." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi @@ -17,12 +16,10 @@ supported: [installation methods](../). - When running your application in ESM mode, you will most likely want to follow the ESM instructions. However, if you can't use the `--import` command line option, you can either use [direct imports](#direct-imports) or [SEA bootstrap setup](#nodejs-single-executable-applications) if you are using a Node.js Single Executable Application (SEA). ## Direct Imports - This installation method has the fundamental restriction that only native Node.js APIs can be instrumented (such as `fetch` and the `http` module). diff --git a/docs/platforms/javascript/common/install/esm.mdx b/docs/platforms/javascript/common/install/esm.mdx index d222a843810b8..cd8eb95a2f033 100644 --- a/docs/platforms/javascript/common/install/esm.mdx +++ b/docs/platforms/javascript/common/install/esm.mdx @@ -4,7 +4,6 @@ sidebar_order: 10 description: "Learn about running Sentry in an ESM application." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi diff --git a/docs/platforms/javascript/common/install/esm__v8.x.mdx b/docs/platforms/javascript/common/install/esm__v8.x.mdx index fb850ab562d98..3796d110427da 100644 --- a/docs/platforms/javascript/common/install/esm__v8.x.mdx +++ b/docs/platforms/javascript/common/install/esm__v8.x.mdx @@ -4,7 +4,6 @@ sidebar_order: 10 description: "Learn about running Sentry in an ESM application." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi diff --git a/docs/platforms/javascript/common/install/late-initialization.mdx b/docs/platforms/javascript/common/install/late-initialization.mdx index 1362f0af7741a..9db8256f76676 100644 --- a/docs/platforms/javascript/common/install/late-initialization.mdx +++ b/docs/platforms/javascript/common/install/late-initialization.mdx @@ -4,7 +4,6 @@ sidebar_order: 12 description: "Learn about running Sentry in an ESM or CJS application, in scenarios where you cannot run init early." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi diff --git a/docs/platforms/javascript/common/install/lightweight.mdx b/docs/platforms/javascript/common/install/lightweight.mdx index dd87680c2cc5b..64798937c3d53 100644 --- a/docs/platforms/javascript/common/install/lightweight.mdx +++ b/docs/platforms/javascript/common/install/lightweight.mdx @@ -4,7 +4,6 @@ sidebar_order: 15 description: "Learn about running Sentry in lightweight mode without OpenTelemetry, or with optional OTLP integration for existing OTel setups." supported: - javascript.node - - javascript.connect - javascript.express - javascript.fastify - javascript.hapi @@ -141,13 +140,13 @@ setConversationId("conv_abc123"); ## When to Use Lightweight Mode vs `@sentry/node` | | `@sentry/node` | `@sentry/node-core/light` | -| ------------------------------- | ------------------- | ---------------------------------------------- | -| **Error tracking** | Yes | Yes | -| **Logs and metrics** | Yes | Yes | -| **Automatic spans** | Yes | No | -| **OpenTelemetry auto-included** | Yes | No | -| **Dependency footprint** | Larger | Minimal | -| **Best for** | Full observability | No auto-instrumentation, manual tracing setup | +| ------------------------------- | ------------------ | --------------------------------------------- | +| **Error tracking** | Yes | Yes | +| **Logs and metrics** | Yes | Yes | +| **Automatic spans** | Yes | No | +| **OpenTelemetry auto-included** | Yes | No | +| **Dependency footprint** | Larger | Minimal | +| **Best for** | Full observability | No auto-instrumentation, manual tracing setup | If you need automatic spans for HTTP requests, database queries, and other operations, use `@sentry/node` (the default). If you don't need automatically created spans and want minimal dependencies, use lightweight mode. @@ -205,7 +204,7 @@ otlpIntegration({ ### Options -| Option | Type | Default | Description | -|---|---|---|---| -| `setupOtlpTracesExporter` | `boolean` | `true` | Automatically configure an exporter to send OTLP traces to the right project from the DSN or `collectorUrl`. Set to `false` to set up the `TracerProvider` manually. | -| `collectorUrl` | `string` | `undefined` | URL of your own OpenTelemetry collector. When set, traces are sent here instead of the Sentry OTLP endpoint derived from the DSN. | +| Option | Type | Default | Description | +| ------------------------- | --------- | ----------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| `setupOtlpTracesExporter` | `boolean` | `true` | Automatically configure an exporter to send OTLP traces to the right project from the DSN or `collectorUrl`. Set to `false` to set up the `TracerProvider` manually. | +| `collectorUrl` | `string` | `undefined` | URL of your own OpenTelemetry collector. When set, traces are sent here instead of the Sentry OTLP endpoint derived from the DSN. | diff --git a/docs/platforms/javascript/common/install/loader.mdx b/docs/platforms/javascript/common/install/loader.mdx index d3e03fa9c8abc..e861b37633db4 100644 --- a/docs/platforms/javascript/common/install/loader.mdx +++ b/docs/platforms/javascript/common/install/loader.mdx @@ -27,7 +27,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.elysia - javascript.express - javascript.fastify @@ -186,7 +185,10 @@ If you want to call any other method when using the Loader, you have to guard it }; - + +```html + - + + Sentry.onLoad(function () { + fetch("/api/users"); + }); + + ``` + ``` + - Use the [CDN bundles](#cdn) instead of the Loader Script. This will ensure that the SDK is loaded synchronously, and that all your `fetch` calls are traced. diff --git a/docs/platforms/javascript/common/install/npm.mdx b/docs/platforms/javascript/common/install/npm.mdx index 02d5422d9c7f7..6005ae6afc6be 100644 --- a/docs/platforms/javascript/common/install/npm.mdx +++ b/docs/platforms/javascript/common/install/npm.mdx @@ -28,7 +28,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.elysia - javascript.express - javascript.fastify diff --git a/docs/platforms/javascript/common/logs/index.mdx b/docs/platforms/javascript/common/logs/index.mdx index f6ceea5a991c6..375f2c5b8bdbc 100644 --- a/docs/platforms/javascript/common/logs/index.mdx +++ b/docs/platforms/javascript/common/logs/index.mdx @@ -10,7 +10,7 @@ notSupported: -Stack traces tell you *what* broke. Logs tell you *why*. When an error fires, you get a snapshot of the failure, but the context leading up to it is often missing. Logs capture the journey — what the data looked like, which code paths executed, and what state the system was in. +Stack traces tell you _what_ broke. Logs tell you _why_. When an error fires, you get a snapshot of the failure, but the context leading up to it is often missing. Logs capture the journey — what the data looked like, which code paths executed, and what state the system was in. Sentry Logs are **high-cardinality** — you can pass any attributes you want and search or filter by them later. No need to decide upfront which fields are important. Just log what might be useful and query it when you need it. @@ -209,7 +209,32 @@ Sentry.init({ Everything in Sentry is linked by trace. When you're viewing a log, you can jump to the parent trace to see the full request context. When you're viewing a trace, you can see all logs emitted during that operation. This connection makes it easy to move between high-level performance data and detailed diagnostic logs. - **[Traces](/product/trace-explorer/)** — Logs emitted during an active span automatically include `sentry.trace.parent_span_id`. Click through from any log to see the full trace, or filter logs by trace ID to see everything that happened during a specific request. -- **[Session Replay](/product/session-replay/)** — Logs include `sentry.replay_id` when a replay is active. Jump from a log entry directly to the replay to see what the user was doing when the log was emitted. +- + **[Session Replay](/product/session-replay/)** — Logs include + `sentry.replay_id` when a replay is active. Jump from a log entry directly + to the replay to see what the user was doing when the log was emitted. + - **[Errors](/product/issues/)** — Logs capture the journey leading up to a failure. When an error occurs, your logs show what data was processed, which code paths executed, and what state the system was in — context that stack traces alone can't provide. ## Best Practices @@ -224,10 +249,38 @@ Everything in Sentry is linked by trace. When you're viewing a log, you can jump Any attributes set via `Sentry.setAttribute()` / `Sentry.setAttributes()` (or directly on a scope) are automatically included on all logs. `Sentry.setAttribute(s)` requires SDK version `10.61.0` or above. See [Attributes](#shared-attributes) above for details. - ## Related Features -- Tracing — Logs are automatically linked to traces, so you can see logs in the context of the request or operation that produced them. -- Session Replay — Logs are automatically linked to replays, letting you jump from a log entry to see what the user was doing. -- Error Monitoring — Use logs to add diagnostic context that helps you understand what led to an error. -- Attributes — Set attributes once and have them automatically included on all your logs. +- Tracing — Logs are automatically + linked to traces, so you can see logs in the context of the request or + operation that produced them. +- + Session Replay — Logs are + automatically linked to replays, letting you jump from a log entry to see + what the user was doing. + +- Error Monitoring — Use logs to add + diagnostic context that helps you understand what led to an error. +- Attributes — + Set attributes once and have them automatically included on all your logs. diff --git a/docs/platforms/javascript/common/metrics/index.mdx b/docs/platforms/javascript/common/metrics/index.mdx index 1e3ad433ef4e9..4d9c1501bf851 100644 --- a/docs/platforms/javascript/common/metrics/index.mdx +++ b/docs/platforms/javascript/common/metrics/index.mdx @@ -34,7 +34,7 @@ With [Sentry's Application Metrics](/product/metrics/), you can send counters, g ## Integrations - + - `elementTimingIntegration` diff --git a/docs/platforms/javascript/common/migration/v7-to-v8/v8-opentelemetry.mdx b/docs/platforms/javascript/common/migration/v7-to-v8/v8-opentelemetry.mdx index f2c096e76c4f3..2f5fad72272a7 100644 --- a/docs/platforms/javascript/common/migration/v7-to-v8/v8-opentelemetry.mdx +++ b/docs/platforms/javascript/common/migration/v7-to-v8/v8-opentelemetry.mdx @@ -9,7 +9,6 @@ supported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx index 75417420afe61..d8211b627db44 100644 --- a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx +++ b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx @@ -9,7 +9,6 @@ supported: - javascript.aws-lambda - javascript.azure-functions - javascript.bun - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions @@ -40,7 +39,7 @@ If you are looking to simply add individual OpenTelemetry instrumentation to you - + If you don't need the full `@sentry/node` SDK and want a simpler way to bridge your existing OpenTelemetry setup with Sentry, consider using lightweight mode with the OTLP integration instead. It requires significantly less manual wiring. diff --git a/docs/platforms/javascript/common/opentelemetry/index.mdx b/docs/platforms/javascript/common/opentelemetry/index.mdx index fbde8fe769b4c..64e58e9ef5c37 100644 --- a/docs/platforms/javascript/common/opentelemetry/index.mdx +++ b/docs/platforms/javascript/common/opentelemetry/index.mdx @@ -11,7 +11,6 @@ supported: - javascript.aws-lambda - javascript.azure-functions - javascript.bun - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx index 40bc8d5179743..bc616ef2875df 100644 --- a/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx +++ b/docs/platforms/javascript/common/opentelemetry/using-opentelemetry-apis.mdx @@ -9,7 +9,6 @@ supported: - javascript.aws-lambda - javascript.azure-functions - javascript.bun - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions @@ -38,9 +37,7 @@ While the Sentry SDK includes some OpenTelemetry instrumentation out of the box, ```javascript {tabTitle: ESM} {12-13} import * as Sentry from "@sentry/node"; -import { - GenericPoolInstrumentation, -} from "@opentelemetry/instrumentation-generic-pool"; +import { GenericPoolInstrumentation } from "@opentelemetry/instrumentation-generic-pool"; Sentry.init({ dsn: "___DSN___", @@ -52,6 +49,7 @@ Sentry.init({ openTelemetryInstrumentations: [new GenericPoolInstrumentation()], }); ``` + ```javascript {tabTitle: CJS} {12-13} const Sentry = require("@sentry/node"); const { @@ -94,6 +92,7 @@ tracer.startActiveSpan("span name", () => { // measure something }); ``` + ```javascript {tabTitle: CJS} const Sentry = require("@sentry/node"); @@ -115,6 +114,7 @@ import * as Sentry from "@sentry/node"; const provider = Sentry.getClient()?.traceProvider; ``` + ```javascript {tabTitle: CJS} const Sentry = require("@sentry/node"); @@ -138,6 +138,7 @@ Sentry.init({ openTelemetrySpanProcessors: [new MySpanProcessor()], }); ``` + ```javascript {tabTitle: CJS} const Sentry = require("@sentry/node"); diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx index 47620afa80fdd..3a601b12587de 100644 --- a/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx +++ b/docs/platforms/javascript/common/sourcemaps/uploading/hosting-publicly.mdx @@ -8,7 +8,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/tracing/distributed-tracing/dealing-with-cors-issues/index.mdx b/docs/platforms/javascript/common/tracing/distributed-tracing/dealing-with-cors-issues/index.mdx index 9a0469fb29ebb..457dd73b7f609 100644 --- a/docs/platforms/javascript/common/tracing/distributed-tracing/dealing-with-cors-issues/index.mdx +++ b/docs/platforms/javascript/common/tracing/distributed-tracing/dealing-with-cors-issues/index.mdx @@ -8,7 +8,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions @@ -26,6 +25,7 @@ If your frontend and backend are hosted on different domains (for example, your Sentry doesn't attach the `sentry-trace` and `baggage` (and optionally `traceparent`) headers to every outgoing request. Instead, it only attaches these headers to requests whose URLs match the patterns specified in the `tracePropagationTargets` configuration option. By default, `tracePropagationTargets` is set to `['localhost', /^\//]`, which means trace headers are only attached to: + - Requests containing `localhost` in their URL (e.g., `http://localhost:3000/api`) - Requests whose URL starts with `/` (e.g., `/api/users`, `/graphql`) @@ -40,10 +40,10 @@ Sentry.init({ dsn: "___PUBLIC_DSN___", integrations: [Sentry.browserTracingIntegration()], tracePropagationTargets: [ - "localhost", // For local development - /^\/api\//, // For same-origin API calls + "localhost", // For local development + /^\/api\//, // For same-origin API calls "https://api.example.com", // For your backend domain - "https://auth.example.com" // For additional services + "https://auth.example.com", // For additional services ], }); ``` diff --git a/docs/platforms/javascript/common/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx index 91064cd58bc00..0f2ee7a74e463 100644 --- a/docs/platforms/javascript/common/tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/index.mdx @@ -61,7 +61,8 @@ Sentry captures distributed traces consisting of transactions and spans, which m If you're building with agents or LLMs, you can extend your tracing setup to capture agent workflows, model calls, tool executions, and token usage. With tracing already enabled, the SDK can automatically instrument supported AI libraries on the server and connect agent activity to the rest of your application traces. -Set up Agent Tracing to get started. +Set up Agent Tracing to get +started. @@ -95,7 +96,7 @@ You can also manually start spans to instrument specific parts of your code. Thi - Sending Span Metrics: Learn how to capture metrics on your spans - + ## Replay Linking @@ -103,7 +104,7 @@ When [Session Replay](/product/session-replay/) is enabled, traces appear in the From any trace, click the replay link to jump directly to the replay and see the user's experience during that operation. From a replay, click any trace span in the timeline to drill into performance details. -This bidirectional linking helps you understand not just *how long* something took, but *what impact* it had on the user's experience. +This bidirectional linking helps you understand not just _how long_ something took, but _what impact_ it had on the user's experience. @@ -123,9 +124,11 @@ Instead, neither `tracesSampleRate` nor `tracesSampler` should be defined in you "javascript.solidstart", ]} > - In addition, you can set `__SENTRY_TRACING__` to `false` to ensure the tracing code - is removed from your production build. This will result in{" "} - trace propagation{" "} + In addition, you can set `__SENTRY_TRACING__` to `false` to ensure the tracing + code is removed from your production build. This will result in{" "} + + trace propagation + {" "} being disabled as well. See{" "} Tree Shaking{" "} for more information. @@ -133,8 +136,37 @@ Instead, neither `tracesSampleRate` nor `tracesSampler` should be defined in you ## Related Features -- Session Replay — Traces appear in the Replay timeline, showing performance data alongside the user's actions. -- Logs — Logs emitted during a trace are automatically linked, giving you diagnostic context for each operation. +- + Session Replay — Traces + appear in the Replay timeline, showing performance data alongside the user's + actions. + +- + Logs — Logs emitted during a trace + are automatically linked, giving you diagnostic context for each operation. + ## Tracing Next Steps diff --git a/docs/platforms/javascript/common/troubleshooting/supported-browsers.mdx b/docs/platforms/javascript/common/troubleshooting/supported-browsers.mdx index 32a83dd416604..19a9073529db9 100644 --- a/docs/platforms/javascript/common/troubleshooting/supported-browsers.mdx +++ b/docs/platforms/javascript/common/troubleshooting/supported-browsers.mdx @@ -9,7 +9,6 @@ notSupported: - javascript.mastra - javascript.aws-lambda - javascript.azure-functions - - javascript.connect - javascript.express - javascript.fastify - javascript.gcp-functions diff --git a/docs/platforms/javascript/common/user-feedback/configuration/index.mdx b/docs/platforms/javascript/common/user-feedback/configuration/index.mdx index 26359e0ac6796..db05f9651aa25 100644 --- a/docs/platforms/javascript/common/user-feedback/configuration/index.mdx +++ b/docs/platforms/javascript/common/user-feedback/configuration/index.mdx @@ -8,7 +8,7 @@ notSupported: - javascript.mastra --- - + ## User Feedback Widget @@ -116,7 +116,7 @@ Sentry.init({ buttonLabel: "Feedback", submitButtonLabel: "Send Feedback", formTitle: "Send Feedback", - }) + }), ], }); ``` @@ -255,7 +255,7 @@ Sentry.init({ You can link directly to a saved feedback item by implementing the `onSubmitSuccess` callback. The URL you need to construct is `https://${orgSlug}.sentry.io/issues/feedback/?projectSlug=${projectSlug}&eventId=${eventId}`. -*Note:* In v9 and below of the SDK, the signature of `onSubmitSuccess` was `(data: FeedbackFormData) => {}`. +_Note:_ In v9 and below of the SDK, the signature of `onSubmitSuccess` was `(data: FeedbackFormData) => {}`. ### Bring Your Own Button @@ -268,7 +268,7 @@ Sentry.init({ Sentry.feedbackIntegration({ // Disable the injection of the default widget autoInject: false, - }) + }), ], }); @@ -324,7 +324,7 @@ Sentry.init({ Sentry.feedbackIntegration({ // Disable the injection of the default widget autoInject: false, - }) + }), ], }); diff --git a/docs/platforms/javascript/common/user-feedback/configuration/index__v7.x.mdx b/docs/platforms/javascript/common/user-feedback/configuration/index__v7.x.mdx index e696f17382cbe..ae0e9b20b2638 100644 --- a/docs/platforms/javascript/common/user-feedback/configuration/index__v7.x.mdx +++ b/docs/platforms/javascript/common/user-feedback/configuration/index__v7.x.mdx @@ -17,7 +17,7 @@ In version 7 of our JavaScript SDK, User Feedback was released as a Beta integra - + ## User Feedback Widget @@ -37,13 +37,13 @@ The following options can be configured for the integration in `feedbackIntegrat ### User and Form -| Key | Type | Default | Description | -| ------------------ | ------------------------ | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | -| `showName` | `boolean` | `true` | Displays the name field on the feedback form. | -| `showEmail` | `boolean` | `true` | Displays the email field on the feedback form. | -| `isNameRequired` | `boolean` | `false` | Requires the name field on the feedback form to be filled in. | -| `isEmailRequired` | `boolean` | `false` | Requires the email field on the feedback form to be filled in. | -| `useSentryUser` | `Record` | `{ email: 'email', name: 'username'}` | Sets the `email` and `name` fields to the corresponding Sentry SDK user fields that were called with `Sentry.setUser`. | +| Key | Type | Default | Description | +| ----------------- | ------------------------ | ------------------------------------- | ---------------------------------------------------------------------------------------------------------------------- | +| `showName` | `boolean` | `true` | Displays the name field on the feedback form. | +| `showEmail` | `boolean` | `true` | Displays the email field on the feedback form. | +| `isNameRequired` | `boolean` | `false` | Requires the name field on the feedback form to be filled in. | +| `isEmailRequired` | `boolean` | `false` | Requires the email field on the feedback form to be filled in. | +| `useSentryUser` | `Record` | `{ email: 'email', name: 'username'}` | Sets the `email` and `name` fields to the corresponding Sentry SDK user fields that were called with `Sentry.setUser`. | By default, the Feedback integration will attempt to fill in the name and email fields if you've set a user context via `Sentry.setUser()`. The email and name fields are expected to be `email` and `username`. Below is an example configuration with non-default user fields: @@ -65,20 +65,20 @@ feedbackIntegration({ Most text that you see in the default Feedback widget can be customized. -| Key | Default | Description | -| -------------------- | -------------------------------------- | ------------------------------------------------------------------ | -| `buttonLabel` | `Report a Bug` | The label of the injected button. | -| `submitButtonLabel` | `Send Bug Report` | The label of the submit button used in the feedback form. | -| `cancelButtonLabel` | `Cancel` | The label of the cancel button used in the feedback form. | -| `formTitle` | `Report a Bug` | The title at the top of the feedback form. | -| `nameLabel` | `Name` | The label of the name input field. | -| `namePlaceholder` | `Your Name` | The placeholder for the name input field. | -| `emailLabel` | `Email` | The label of the email input field. | -| `emailPlaceholder` | `your.email@example.org` | The placeholder for the email input field. | -| `messageLabel` | `Description` | The label for the feedback description input field. | -| `messagePlaceholder` | `What's the bug? What did you expect?` | The placeholder for the feedback description input field. | +| Key | Default | Description | +| -------------------- | -------------------------------------- | ------------------------------------------------------------------- | +| `buttonLabel` | `Report a Bug` | The label of the injected button. | +| `submitButtonLabel` | `Send Bug Report` | The label of the submit button used in the feedback form. | +| `cancelButtonLabel` | `Cancel` | The label of the cancel button used in the feedback form. | +| `formTitle` | `Report a Bug` | The title at the top of the feedback form. | +| `nameLabel` | `Name` | The label of the name input field. | +| `namePlaceholder` | `Your Name` | The placeholder for the name input field. | +| `emailLabel` | `Email` | The label of the email input field. | +| `emailPlaceholder` | `your.email@example.org` | The placeholder for the email input field. | +| `messageLabel` | `Description` | The label for the feedback description input field. | +| `messagePlaceholder` | `What's the bug? What did you expect?` | The placeholder for the feedback description input field. | | `successMessageText` | `Thank you for your report!` | The message to be displayed after a successful feedback submission. | -| `isRequiredText` | `(required)` | The text displayed next to a required field. | +| `isRequiredText` | `(required)` | The text displayed next to a required field. | Example of customization: diff --git a/docs/platforms/javascript/common/user-feedback/index.mdx b/docs/platforms/javascript/common/user-feedback/index.mdx index 55ce4afc68739..d3923369258d4 100644 --- a/docs/platforms/javascript/common/user-feedback/index.mdx +++ b/docs/platforms/javascript/common/user-feedback/index.mdx @@ -18,7 +18,7 @@ The User Feedback feature allows you to collect user feedback from anywhere insi feature. Lower versions may have limited functionality. - + ## User Feedback Widget diff --git a/docs/platforms/javascript/guides/connect/configuration/integrations/contextlines.mdx b/docs/platforms/javascript/guides/connect/configuration/integrations/contextlines.mdx deleted file mode 100644 index 7b3af58727490..0000000000000 --- a/docs/platforms/javascript/guides/connect/configuration/integrations/contextlines.mdx +++ /dev/null @@ -1,20 +0,0 @@ ---- -title: ContextLines -description: "Adds source code to your stack frames. (default)" ---- - -_Import name: `Sentry.contextLinesIntegration`_ - -This integration is enabled by default. If you'd like to modify your default integrations, read [this](./../#modifying-default-integrations). - -This integration adds source code to your stack frames. It ensures that you can see the code that caused the error directly in the Sentry UI. - - - -## Options - -### `frameContextLines` - -_Type: `number`_ - -The number of lines to collect around each stack frame's line number. Defaults to 7. diff --git a/docs/platforms/javascript/guides/connect/index.mdx b/docs/platforms/javascript/guides/connect/index.mdx deleted file mode 100644 index 99fcbef7ffb95..0000000000000 --- a/docs/platforms/javascript/guides/connect/index.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Connect -description: "Learn how to manually set up Sentry in your Connect app and capture your first errors." -sdk: sentry.javascript.node -fallbackGuide: javascript.node -categories: - - server - - server-only ---- - - diff --git a/docs/platforms/javascript/guides/connect/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/javascript/guides/connect/tracing/instrumentation/automatic-instrumentation.mdx deleted file mode 100644 index 2f7c38261d7f1..0000000000000 --- a/docs/platforms/javascript/guides/connect/tracing/instrumentation/automatic-instrumentation.mdx +++ /dev/null @@ -1,6 +0,0 @@ ---- -title: Automatic Instrumentation -description: "Learn what transactions are captured after tracing is enabled in the Sentry Connect SDK." ---- - - diff --git a/docs/product/logs/getting-started/index.mdx b/docs/product/logs/getting-started/index.mdx index c1a6d6ab9795b..f84a07acc664a 100644 --- a/docs/product/logs/getting-started/index.mdx +++ b/docs/product/logs/getting-started/index.mdx @@ -54,7 +54,7 @@ To set up Sentry Logs, use the links below for supported SDKs. After it's been s skill="sentry-cloudflare-sdk" /> - +- - +- ### Rust diff --git a/docs/product/metrics/getting-started/index.mdx b/docs/product/metrics/getting-started/index.mdx index 7cbf192e47c74..246456be89627 100644 --- a/docs/product/metrics/getting-started/index.mdx +++ b/docs/product/metrics/getting-started/index.mdx @@ -54,7 +54,7 @@ To set up Sentry's Application Metrics, use the links below for supported SDKs. skill="sentry-cloudflare-sdk" /> - -Application Metrics are enabled by default. +Application Metrics are enabled by +default. @@ -8,16 +9,37 @@ Send test metrics from your app to verify that metrics are arriving in Sentry: - -In a Node.js runtime, you can use the [NodeRuntimeMetrics](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics/) integration to automatically collect Node.js runtime health metrics. + + + In a Node.js runtime, you can use the + [NodeRuntimeMetrics](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics/) + integration to automatically collect Node.js runtime health metrics. + ```javascript -Sentry.metrics.count("checkout.failed", 1) -Sentry.metrics.gauge("queue.depth", 42) +Sentry.metrics.count("checkout.failed", 1); +Sentry.metrics.gauge("queue.depth", 42); Sentry.metrics.distribution("api_latency", 187, { unit: "millisecond", }); diff --git a/includes/quick-start-features-expandable.mdx b/includes/quick-start-features-expandable.mdx index 8ee5e2d2aef86..86de01e4c4b92 100644 --- a/includes/quick-start-features-expandable.mdx +++ b/includes/quick-start-features-expandable.mdx @@ -12,7 +12,7 @@ import { FeatureInfo } from "sentry-docs/components/featureInfo"; "sessionReplay", "logs", "userFeedback", - "metrics" + "metrics", ]} type="learnMore" /> @@ -21,13 +21,20 @@ import { FeatureInfo } from "sentry-docs/components/featureInfo"; - + - + diff --git a/includes/quick-start-locate-data-expandable.mdx b/includes/quick-start-locate-data-expandable.mdx index db053a6c3d22a..a10a3647d876a 100644 --- a/includes/quick-start-locate-data-expandable.mdx +++ b/includes/quick-start-locate-data-expandable.mdx @@ -12,7 +12,7 @@ import { FeatureInfo } from "sentry-docs/components/featureInfo"; "sessionReplay", "logs", "userFeedback", - "metrics" + "metrics", ]} type="findInSentry" /> @@ -21,13 +21,20 @@ import { FeatureInfo } from "sentry-docs/components/featureInfo"; - + - + diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index cb6da7d5b4f7f..e73e949efbd3d 100644 --- a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx @@ -39,7 +39,7 @@ To verify that the distribution has been set correctly in the SDK, open an issue If you've uploaded source maps and they aren't applying to your code in an issue in Sentry, take a look at the JSON of the event and look for the `abs_path` to see exactly where we're attempting to resolve the file - for example, `http://localhost:8000/scripts/script.js` (`abs_path` will appear once for each frame in the stack trace - match this up with the file(s) that are not deminified.). A link to the JSON view can be found at the top of the issue page next to the date the event occurred. The uploaded artifact names must match these values. -If you have **dynamic values in your path** (for example, `https://www.site.com/{some_value}/scripts/script.js`), you may want to use the `rewriteFrames` integration`rewriteFrames` integration to change your `abs_path` values. +If you have **dynamic values in your path** (for example, `https://www.site.com/{some_value}/scripts/script.js`), you may want to use the `rewriteFrames` integration`rewriteFrames` integration to change your `abs_path` values. ### Using sentry-cli diff --git a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx index aa5af4955018b..25d482e2cc9c2 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -98,7 +98,11 @@ module.exports = { sourcemaps: { // As you're enabling client source maps, you probably want to delete them after they're uploaded to Sentry. // Set the appropriate glob pattern for your output folder - some glob examples below: - filesToDeleteAfterUpload: ["./**/*.map", ".*/**/public/**/*.map", "./dist/**/client/**/*.map"] + filesToDeleteAfterUpload: [ + "./**/*.map", + ".*/**/public/**/*.map", + "./dist/**/client/**/*.map", + ], }, // Auth tokens can be obtained from @@ -163,7 +167,11 @@ module.exports = { sourcemaps: { // As you're enabling client source maps, you probably want to delete them after they're uploaded to Sentry. // Set the appropriate glob pattern for your output folder - some glob examples below: - filesToDeleteAfterUpload: ["./**/*.map", ".*/**/public/**/*.map", "./dist/**/client/**/*.map"] + filesToDeleteAfterUpload: [ + "./**/*.map", + ".*/**/public/**/*.map", + "./dist/**/client/**/*.map", + ], }, release: { @@ -232,7 +240,11 @@ require("esbuild").build({ sourcemaps: { // As you're enabling client source maps, you probably want to delete them after they're uploaded to Sentry. // Set the appropriate glob pattern for your output folder - some glob examples below: - filesToDeleteAfterUpload: ["./**/*.map", ".*/**/public/**/*.map", "./dist/**/client/**/*.map"] + filesToDeleteAfterUpload: [ + "./**/*.map", + ".*/**/public/**/*.map", + "./dist/**/client/**/*.map", + ], }, release: { @@ -328,7 +340,7 @@ To verify that the distribution has been set correctly in the SDK, open an issue If you've uploaded source maps and they aren't applying to your code in an issue in Sentry, take a look at the JSON of the event and look for the `abs_path` to see exactly where we're attempting to resolve the file - for example, `http://localhost:8000/scripts/script.js` (`abs_path` will appear once for each frame in the stack trace - match this up with the file(s) that are not deminified.). A link to the JSON view can be found at the top of the issue page next to the date the event occurred. The uploaded artifact names must match these values. -If you have **dynamic values in your path** (for example, `https://www.site.com/{some_value}/scripts/script.js`), you may want to use the `rewriteFrames` integration`rewriteFrames` integration to change your `abs_path` values. +If you have **dynamic values in your path** (for example, `https://www.site.com/{some_value}/scripts/script.js`), you may want to use the `rewriteFrames` integration`rewriteFrames` integration to change your `abs_path` values. #### Using sentry-cli diff --git a/platform-includes/sourcemaps/overview/javascript.capacitor.mdx b/platform-includes/sourcemaps/overview/javascript.capacitor.mdx index 2e80008f76640..b74174eb06ba6 100644 --- a/platform-includes/sourcemaps/overview/javascript.capacitor.mdx +++ b/platform-includes/sourcemaps/overview/javascript.capacitor.mdx @@ -33,9 +33,13 @@ If you used Create React App to set up your React application see our Ionic Capacitor build +- + Ionic Capacitor build + - Ionic Build -- TypeScript (tsc) +- + TypeScript (tsc) + If you're using one of webpack, Vite, Rollup, or Esbuild, use the @@ -50,7 +54,7 @@ If you used Create React App to set up your React application see our Sentry CLI. - + diff --git a/platform-includes/sourcemaps/overview/javascript.mdx b/platform-includes/sourcemaps/overview/javascript.mdx index 0461bec03fa66..caaa709cc9c21 100644 --- a/platform-includes/sourcemaps/overview/javascript.mdx +++ b/platform-includes/sourcemaps/overview/javascript.mdx @@ -43,7 +43,9 @@ If you used Create React App to set up your React application see our TypeScript (tsc) +- + TypeScript (tsc) + If you're using one of webpack, Vite, Rollup, or Esbuild, use the @@ -58,7 +60,7 @@ If you used Create React App to set up your React application see our Sentry CLI. - + diff --git a/platform-includes/sourcemaps/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 0a478c5e54635..9015bf368ce4e 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -133,7 +133,6 @@ Sometimes build scripts and plugins produce pre-compressed minified files (for e 'javascript.node', 'javascript.aws-lambda', 'javascript.azure-functions', - 'javascript.connect', 'javascript.express', 'javascript.fastify', 'javascript.gcp-functions', diff --git a/platform-includes/sourcemaps/upload/primer/javascript.mdx b/platform-includes/sourcemaps/upload/primer/javascript.mdx index f181c01f57bc5..45e543f4beaf5 100644 --- a/platform-includes/sourcemaps/upload/primer/javascript.mdx +++ b/platform-includes/sourcemaps/upload/primer/javascript.mdx @@ -1,7 +1,7 @@ We provide guides on uploading source maps to Sentry for the most popular JavaScript build tools. Pick one from the list below to learn more. - + @@ -11,7 +11,7 @@ If you can't find the tool of your choice in the list below, we recommend you ch - + diff --git a/redirects.js b/redirects.js index ce4a3cae7c455..4927a57b6ef9a 100644 --- a/redirects.js +++ b/redirects.js @@ -588,6 +588,11 @@ const developerDocsRedirects = [ /** @type {import('next/dist/lib/load-custom-routes').Redirect[]} */ const userDocsRedirects = [ + // Connect guide removed (SDK no longer supports Connect) → Node + { + source: '/platforms/javascript/guides/connect/:path*', + destination: '/platforms/javascript/guides/node/:path*', + }, // Guides → Get Started restructure { source: '/guides/',