From 94c626bf8b3929d98520407dbfacbcd9392b488d Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Mon, 10 Aug 2026 11:30:32 -0700 Subject: [PATCH] fix(seo): enforce trailing slashes on internal links to fix 134 non-indexable canonicals Three changes to eliminate broken canonical chains caused by missing trailing slashes: 1. SmartLink normalization: Add ensureTrailingSlash() to src/utils.ts and apply it in SmartLink for all internal links. This prevents future regressions by normalizing URLs at render time, avoiding 308 redirects that break canonical signal chains. 2. Content link cleanup: Fix 732 internal links across 366 content files (docs/, includes/, platform-includes/) that were missing trailing slashes on markdown links and PlatformLink to= props. 3. MD export canonical URLs: Fix generate-md-exports.mjs to include trailing slashes in canonical URLs embedded in export HTML, matching the behavior of generateMetadata() and middleware. Also consolidates the duplicated appendSlash() helper in sitemap.ts to use the shared ensureTrailingSlash() utility. --- app/sitemap.ts | 10 +--- docs/api/guides/teams-tutorial.mdx | 2 +- docs/api/index.mdx | 2 +- docs/cli/crons.mdx | 4 +- docs/cli/logs.mdx | 6 +- .../event-grouping/stack-trace-rules.mdx | 4 +- .../searchable-properties/session-replay.mdx | 2 +- docs/contributing/approach/sdk-docs/index.mdx | 10 ++-- docs/contributing/linking.mdx | 2 +- .../data-forwarding/grafana/index.mdx | 2 +- docs/integrations/deployment/expo/index.mdx | 2 +- docs/integrations/deployment/vercel/index.mdx | 2 +- .../integrations/feature-flag/split/index.mdx | 2 +- docs/integrations/index.mdx | 4 +- .../integration-platform/index.mdx | 8 +-- .../internal-integration.mdx | 2 +- .../public-integration.mdx | 2 +- .../ui-components/alert-action.mdx | 16 +++--- .../ui-components/formfield.mdx | 6 +- .../ui-components/index.mdx | 6 +- .../ui-components/issue-link.mdx | 4 +- .../integration-platform/webhooks.mdx | 2 +- .../webhooks/activity-alerts.mdx | 2 +- .../webhooks/installation.mdx | 2 +- .../webhooks/issue-alerts.mdx | 2 +- .../webhooks/metric-alerts.mdx | 2 +- .../issue-tracking/sourcegraph.mdx | 2 +- .../integrations/session-replay/fullstory.mdx | 2 +- .../session-replay/openreplay.mdx | 2 +- .../source-code-mgmt/azure-devops/index.mdx | 2 +- .../source-code-mgmt/bitbucket/index.mdx | 2 +- .../source-code-mgmt/github/index.mdx | 2 +- .../source-code-mgmt/gitlab/index.mdx | 2 +- .../android/build-distribution/index.mdx | 2 +- .../android/configuration/gradle.mdx | 4 +- .../android/configuration/options.mdx | 4 +- .../android/configuration/webview.mdx | 2 +- .../debug-files/source-context/index.mdx | 2 +- .../enhance-errors/kotlin-compiler-plugin.mdx | 4 +- .../android/enhance-errors/proguard.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/viewhierarchy/index.mdx | 2 +- docs/platforms/android/features/index.mdx | 38 ++++++------- docs/platforms/android/index.mdx | 10 ++-- .../android/integrations/apollo3/index.mdx | 2 +- .../android/integrations/apollo4/index.mdx | 2 +- docs/platforms/android/manual-setup/index.mdx | 2 +- docs/platforms/android/overhead/index.mdx | 6 +- docs/platforms/android/profiling/index.mdx | 8 +-- .../android/profiling/legacy/index.mdx | 2 +- .../profiling/troubleshooting/index.mdx | 6 +- .../session-replay/troubleshooting.mdx | 2 +- .../platforms/android/size-analysis/index.mdx | 2 +- .../automatic-instrumentation.mdx | 4 +- .../apple/common/configuration/app-hangs.mdx | 2 +- .../apple/common/configuration/webview.mdx | 2 +- .../common/data-management/data-collected.mdx | 10 ++-- .../debug-files/source-context/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/viewhierarchy/index.mdx | 2 +- .../platforms/apple/common/features/index.mdx | 32 +++++------ .../platforms/apple/common/overhead/index.mdx | 6 +- .../profiling/troubleshooting/index.mdx | 2 +- .../apple/common/session-replay/index.mdx | 2 +- .../common/session-replay/troubleshooting.mdx | 2 +- .../automatic-instrumentation.mdx | 6 +- .../apple/common/troubleshooting/index.mdx | 4 +- .../guides/ios/build-distribution/index.mdx | 2 +- .../apple/guides/ios/features/index.mdx | 26 ++++----- .../apple/guides/ios/manual-setup.mdx | 2 +- .../apple/guides/ios/size-analysis/index.mdx | 2 +- .../apple/guides/macos/features/index.mdx | 24 ++++---- .../apple/guides/tvos/features/index.mdx | 20 +++---- .../apple/guides/visionos/features/index.mdx | 18 +++--- .../apple/guides/watchos/features/index.mdx | 18 +++--- .../dart/common/configuration/filtering.mdx | 2 +- .../dart/common/configuration/options.mdx | 6 +- .../common/data-management/data-collected.mdx | 2 +- .../data-management/sensitive-data/index.mdx | 2 +- .../enriching-events/attributes/index.mdx | 6 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- docs/platforms/dart/common/features/index.mdx | 6 +- docs/platforms/dart/common/index.mdx | 6 +- docs/platforms/dart/common/overhead/index.mdx | 2 +- .../tracing/trace-propagation/index.mdx | 2 +- .../flutter/configuration/filtering.mdx | 2 +- .../guides/flutter/configuration/options.mdx | 6 +- .../guides/flutter/configuration/webview.mdx | 2 +- .../data-management/sensitive-data/index.mdx | 2 +- .../guides/flutter/debug-symbols/index.mdx | 4 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/viewhierarchy/index.mdx | 2 +- .../dart/guides/flutter/features/index.mdx | 30 +++++----- docs/platforms/dart/guides/flutter/index.mdx | 4 +- .../dart/guides/flutter/manual-setup.mdx | 4 +- .../dart/guides/flutter/overhead/index.mdx | 4 +- .../profiling/troubleshooting/index.mdx | 2 +- .../guides/flutter/size-analysis/index.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- .../tracing/trace-propagation/index.mdx | 2 +- .../dart/guides/flutter/troubleshooting.mdx | 2 +- .../dotnet/common/configuration/msbuild.mdx | 4 +- docs/platforms/dotnet/common/crons/index.mdx | 2 +- .../debug-files/upload/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../profiling/troubleshooting/index.mdx | 2 +- .../instrumentation/opentelemetry-otlp.mdx | 2 +- .../platforms/dotnet/guides/android/index.mdx | 4 +- docs/platforms/dotnet/guides/apple/index.mdx | 4 +- .../dotnet/guides/aspnetcore/index.mdx | 2 +- docs/platforms/dotnet/guides/maui/index.mdx | 6 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- docs/platforms/go/common/usage/index.mdx | 2 +- .../godot/data-management/data-collected.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/view-hierarchy/index.mdx | 2 +- .../java/common/configuration/options.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../java/common/integrations/reactor.mdx | 2 +- docs/platforms/java/common/legacy/index.mdx | 4 +- .../java/common/legacy/log4j2/index.mdx | 2 +- .../java/common/legacy/logback/index.mdx | 2 +- .../java/common/legacy/logging/index.mdx | 2 +- .../java/common/legacy/spring/index.mdx | 2 +- .../java/common/migration/6.x-to-7.0.mdx | 2 +- .../common/opentelemetry/setup/agentless.mdx | 2 +- .../java/common/opentelemetry/setup/index.mdx | 6 +- .../java/common/opentelemetry/setup/otlp.mdx | 2 +- .../tracing/instrumentation/apollo2.mdx | 2 +- .../tracing/instrumentation/apollo3.mdx | 4 +- .../tracing/instrumentation/apollo4.mdx | 2 +- .../tracing/instrumentation/opentelemetry.mdx | 2 +- .../multiple-sentry-instances.mdx | 2 +- .../javascript/common/configuration/apis.mdx | 8 +-- .../common/configuration/filtering.mdx | 2 +- .../integrations/bunruntimemetrics.mdx | 2 +- .../integrations/denoruntimemetrics.mdx | 2 +- .../integrations/elementtiming.mdx | 2 +- .../configuration/integrations/vercelai.mdx | 6 +- .../common/configuration/options.mdx | 14 ++--- .../common/configuration/tree-shaking.mdx | 6 +- .../data-management/data-collected/index.mdx | 8 +-- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../common/install/esm-without-import.mdx | 2 +- .../v7-to-v8/v8-new-performance-api.mdx | 2 +- .../common/opentelemetry/custom-setup.mdx | 4 +- .../common/session-replay/index.mdx | 4 +- .../sourcemaps/uploading/ionic-capacitor.mdx | 2 +- .../dealing-with-cors-issues/index.mdx | 2 +- .../tracing/distributed-tracing/index.mdx | 4 +- .../javascript/common/tracing/index.mdx | 2 +- .../common/tracing/troubleshooting/index.mdx | 2 +- .../common/troubleshooting/index.mdx | 6 +- .../javascript/common/user-feedback/index.mdx | 2 +- .../javascript/guides/angular/index.mdx | 12 ++-- .../guides/angular/manual-setup.mdx | 12 ++-- .../guides/aws-lambda/install/layer__v7.x.mdx | 2 +- .../guides/aws-lambda/install/layer__v8.x.mdx | 4 +- .../guides/aws-lambda/install/npm.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- .../guides/azure-functions/index.mdx | 6 +- .../platforms/javascript/guides/bun/index.mdx | 8 +-- .../javascript/guides/capacitor/index.mdx | 10 ++-- .../configuration/integrations/prisma.mdx | 2 +- .../cloudflare/features/durableobject.mdx | 2 +- .../cloudflare/features/nodejs-compat.mdx | 4 +- .../frameworks/hydrogen-react-router.mdx | 8 +-- .../cloudflare/frameworks/tanstack-start.mdx | 6 +- .../javascript/guides/cloudflare/index.mdx | 6 +- .../javascript/guides/cordova/index.mdx | 10 ++-- .../javascript/guides/deno/index.mdx | 8 +-- .../javascript/guides/effect/index.mdx | 2 +- .../integrations/browserwindowsession.mdx | 2 +- .../integrations/mainprocesssession.mdx | 2 +- .../javascript/guides/electron/index.mdx | 8 +-- .../javascript/guides/elysia/index.mdx | 8 +-- .../ember/configuration/ember-options.mdx | 2 +- .../javascript/guides/firebase/index.mdx | 8 +-- .../javascript/guides/gatsby/index.mdx | 6 +- .../javascript/guides/gcp-functions/index.mdx | 6 +- .../javascript/guides/hono/index.mdx | 10 ++-- .../javascript/guides/nestjs/index.mdx | 8 +-- .../nestjs/install/esm-without-import.mdx | 2 +- .../nextjs/configuration/build/index.mdx | 2 +- .../javascript/guides/nextjs/logs/index.mdx | 2 +- .../guides/nextjs/manual-setup/index.mdx | 2 +- .../nextjs/manual-setup/pages-router.mdx | 2 +- .../javascript/guides/nitro/index.mdx | 8 +-- .../features/nitro-deployment-presets.mdx | 2 +- .../javascript/guides/nuxt/index.mdx | 4 +- .../guides/nuxt/install/cli-import.mdx | 2 +- .../guides/nuxt/install/dynamic-import.mdx | 4 +- .../nuxt/install/limited-server-tracing.mdx | 2 +- .../javascript/guides/react-router/index.mdx | 8 +-- .../guides/react-router/manual-setup.mdx | 6 +- .../guides/react/features/react-router/v6.mdx | 8 +-- .../guides/react/features/react-router/v7.mdx | 8 +-- .../guides/react/features/react-router/v8.mdx | 6 +- .../javascript/guides/remix/index.mdx | 4 +- .../javascript/guides/remix/manual-setup.mdx | 2 +- .../guides/remix/manual-setup__v8.x.mdx | 4 +- .../guides/solid/features/index.mdx | 2 +- .../javascript/guides/solid/index.mdx | 10 ++-- .../javascript/guides/solidstart/index.mdx | 4 +- .../guides/solidstart/install/cli-import.mdx | 2 +- .../solidstart/install/dynamic-import.mdx | 4 +- .../install/limited-server-tracing.mdx | 2 +- .../javascript/guides/svelte/index.mdx | 8 +-- .../javascript/guides/sveltekit/index.mdx | 4 +- .../sveltekit/manual-setup__v10.7.0.mdx | 4 +- .../manual-setup/index.mdx | 4 +- .../platforms/javascript/guides/vue/index.mdx | 8 +-- .../javascript/guides/wasm/index.mdx | 6 +- .../guides/compose-multiplatform/index.mdx | 2 +- .../debug-symbols/index.mdx | 4 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/viewhierarchy/index.mdx | 2 +- .../kotlin-multiplatform/features/index.mdx | 6 +- .../guides/kotlin-multiplatform/index.mdx | 8 +-- .../kotlin-multiplatform/troubleshooting.mdx | 2 +- docs/platforms/kotlin/index.mdx | 6 +- .../native/common/configuration/options.mdx | 4 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../native/configuration/backends/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../php/common/integrations/otlp/index.mdx | 2 +- .../php/common/troubleshooting/index.mdx | 2 +- .../php/guides/laravel/integrations/otlp.mdx | 2 +- .../php/guides/symfony/integrations/otlp.mdx | 2 +- docs/platforms/php/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- docs/platforms/powershell/index.mdx | 2 +- .../python/configuration/filtering/index.mdx | 2 +- .../python/configuration/options.mdx | 8 +-- .../enriching-events/attributes/index.mdx | 10 ++-- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../python/integrations/anthropic/index.mdx | 4 +- .../integrations/gcp-functions/index.mdx | 2 +- .../integrations/google-genai/index.mdx | 4 +- .../python/integrations/graphene/index.mdx | 4 +- .../integrations/huggingface_hub/index.mdx | 4 +- .../python/integrations/langchain/index.mdx | 4 +- .../python/integrations/langgraph/index.mdx | 4 +- .../python/integrations/litellm/index.mdx | 4 +- .../python/integrations/litestar/index.mdx | 2 +- .../python/integrations/loguru/index.mdx | 2 +- .../python/integrations/openai/index.mdx | 4 +- .../python/integrations/otlp/index.mdx | 4 +- .../python/integrations/starlite/index.mdx | 2 +- docs/platforms/python/profiling/index.mdx | 2 +- docs/platforms/python/sampling.mdx | 2 +- .../tracing/configure-sampling/index.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- docs/platforms/python/troubleshooting.mdx | 2 +- .../common/configuration/webview.mdx | 4 +- .../common/data-management/data-collected.mdx | 4 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../common/enriching-events/context/index.mdx | 2 +- .../enriching-events/viewhierarchy/index.mdx | 2 +- docs/platforms/react-native/common/index.mdx | 6 +- .../common/manual-setup/manual-setup.mdx | 4 +- .../common/manual-setup/metro.mdx | 4 +- .../react-native/common/overhead/index.mdx | 4 +- .../profiling/troubleshooting/index.mdx | 4 +- .../common/size-analysis/index.mdx | 2 +- .../react-native/common/sourcemaps/index.mdx | 2 +- .../legacy-uploading-methods.mdx | 2 +- .../common/sourcemaps/uploading/codepush.mdx | 4 +- .../automatic-instrumentation.mdx | 6 +- .../instrumentation/react-navigation.mdx | 2 +- .../instrumentation/time-to-display.mdx | 2 +- .../common/troubleshooting/index.mdx | 8 +-- .../react-native/guides/expo/index.mdx | 2 +- .../tracing/instrumentation/expo-router.mdx | 2 +- .../enriching-events/attributes/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../ruby/common/integrations/index.mdx | 2 +- .../ruby/common/integrations/otlp/index.mdx | 2 +- .../platforms/ruby/common/troubleshooting.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../debug-files/upload/index.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../enriching-events/view-hierarchy/index.mdx | 2 +- .../usage/automatic-error-capture/index.mdx | 2 +- .../configuration/debug-symbols/index.mdx | 2 +- .../unreal/data-management/data-collected.mdx | 2 +- .../enriching-events/breadcrumbs/index.mdx | 2 +- .../quotas/manage-attachments-quota.mdx | 2 +- docs/product/agents/getting-started.mdx | 2 +- .../sentry-dashboards/backend/queries.mdx | 2 +- .../sentry-dashboards/frontend/assets.mdx | 2 +- .../mobile/mobile-vitals/app-starts.mdx | 2 +- .../outbound-api-requests.mdx | 2 +- docs/product/issues/issue-details/index.mdx | 6 +- .../function-regressions.mdx | 2 +- .../performance-issues/n-one-api-calls.mdx | 2 +- docs/product/issues/suspect-commits/index.mdx | 2 +- .../monitors/crons/troubleshooting.mdx | 4 +- docs/product/profiling/getting-started.mdx | 4 +- docs/product/profiling/index.mdx | 6 +- docs/product/profiling/profile-details.mdx | 2 +- .../transaction-vs-continuous-profiling.mdx | 4 +- docs/product/releases/health/index.mdx | 2 +- .../bitbucket-pipelines/index.mdx | 2 +- .../release-automation/netlify/index.mdx | 2 +- docs/product/sentry-toolbar/index.mdx | 2 +- .../snapshots/uploading-snapshots/index.mdx | 2 +- .../scrubbing/advanced-datascrubbing.mdx | 2 +- .../scrubbing/attachment-scrubbing.mdx | 2 +- includes/apple-platform-getting-started.mdx | 4 +- includes/build-distribution/intro.mdx | 2 +- .../app-start-instrumentation.mdx | 2 +- includes/dart-integrations/index.mdx | 30 +++++----- includes/insights-requests-body.mdx | 2 +- includes/logs/javascript-pino-integration.mdx | 2 +- includes/sentry-cli-sourcemaps.mdx | 2 +- .../watch-architecture-thinning.mdx | 2 +- .../config-intro/java.spring-boot.mdx | 2 +- .../dart-plugin/dart.flutter.mdx | 2 +- .../browser/javascript.mdx | 2 +- .../server/javascript.mdx | 2 +- .../automatic-breadcrumbs/react-native.mdx | 2 +- .../evaluation-tracking-index/android.mdx | 2 +- .../evaluation-tracking-index/java.mdx | 4 +- .../feature-flags/requirements/php.mdx | 2 +- .../javascript.astro.mdx | 10 ++-- .../getting-started-complete/javascript.mdx | 4 +- .../javascript.nuxt.mdx | 14 ++--- .../javascript.remix.mdx | 8 +-- .../javascript.sveltekit.mdx | 8 +-- .../getting-started-install/java.jul.mdx | 2 +- .../getting-started-install/java.log4j2.mdx | 2 +- .../getting-started-install/java.logback.mdx | 2 +- .../getting-started-install/java.mdx | 2 +- .../getting-started-install/java.servlet.mdx | 2 +- .../java.spring-boot.mdx | 2 +- .../getting-started-install/java.spring.mdx | 2 +- .../getting-started-node/javascript.mdx | 12 ++-- .../getting-started-primer/java.spring.mdx | 2 +- .../kotlin.kotlin-multiplatform.mdx | 2 +- .../getting-started-run/javascript.mdx | 2 +- .../javascript.mdx | 2 +- platform-includes/logs/setup/unity.mdx | 2 +- platform-includes/logs/usage/dart.mdx | 4 +- platform-includes/logs/usage/python.mdx | 4 +- .../metrics/requirements/php.laravel.mdx | 2 +- .../metrics/requirements/php.mdx | 2 +- .../metrics/requirements/php.symfony.mdx | 2 +- platform-includes/metrics/setup/unity.mdx | 2 +- .../metrics/usage/dart.flutter.mdx | 4 +- platform-includes/metrics/usage/dart.mdx | 4 +- platform-includes/metrics/usage/python.mdx | 6 +- .../important-changes/javascript.connect.mdx | 4 +- .../important-changes/javascript.express.mdx | 4 +- .../important-changes/javascript.fastify.mdx | 4 +- .../important-changes/javascript.koa.mdx | 4 +- .../important-changes/javascript.node.mdx | 4 +- .../important-changes/javascript.remix.mdx | 2 +- .../custom-performance-metrics/dart.mdx | 2 +- .../java.spring-boot.mdx | 2 +- .../java.spring.mdx | 4 +- .../set-release/react-native.mdx | 2 +- platform-includes/source-context/apple.mdx | 2 +- .../legacy-troubleshooting/javascript.mdx | 2 +- .../legacy-uploading-methods/javascript.mdx | 4 +- .../sourcemaps/troubleshooting/javascript.mdx | 2 +- .../upload/primer/javascript.sveltekit.mdx | 2 +- scripts/generate-md-exports.mjs | 47 ++++++++++----- src/components/smartLink.tsx | 11 +++- src/utils.test.ts | 57 +++++++++++++++++++ src/utils.ts | 18 ++++++ 372 files changed, 864 insertions(+), 765 deletions(-) create mode 100644 src/utils.test.ts diff --git a/app/sitemap.ts b/app/sitemap.ts index 7ba3a6c6ba460..0ce227ee12c76 100644 --- a/app/sitemap.ts +++ b/app/sitemap.ts @@ -2,6 +2,7 @@ import type {MetadataRoute} from 'next'; import {DEVELOP_DOCS_INDEXABLE_ROOTS} from 'sentry-docs/developDocsConfig'; import {type DocNode, getDocsRootNode} from 'sentry-docs/docTree'; import {isDeveloperDocs} from 'sentry-docs/isDeveloperDocs'; +import {ensureTrailingSlash} from 'sentry-docs/utils'; /** * Recursively extracts all slugs (paths) from a DocNode tree. @@ -50,13 +51,8 @@ export default async function sitemap(): Promise { } function docsToSitemap(paths: string[], baseUrl: string): MetadataRoute.Sitemap { - const appendSlash = (path: string) => { - if (path === '' || path.endsWith('/')) { - return path; - } - return path + '/'; - }; - const toFullUrl = (path: string) => `${appendSlash(baseUrl)}${appendSlash(path)}`; + const toFullUrl = (path: string) => + `${ensureTrailingSlash(baseUrl)}${ensureTrailingSlash(path)}`; const toSitemapEntry = (path: string) => ({url: toFullUrl(path)}); return ['', ...paths].map(toSitemapEntry); } diff --git a/docs/api/guides/teams-tutorial.mdx b/docs/api/guides/teams-tutorial.mdx index 3e334a6293b5f..43ddc73340e78 100644 --- a/docs/api/guides/teams-tutorial.mdx +++ b/docs/api/guides/teams-tutorial.mdx @@ -14,7 +14,7 @@ APIs used in this tutorial: - A Sentry authentication token with team:write scopes or higher and project:read scopes or higher. - > If you don't have an authentication token, follow the [Create a Sentry Authentication Token](/api/guides/create-auth-token) tutorial to create an organization token with the following permissions, or higher: + > If you don't have an authentication token, follow the [Create a Sentry Authentication Token](/api/guides/create-auth-token/) tutorial to create an organization token with the following permissions, or higher: > > - Organization: Read > - Team: Write diff --git a/docs/api/index.mdx b/docs/api/index.mdx index 0785f4610e928..25c1680d8a3f8 100644 --- a/docs/api/index.mdx +++ b/docs/api/index.mdx @@ -16,7 +16,7 @@ The current version of the Sentry's web API is considered **v0**. Our public end - [Authentication](/api/auth/) - [Pagination](/api/pagination/) - [Permissions](/api/permissions/) -- [Rate Limits](/api/ratelimits) +- [Rate Limits](/api/ratelimits/) - [Requests](/api/requests/) ### Sentry API Tutorials diff --git a/docs/cli/crons.mdx b/docs/cli/crons.mdx index a09e1036fc4cf..5f37997d0a0ab 100644 --- a/docs/cli/crons.mdx +++ b/docs/cli/crons.mdx @@ -18,7 +18,7 @@ Sentry Crons allows you to monitor the uptime and performance of any scheduled, To begin monitoring your recurring, scheduled job: -- [Install](/cli/installation) the Sentry CLI (min v2.16.1). +- [Install](/cli/installation/) the Sentry CLI (min v2.16.1). - Create and configure your first Monitor in [Sentry](https://sentry.io/issues/alerts/new/crons/) or [via the CLI](#creating-or-updating-a-monitor-through-a-check-in-optional). ## Configuration @@ -38,7 +38,7 @@ Alternatively, you can add it to your `~/.sentryclirc` config: dsn = ___PUBLIC_DSN___ ``` -Learn more about the CLI's [configuration file](/cli/configuration#configuration-file). +Learn more about the CLI's [configuration file](/cli/configuration/#configuration-file). ## Job Monitoring diff --git a/docs/cli/logs.mdx b/docs/cli/logs.mdx index 2f4459435ab46..d72115870288a 100644 --- a/docs/cli/logs.mdx +++ b/docs/cli/logs.mdx @@ -12,8 +12,8 @@ The `sentry-cli` tool can be used to view and stream logs from your Sentry proje To use the logs command, you need to: -- [Install](/cli/installation) the Sentry CLI -- [Authenticate](/cli/configuration) with Sentry using an auth token +- [Install](/cli/installation/) the Sentry CLI +- [Authenticate](/cli/configuration/) with Sentry using an auth token - Have logs enabled for your project ## Configuration @@ -30,7 +30,7 @@ Or by setting the `SENTRY_AUTH_TOKEN` environment variable: export SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___ ``` -Learn more about the CLI's [configuration file](/cli/configuration#configuration-file). +Learn more about the CLI's [configuration file](/cli/configuration/#configuration-file). ## Basic Usage diff --git a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx index a80299d2b9564..4e6ee52c3eb9c 100644 --- a/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx +++ b/docs/concepts/data-management/event-grouping/stack-trace-rules.mdx @@ -138,7 +138,7 @@ Frame categorization is heavily used by our newest grouping algorithm. You can m - `driver` - graphics drivers, and so on - `telemetry` - crash reporting and analytics frameworks -See [our source code](https://github.com/getsentry/sentry/blob/master/src/sentry/grouping/enhancer/enhancement-configs/mobile%402021-04-02.txt) for a full list of built-in categories. +See [our source code](https://github.com/getsentry/sentry/blob/master/src/sentry/grouping/enhancer/enhancement-configs/all-platforms%402023-01-11.txt) for a full list of built-in categories. @@ -217,7 +217,7 @@ For instance, the following marks all frames that are below a specific C++ names stack.function:myapplication::* +app ``` -See [in-app frames for Apple](/platforms/apple/usage/in-app-frames) to find out how the `sentry-cocoa` SDK marks frames as in-app. +See [in-app frames for Apple](/platforms/apple/usage/in-app-frames/) to find out how the `sentry-cocoa` SDK marks frames as in-app. #### Stack Trace Rules diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx index 40694cde41219..a752e667a6ce0 100644 --- a/docs/concepts/search/searchable-properties/session-replay.mdx +++ b/docs/concepts/search/searchable-properties/session-replay.mdx @@ -48,7 +48,7 @@ The `class` of an element that was clicked. No leading `.` is necessary. For exa The name of the frontend component that was clicked. For example, `MyAwesomeComponent` would match the React component ``. -Note: This property requires that your project have [React component name capturing configured](/platforms/javascript/guides/react/features/component-names). +Note: This property requires that your project have [React component name capturing configured](/platforms/javascript/guides/react/features/component-names/). - **Type:** string diff --git a/docs/contributing/approach/sdk-docs/index.mdx b/docs/contributing/approach/sdk-docs/index.mdx index d057022dee023..cc4a26a81a99d 100644 --- a/docs/contributing/approach/sdk-docs/index.mdx +++ b/docs/contributing/approach/sdk-docs/index.mdx @@ -18,7 +18,7 @@ SDKs provide content that focus on 10 sections (two of which are auto-generated) **[How to Write - Quick Start](/contributing/approach/sdk-docs/write-quick-start/)** To update existing Getting Started guides, use: - **[How to Write - Getting Started](/contributing/approach/sdk-docs/write-getting-started)** + **[How to Write - Getting Started](/contributing/approach/sdk-docs/write-getting-started/)** This content is used in two different areas for Sentry customers: @@ -29,13 +29,13 @@ SDKs provide content that focus on 10 sections (two of which are auto-generated) Covers all the ways customers can manage their implementation of the SDK. It consists of subpages (all of which can be turned on or off, as appropriate to the SDK). - **[How to Update: Configuration](/contributing/approach/sdk-docs/write-configuration)** + **[How to Update: Configuration](/contributing/approach/sdk-docs/write-configuration/)** 3) **Usage** Covers how to capture errors and messages, with a subpage to set the Level. - **[How to Update: Usage](/contributing/approach/sdk-docs/write-usage)** + **[How to Update: Usage](/contributing/approach/sdk-docs/write-usage/)** 4) **Troubleshooting** @@ -57,13 +57,13 @@ SDKs provide content that focus on 10 sections (two of which are auto-generated) Covers the data sent to Sentry, as well as how to customize it. - **[How to Update: Enriching Events](/contributing/approach/sdk-docs/write-enriching-events)** + **[How to Update: Enriching Events](/contributing/approach/sdk-docs/write-enriching-events/)** 8) **Data Management** section Covers our algorithm for grouping and how it can be modified, as well as how to scrub sensitive data using the SDK. - **[How to Update: Data Management](/contributing/approach/sdk-docs/write-data-management)** + **[How to Update: Data Management](/contributing/approach/sdk-docs/write-data-management/)** 9) (Auto-generated) **Other Guides** diff --git a/docs/contributing/linking.mdx b/docs/contributing/linking.mdx index bfaf1ab25f667..a54a4dd957e07 100644 --- a/docs/contributing/linking.mdx +++ b/docs/contributing/linking.mdx @@ -101,7 +101,7 @@ For instance, to use the image, `/public/product/monitors-and-alerts/alerts/issu `![Image alt text](product/monitors-and-alerts/alerts/issue-alert.png)` -The folder structure of `docs` is duplicated in `public` so that you can still use relative paths to reference images in your content files. For more details, see [Images](/contributing/pages/images). +The folder structure of `docs` is duplicated in `public` so that you can still use relative paths to reference images in your content files. For more details, see [Images](/contributing/pages/images/). ## Email address diff --git a/docs/integrations/data-forwarding/grafana/index.mdx b/docs/integrations/data-forwarding/grafana/index.mdx index c6ac31850ba09..4213647f5b004 100644 --- a/docs/integrations/data-forwarding/grafana/index.mdx +++ b/docs/integrations/data-forwarding/grafana/index.mdx @@ -5,7 +5,7 @@ description: "Learn about Sentry's Grafana integration, which allows you to quer --- -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). Visualize your Sentry [Issues](/product/issues/) and [Stats](/product/stats/) data in Grafana with the Sentry [data source plugin](https://grafana.com/grafana/plugins/grafana-sentry-datasource/). Once installed, you can combine Sentry data with that of other sources, like your infrastructure data through Prometheus or your business data from your data warehouse, in a single dashboard. diff --git a/docs/integrations/deployment/expo/index.mdx b/docs/integrations/deployment/expo/index.mdx index 175938fb0be73..26b86e52d9b80 100644 --- a/docs/integrations/deployment/expo/index.mdx +++ b/docs/integrations/deployment/expo/index.mdx @@ -8,7 +8,7 @@ description: "Learn how to integrate Sentry with Expo Application Services (EAS) -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/deployment/vercel/index.mdx b/docs/integrations/deployment/vercel/index.mdx index edaa87ca6b820..05c7456c69040 100644 --- a/docs/integrations/deployment/vercel/index.mdx +++ b/docs/integrations/deployment/vercel/index.mdx @@ -12,7 +12,7 @@ og_image: /og-images/organization-integrations-deployment-vercel.png -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/feature-flag/split/index.mdx b/docs/integrations/feature-flag/split/index.mdx index 21d7e15275582..e3daefa0f45c6 100644 --- a/docs/integrations/feature-flag/split/index.mdx +++ b/docs/integrations/feature-flag/split/index.mdx @@ -9,7 +9,7 @@ og_image: /og-images/organization-integrations-feature-flag-split.png -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/index.mdx b/docs/integrations/index.mdx index 81bc0fcadf1cf..70d7bc6ed7e92 100644 --- a/docs/integrations/index.mdx +++ b/docs/integrations/index.mdx @@ -11,7 +11,7 @@ Sentry integrates with your favorite apps and services. Each integration offers ## Integration Platform -Sentry’s integration platform provides a way for external services to interact with Sentry. Integrations utilizing this platform are first-class actors within Sentry, and you can build them for [public](/integrations/integration-platform/public-integration) as well as [internal](/integrations/integration-platform/internal-integration) use cases. +Sentry’s integration platform provides a way for external services to interact with Sentry. Integrations utilizing this platform are first-class actors within Sentry, and you can build them for [public](/integrations/integration-platform/public-integration/) as well as [internal](/integrations/integration-platform/internal-integration/) use cases. For more details, see the [full Integration Platform documentation](/integrations/integration-platform/). @@ -96,7 +96,7 @@ For more details, see the [full Integration Platform documentation](/integration | Integration | Link Issue to user sessions | | ------------------------------------------------------ | --------------------------- | | [Atlas](/integrations/session-replay/atlas/) | X | -| [BetterBugs](/integrations/session-replay/betterbugs) | X | +| [BetterBugs](/integrations/session-replay/betterbugs/) | X | | [FullStory](/integrations/session-replay/fullstory/) | X | | [Jam](/integrations/session-replay/jam/) | X | | [OpenReplay](/integrations/session-replay/openreplay/) | X | diff --git a/docs/integrations/integration-platform/index.mdx b/docs/integrations/integration-platform/index.mdx index fc532891c058e..87df8089f1a28 100644 --- a/docs/integrations/integration-platform/index.mdx +++ b/docs/integrations/integration-platform/index.mdx @@ -7,7 +7,7 @@ description: >- og_image: /og-images/organization-integrations-integration-platform.png --- -Sentry’s integration platform provides a way for external services to interact with Sentry using [webhooks](/integrations/integration-platform/webhooks/), [UI components](/integrations/integration-platform/ui-components/), and the [REST API](/api). Integrations using this platform are first-class actors within Sentry. +Sentry’s integration platform provides a way for external services to interact with Sentry using [webhooks](/integrations/integration-platform/webhooks/), [UI components](/integrations/integration-platform/ui-components/), and the [REST API](/api/). Integrations using this platform are first-class actors within Sentry. ## Example App @@ -19,7 +19,7 @@ It's a kanban application that uses many of the features available to Sentry int ## Creating an Integration -In [sentry.io](https://sentry.io), navigate to **Settings > Developer Settings**. From here, you can choose to create an [internal](/integrations/integration-platform/internal-integration) or [public](/integrations/integration-platform/public-integration) integration. Internal integrations can only be used by your organization, whereas public integrations can be published and are available for all Sentry users. +In [sentry.io](https://sentry.io), navigate to **Settings > Developer Settings**. From here, you can choose to create an [internal](/integrations/integration-platform/internal-integration/) or [public](/integrations/integration-platform/public-integration/) integration. Internal integrations can only be used by your organization, whereas public integrations can be published and are available for all Sentry users. ![Settings page that allows developer to choose between public or internal integrations.](./img/dev-settings.png) @@ -44,7 +44,7 @@ up as a service in the action section when creating or updating an alert. The in For your service to receive webhooks for alerts, you must have `Send a notification via ` as an action. Once that's set up, you'll start receiving webhook requests for triggered alerts. For more information about the request and payload, check out the [full Webhooks documentation](/integrations/integration-platform/webhooks/). -If you'd like users to provide more app-specific information to handle these webhooks (e.g. assignees, teams, notification channels), consider implementing the [alert action UI component](/integrations/integration-platform/ui-components/alert-action). +If you'd like users to provide more app-specific information to handle these webhooks (e.g. assignees, teams, notification channels), consider implementing the [alert action UI component](/integrations/integration-platform/ui-components/alert-action/). ## Permissions @@ -56,7 +56,7 @@ You can't create an integration or change an existing integration to have permis ## Auth Tokens -Auth tokens are passed using an auth header, and are used to authenticate as a user account with the API. [Public integrations](/integrations/integration-platform/public-integration) require an OAuth flow for tokens. [Internal integrations](/integrations/integration-platform/internal-integration) automatically generate tokens after installation. For more information, check out the [full Authentication documentation](/api/auth/). +Auth tokens are passed using an auth header, and are used to authenticate as a user account with the API. [Public integrations](/integrations/integration-platform/public-integration/) require an OAuth flow for tokens. [Internal integrations](/integrations/integration-platform/internal-integration/) automatically generate tokens after installation. For more information, check out the [full Authentication documentation](/api/auth/). ## Learn More diff --git a/docs/integrations/integration-platform/internal-integration.mdx b/docs/integrations/integration-platform/internal-integration.mdx index 6a40c45fe2eac..b699635e625d4 100644 --- a/docs/integrations/integration-platform/internal-integration.mdx +++ b/docs/integrations/integration-platform/internal-integration.mdx @@ -42,7 +42,7 @@ Internal integrations don't require logos or icons to be uploaded, but you can u - File format must be PNG - Background must be transparent (unless the logo takes up the entire space) -If the integration has a [UI component](/integrations/integration-platform/ui-components), you can also upload an icon that follows these requirements: +If the integration has a [UI component](/integrations/integration-platform/ui-components/), you can also upload an icon that follows these requirements: - Icon size must be between 256 × 256px and 1024 × 1024px - File must be a PNG in RGBA format diff --git a/docs/integrations/integration-platform/public-integration.mdx b/docs/integrations/integration-platform/public-integration.mdx index 099d57513e6c1..687f6d8ea1c09 100644 --- a/docs/integrations/integration-platform/public-integration.mdx +++ b/docs/integrations/integration-platform/public-integration.mdx @@ -193,7 +193,7 @@ Public integrations require a logo image to be uploaded. The requirements for th - File format must be PNG - Background must be transparent (unless the logo takes up the entire space) -If the integration has a [UI component](/integrations/integration-platform/ui-components), you must also upload an icon that follows these requirements: +If the integration has a [UI component](/integrations/integration-platform/ui-components/), you must also upload an icon that follows these requirements: - Icon size must be between 256 × 256px and 1024 × 1024px - File must be a PNG in RGBA format diff --git a/docs/integrations/integration-platform/ui-components/alert-action.mdx b/docs/integrations/integration-platform/ui-components/alert-action.mdx index 3e5b593505096..a30d96cdbb12d 100644 --- a/docs/integrations/integration-platform/ui-components/alert-action.mdx +++ b/docs/integrations/integration-platform/ui-components/alert-action.mdx @@ -8,9 +8,9 @@ og_image: >- An alert action component allows users to specify details specific to your service that can help route alerts when they're triggered in Sentry. The schema is defined on the integration details page, and when users set up an alert action with your integration, the associated UI components will be presented to them. The details they provide will be included in the following alert webhook payloads, when the alerts fire: -- [Issue Alert](/integrations/integration-platform/webhooks/issue-alerts) -- [Metric Alert](/integrations/integration-platform/webhooks/metric-alerts) -- [Activity Alert](/integrations/integration-platform/webhooks/activity-alerts) +- [Issue Alert](/integrations/integration-platform/webhooks/issue-alerts/) +- [Metric Alert](/integrations/integration-platform/webhooks/metric-alerts/) +- [Activity Alert](/integrations/integration-platform/webhooks/activity-alerts/) ![Example of an alert UI component.](./img/alert-component-action-example.png) @@ -40,8 +40,8 @@ An alert action component allows users to specify details specific to your servi - `title` - (Required) The title shown in the UI component. - `uri` - (Required) Sentry will make a POST request to the URI when the User submits the form. If the services fails to process the request (status code >= 400), this component will bubble up the error to the User with the provided response text. Check out our [URI Guidelines](/integrations/integration-platform/ui-components/#uri-guidelines) documentation for formatting help. -- `required_fields` - (Required) List of [FormField](/integrations/integration-platform/ui-components/formfield) components the User is required to complete. -- `optional_fields` - (Optional) List of [FormField](/integrations/integration-platform/ui-components/formfield) components the User may complete. +- `required_fields` - (Required) List of [FormField](/integrations/integration-platform/ui-components/formfield/) components the User is required to complete. +- `optional_fields` - (Optional) List of [FormField](/integrations/integration-platform/ui-components/formfield/) components the User may complete. - `description` - (Optional) Text that will be displayed above the form. Limited to 140 characters. ## Example @@ -86,7 +86,7 @@ An alert action component allows users to specify details specific to your servi ## Issue Alert Request Format -When an issue alert fires, your service will need to read the settings from the alert payload. The `settings` are in `data.issue_alert.settings`. Check out the full [Issue Alert webhook documentation](/integrations/integration-platform/webhooks/issue-alerts) for more information. +When an issue alert fires, your service will need to read the settings from the alert payload. The `settings` are in `data.issue_alert.settings`. Check out the full [Issue Alert webhook documentation](/integrations/integration-platform/webhooks/issue-alerts/) for more information. ```json { @@ -116,7 +116,7 @@ When an issue alert fires, your service will need to read the settings from the ## Metric Alert Request Format -When a metric alert fires, your service will need to read the settings from the alert payload. The `settings` in this example are nested in `data.metric_alert.alert_rule.triggers[1].actions[0].settings`. You will have to identify which trigger and action contains your settings based on the webhook type, so `triggers[1]` and `actions[0]` may not be accurate in your case. Check out the full [Metric Alert webhook documentation](/integrations/integration-platform/webhooks/metric-alerts) for more information. +When a metric alert fires, your service will need to read the settings from the alert payload. The `settings` in this example are nested in `data.metric_alert.alert_rule.triggers[1].actions[0].settings`. You will have to identify which trigger and action contains your settings based on the webhook type, so `triggers[1]` and `actions[0]` may not be accurate in your case. Check out the full [Metric Alert webhook documentation](/integrations/integration-platform/webhooks/metric-alerts/) for more information. ```json { @@ -160,7 +160,7 @@ When a metric alert fires, your service will need to read the settings from the ## Activity Alert Request Format -When an activity alert fires, your service will need to read the settings from the alert payload. The `settings` are in `data.alert.settings`. Check out the full [Activity Alert webhook documentation](/integrations/integration-platform/webhooks/activity-alerts) for more information. +When an activity alert fires, your service will need to read the settings from the alert payload. The `settings` are in `data.alert.settings`. Check out the full [Activity Alert webhook documentation](/integrations/integration-platform/webhooks/activity-alerts/) for more information. ```json { diff --git a/docs/integrations/integration-platform/ui-components/formfield.mdx b/docs/integrations/integration-platform/ui-components/formfield.mdx index c4d8a275d1580..9947a6ee3732c 100644 --- a/docs/integrations/integration-platform/ui-components/formfield.mdx +++ b/docs/integrations/integration-platform/ui-components/formfield.mdx @@ -4,7 +4,7 @@ sidebar_order: 4 description: "Learn about FormField components." --- -The [issue linking](/integrations/integration-platform/ui-components/issue-link) and [alert action](/integrations/integration-platform/ui-components/alert-action) UI components can use `FormField` components to display attributes in their respective modals. These components can render custom forms with inputs specified according to the schemes below. They behave similarly to their HTML equivalents. +The [issue linking](/integrations/integration-platform/ui-components/issue-link/) and [alert action](/integrations/integration-platform/ui-components/alert-action/) UI components can use `FormField` components to display attributes in their respective modals. These components can render custom forms with inputs specified according to the schemes below. They behave similarly to their HTML equivalents. ## Text @@ -23,7 +23,7 @@ The [issue linking](/integrations/integration-platform/ui-components/issue-link) - `label` - (Required) Label text to be rendered for the form field - `name` - (Required) Value to use in `name` attribute of the field -- `default` - default to pre-populate with. Options include `issue.title` and `issue.description`. Only used for [issue link](/integrations/integration-platform/ui-components/issue-link) components. +- `default` - default to pre-populate with. Options include `issue.title` and `issue.description`. Only used for [issue link](/integrations/integration-platform/ui-components/issue-link/) components. - `issue.title` - title of the Sentry issue - `issue.description` - description of the Sentry issue @@ -44,7 +44,7 @@ The [issue linking](/integrations/integration-platform/ui-components/issue-link) - `label` - (Required) Label text to be rendered for the form field - `name` - (Required) Value to use in `name` attribute of the field -- `default` - default to pre-populate with options include `issue.title` and `issue.description`. Only used for [issue link](/integrations/integration-platform/ui-components/issue-link) components. +- `default` - default to pre-populate with options include `issue.title` and `issue.description`. Only used for [issue link](/integrations/integration-platform/ui-components/issue-link/) components. - `issue.title` - title of the Sentry issue - `issue.description` - description of the Sentry issue diff --git a/docs/integrations/integration-platform/ui-components/index.mdx b/docs/integrations/integration-platform/ui-components/index.mdx index 0d5c91925eedb..0e1718b3e16fd 100644 --- a/docs/integrations/integration-platform/ui-components/index.mdx +++ b/docs/integrations/integration-platform/ui-components/index.mdx @@ -14,9 +14,9 @@ The Sentry integration platform provides developers with the ability to define c You can define the following components: -- [Issue Link](/integrations/integration-platform/ui-components/issue-link) (uses [FormField](/integrations/integration-platform/ui-components/formfield) components) -- [Alert Action](/integrations/integration-platform/ui-components/alert-action) (uses [FormField](/integrations/integration-platform/ui-components/formfield) components) -- [Stack Trace Link](/integrations/integration-platform/ui-components/stacktrace-link) +- [Issue Link](/integrations/integration-platform/ui-components/issue-link/) (uses [FormField](/integrations/integration-platform/ui-components/formfield/) components) +- [Alert Action](/integrations/integration-platform/ui-components/alert-action/) (uses [FormField](/integrations/integration-platform/ui-components/formfield/) components) +- [Stack Trace Link](/integrations/integration-platform/ui-components/stacktrace-link/) ## Schema diff --git a/docs/integrations/integration-platform/ui-components/issue-link.mdx b/docs/integrations/integration-platform/ui-components/issue-link.mdx index c9c64707786f8..92996331b71ca 100644 --- a/docs/integrations/integration-platform/ui-components/issue-link.mdx +++ b/docs/integrations/integration-platform/ui-components/issue-link.mdx @@ -42,8 +42,8 @@ When an external issue is created or linked in [sentry.io](https://sentry.io), a ## Attributes - `uri` - (Required) The URI to request when the User submits the Link/Create Issue form. Check out our [URI Guidelines](/integrations/integration-platform/ui-components/#uri-guidelines) documentation for formatting help. -- `required_fields` - (Required) List of [FormField](/integrations/integration-platform/ui-components/formfield) components the User is required to complete. -- `optional_fields` - (Optional) List of [FormField](/integrations/integration-platform/ui-components/formfield) components the User may complete. +- `required_fields` - (Required) List of [FormField](/integrations/integration-platform/ui-components/formfield/) components the User is required to complete. +- `optional_fields` - (Optional) List of [FormField](/integrations/integration-platform/ui-components/formfield/) components the User may complete. ## Example diff --git a/docs/integrations/integration-platform/webhooks.mdx b/docs/integrations/integration-platform/webhooks.mdx index e3b410c4832eb..c5735672722cd 100644 --- a/docs/integrations/integration-platform/webhooks.mdx +++ b/docs/integrations/integration-platform/webhooks.mdx @@ -103,7 +103,7 @@ An object with the `uuid` of the installation so that you can map the webhook re `data` -The data object contains information about the [resource](#sentry-hook-resource) and will differ in content depending on the type of webhook. This payload may be able to be customized via [UI components](/integrations/integration-platform/ui-components). +The data object contains information about the [resource](#sentry-hook-resource) and will differ in content depending on the type of webhook. This payload may be able to be customized via [UI components](/integrations/integration-platform/ui-components/). `actor` diff --git a/docs/integrations/integration-platform/webhooks/activity-alerts.mdx b/docs/integrations/integration-platform/webhooks/activity-alerts.mdx index eae8ac5861b7e..0f552d45a7333 100644 --- a/docs/integrations/integration-platform/webhooks/activity-alerts.mdx +++ b/docs/integrations/integration-platform/webhooks/activity-alerts.mdx @@ -73,7 +73,7 @@ The interactive demo below shows how to set up an internal integration that can ### data['alert']['settings'] - type: object -- description: the saved settings a user configured for routing when the alert was set up. Only available for [alert action UI components](/integrations/integration-platform/ui-components/alert-action). +- description: the saved settings a user configured for routing when the alert was set up. Only available for [alert action UI components](/integrations/integration-platform/ui-components/alert-action/). ## Payload diff --git a/docs/integrations/integration-platform/webhooks/installation.mdx b/docs/integrations/integration-platform/webhooks/installation.mdx index 79dd5fac065d9..1ddca01768115 100644 --- a/docs/integrations/integration-platform/webhooks/installation.mdx +++ b/docs/integrations/integration-platform/webhooks/installation.mdx @@ -4,7 +4,7 @@ sidebar_order: 1 description: "Learn more about Sentry's integration platform installation and uninstallation webhooks." --- -A [public Sentry integration](/integrations/integration-platform/public-integration) will receive installation and uninstallation webhooks. +A [public Sentry integration](/integrations/integration-platform/public-integration/) will receive installation and uninstallation webhooks. ## Sentry-Hook-Resource Header diff --git a/docs/integrations/integration-platform/webhooks/issue-alerts.mdx b/docs/integrations/integration-platform/webhooks/issue-alerts.mdx index 2fe34c11812c8..01dc44903b4cb 100644 --- a/docs/integrations/integration-platform/webhooks/issue-alerts.mdx +++ b/docs/integrations/integration-platform/webhooks/issue-alerts.mdx @@ -53,7 +53,7 @@ The interactive demo below shows how to set up an internal integration that can -The following two fields are for [alert action UI components](/integrations/integration-platform/ui-components/alert-action) only. +The following two fields are for [alert action UI components](/integrations/integration-platform/ui-components/alert-action/) only. diff --git a/docs/integrations/integration-platform/webhooks/metric-alerts.mdx b/docs/integrations/integration-platform/webhooks/metric-alerts.mdx index 9fcc3d0f48c13..b5576a2f02b8b 100644 --- a/docs/integrations/integration-platform/webhooks/metric-alerts.mdx +++ b/docs/integrations/integration-platform/webhooks/metric-alerts.mdx @@ -58,7 +58,7 @@ The interactive demo below shows how to set up an internal integration that can -The following field is for [alert action UI components](/integrations/integration-platform/ui-components/alert-action) only. +The following field is for [alert action UI components](/integrations/integration-platform/ui-components/alert-action/) only. diff --git a/docs/integrations/issue-tracking/sourcegraph.mdx b/docs/integrations/issue-tracking/sourcegraph.mdx index 11da024dbeb55..d1aeb66351519 100644 --- a/docs/integrations/issue-tracking/sourcegraph.mdx +++ b/docs/integrations/issue-tracking/sourcegraph.mdx @@ -6,7 +6,7 @@ description: "Learn about Sentry's Sourcegraph integration." -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/session-replay/fullstory.mdx b/docs/integrations/session-replay/fullstory.mdx index 4d9db0a9e1bfa..a467a9f228683 100644 --- a/docs/integrations/session-replay/fullstory.mdx +++ b/docs/integrations/session-replay/fullstory.mdx @@ -6,7 +6,7 @@ description: "Learn about Sentry's FullStory integration." -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/session-replay/openreplay.mdx b/docs/integrations/session-replay/openreplay.mdx index ed336b16ffc15..c0789eb973d78 100644 --- a/docs/integrations/session-replay/openreplay.mdx +++ b/docs/integrations/session-replay/openreplay.mdx @@ -6,7 +6,7 @@ description: "Learn about Sentry's OpenReplay integration." -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/integrations/source-code-mgmt/azure-devops/index.mdx b/docs/integrations/source-code-mgmt/azure-devops/index.mdx index b67dbb821a6fc..0f5a67a4c8dce 100644 --- a/docs/integrations/source-code-mgmt/azure-devops/index.mdx +++ b/docs/integrations/source-code-mgmt/azure-devops/index.mdx @@ -132,7 +132,7 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam -The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings). +The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context/#setting-up-code-mappings). diff --git a/docs/integrations/source-code-mgmt/bitbucket/index.mdx b/docs/integrations/source-code-mgmt/bitbucket/index.mdx index a5949f7f1d0ea..9bf8306c0202a 100644 --- a/docs/integrations/source-code-mgmt/bitbucket/index.mdx +++ b/docs/integrations/source-code-mgmt/bitbucket/index.mdx @@ -198,7 +198,7 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam -The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings). +The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context/#setting-up-code-mappings). diff --git a/docs/integrations/source-code-mgmt/github/index.mdx b/docs/integrations/source-code-mgmt/github/index.mdx index a78f4a5b4907e..fb9f2c27d6084 100644 --- a/docs/integrations/source-code-mgmt/github/index.mdx +++ b/docs/integrations/source-code-mgmt/github/index.mdx @@ -463,7 +463,7 @@ Stack trace linking takes you from a file in your Sentry stack trace to that sam -The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context#setting-up-code-mappings). +The following information is only valid for platforms which use traditional file paths. Platforms with package names require additional steps. For **Java**, read more in the [page on source context](/platforms/java/source-context/#setting-up-code-mappings). diff --git a/docs/integrations/source-code-mgmt/gitlab/index.mdx b/docs/integrations/source-code-mgmt/gitlab/index.mdx index 8f1cd28df59fa..714b3125c687a 100644 --- a/docs/integrations/source-code-mgmt/gitlab/index.mdx +++ b/docs/integrations/source-code-mgmt/gitlab/index.mdx @@ -201,7 +201,7 @@ For more details, see the full documentation for [Code Owners](/product/issues/o The Gitlab Seer integration is currently in early beta, slowly opening up to more organizations. Please reach out to seer@sentry.io if you are interested in trying it out. -With the GitLab integration connected, you can use Seer's AI features, including [Autofix](/product/ai-in-sentry/seer/autofix/) and [Code Review](/product/ai-in-sentry/seer/code-review) with your GitLab repositories. +With the GitLab integration connected, you can use Seer's AI features, including [Autofix](/product/ai-in-sentry/seer/autofix/) and [Code Review](/product/ai-in-sentry/seer/code-review/) with your GitLab repositories. **Autofix** analyzes Sentry issues using your GitLab repo code as context and can open a merge request with the proposed fix directly in GitLab. diff --git a/docs/platforms/android/build-distribution/index.mdx b/docs/platforms/android/build-distribution/index.mdx index 00a5db67e0423..4e23dab9412f7 100644 --- a/docs/platforms/android/build-distribution/index.mdx +++ b/docs/platforms/android/build-distribution/index.mdx @@ -7,7 +7,7 @@ description: Upload Android builds to Sentry for distribution to internal teams beta: true --- -[Build Distribution](/product/build-distribution) helps you securely distribute Android builds to your internal teams and beta testers. +[Build Distribution](/product/build-distribution/) helps you securely distribute Android builds to your internal teams and beta testers. ## Getting Started diff --git a/docs/platforms/android/configuration/gradle.mdx b/docs/platforms/android/configuration/gradle.mdx index 5c70b06393691..f230863e46a0c 100644 --- a/docs/platforms/android/configuration/gradle.mdx +++ b/docs/platforms/android/configuration/gradle.mdx @@ -432,7 +432,7 @@ sentry { } ``` -Checkout the full documentation on Source Context for more details. +Checkout the full documentation on Source Context for more details. ## Tracing Auto-instrumentation @@ -517,4 +517,4 @@ The plugin algorithm does the following when defining dependency versions: 3. If there are transitive dependencies on any of the integrations or the Sentry Android SDK, then their versions are not considered. However, if the versions are higher than those bundled with the Sentry Gradle plugin, Gradle will choose them instead. -To test unreleased versions of the Sentry Android Gradle Plugin, see Pre-Release Versions. +To test unreleased versions of the Sentry Android Gradle Plugin, see Pre-Release Versions. diff --git a/docs/platforms/android/configuration/options.mdx b/docs/platforms/android/configuration/options.mdx index d14861fc2c9ca..a02ef366c1e98 100644 --- a/docs/platforms/android/configuration/options.mdx +++ b/docs/platforms/android/configuration/options.mdx @@ -355,7 +355,7 @@ UI Profiling requires SDK versions `8.7.0` or higher. Lower versions can use the -On devices running Android 15 (API level 35) or higher, UI Profiling always uses the Android ProfilingManager to capture Perfetto traces. On older devices, this option controls whether the SDK falls back to the legacy `tracer` backend. When `true` (the default), the legacy profiler runs on devices below API level 35. Set it to `false` to disable profiling on those devices entirely. +On devices running Android 15 (API level 35) or higher, UI Profiling always uses the Android ProfilingManager to capture Perfetto traces. On older devices, this option controls whether the SDK falls back to the legacy `tracer` backend. When `true` (the default), the legacy profiler runs on devices below API level 35. Set it to `false` to disable profiling on those devices entirely. Setting this option to `false` also disables transaction-based profiling (`profilesSampleRate`/`profilesSampler`) on all devices, since transaction-based profiling always relies on the legacy profiler and is not supported by the ProfilingManager (Perfetto) backend. @@ -380,7 +380,7 @@ Whether the UI profiling lifecycle is controlled manually or based on the trace -A boolean value that determines whether the app start process will be profiled. When true, the startup process, including ContentProviders, Application, and first Activity creation, will be profiled. Note that must be defined. App start profiling is only supported by the legacy profiler, which runs on devices below Android 15 (API level 35). It has no effect with the ProfilingManager (Perfetto) backend used on API level 35 and higher. +A boolean value that determines whether the app start process will be profiled. When true, the startup process, including ContentProviders, Application, and first Activity creation, will be profiled. Note that must be defined. App start profiling is only supported by the legacy profiler, which runs on devices below Android 15 (API level 35). It has no effect with the ProfilingManager (Perfetto) backend used on API level 35 and higher. - If profileLifecycle is set to `manual`: profiling is started automatically on startup and stopProfiler must be called manually whenever the app startup is deemed to be completed - If profileLifecycle is set to `trace`: profiling is started automatically on startup, and will automatically be stopped when the root span that is associated with app startup ends diff --git a/docs/platforms/android/configuration/webview.mdx b/docs/platforms/android/configuration/webview.mdx index 580fca3fdf9f8..f8765dd113ea5 100644 --- a/docs/platforms/android/configuration/webview.mdx +++ b/docs/platforms/android/configuration/webview.mdx @@ -15,7 +15,7 @@ To monitor errors and performance in web views choose the appropriate Sentry Jav - [Sentry React SDK](/platforms/javascript/guides/react/) (if the web project uses React) - [Sentry Angular SDK](/platforms/javascript/guides/angular/) (if the web project uses Angular) -- [Other Sentry JavaScript SDKs](/platforms/javascript) +- [Other Sentry JavaScript SDKs](/platforms/javascript/) ## Notes diff --git a/docs/platforms/android/data-management/debug-files/source-context/index.mdx b/docs/platforms/android/data-management/debug-files/source-context/index.mdx index 975b2277cf832..d643e4e01ef82 100644 --- a/docs/platforms/android/data-management/debug-files/source-context/index.mdx +++ b/docs/platforms/android/data-management/debug-files/source-context/index.mdx @@ -25,7 +25,7 @@ See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more inform -For Android, follow the instructions in the [Android Source Context](/platforms/android/enhance-errors/source-context) guide. +For Android, follow the instructions in the [Android Source Context](/platforms/android/enhance-errors/source-context/) guide. diff --git a/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx b/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx index 314553639fb0d..4a46edc2c537b 100644 --- a/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx +++ b/docs/platforms/android/enhance-errors/kotlin-compiler-plugin.mdx @@ -6,7 +6,7 @@ description: "Learn about using the Sentry Kotlin Compiler Plugin." The [Sentry Kotlin Compiler Plugin](https://github.com/getsentry/sentry-android-gradle-plugin) is an addition to the Sentry Android Gradle plugin and offers improvements to existing SDK features. As of now the main focus of the plugin is to improve apps which utilize Jetpack Compose by automatically tagging `@Composable` functions. -- View Hierarchy +- View Hierarchy - User Interaction Tracing @@ -67,4 +67,4 @@ implementation("io.sentry:sentry-compose-android:{{@inject packages.version('sen ### Configuration -As of now no additional steps are necessary. Checkout the docs for View Hierarchy and User Interaction Tracing to see which features the Sentry Kotlin Compiler Plugin improves. +As of now no additional steps are necessary. Checkout the docs for View Hierarchy and User Interaction Tracing to see which features the Sentry Kotlin Compiler Plugin improves. diff --git a/docs/platforms/android/enhance-errors/proguard.mdx b/docs/platforms/android/enhance-errors/proguard.mdx index 031e2aff24de2..73ee4a95cc07f 100644 --- a/docs/platforms/android/enhance-errors/proguard.mdx +++ b/docs/platforms/android/enhance-errors/proguard.mdx @@ -8,7 +8,7 @@ If you want to see de-obfuscated stack traces, you'll need to use [ProGuard](htt It works the same either way. A (random) UUID will be or has to be generated and placed into the `AndroidManifest.xml`. The same UUID has to be used to upload the mapping file(s). In case a crash happens in the app, the Sentry Android SDK will send the UUID along with the stack trace to the Sentry server instance. Sentry will then de-obfuscate the stack trace by searching for the associated mapping file with the same UUID. -If [Source Context](/platforms/android/enhance-errors/source-context) is enabled, Sentry can show snippets of code (_source context_) around the location of stack frames, which helps to quickly pinpoint problematic code. +If [Source Context](/platforms/android/enhance-errors/source-context/) is enabled, Sentry can show snippets of code (_source context_) around the location of stack frames, which helps to quickly pinpoint problematic code. Support for Guardsquare's ProGuard and [DexGuard](https://www.guardsquare.com/dexguard) was added in version 3.0.0 of the [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/). diff --git a/docs/platforms/android/enriching-events/breadcrumbs/index.mdx b/docs/platforms/android/enriching-events/breadcrumbs/index.mdx index 85c00b11839fe..7fffc686e8cc1 100644 --- a/docs/platforms/android/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/android/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/android/enriching-events/viewhierarchy/index.mdx b/docs/platforms/android/enriching-events/viewhierarchy/index.mdx index 8465bd6f30480..17680240669bb 100644 --- a/docs/platforms/android/enriching-events/viewhierarchy/index.mdx +++ b/docs/platforms/android/enriching-events/viewhierarchy/index.mdx @@ -107,7 +107,7 @@ plugins { ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/android/features/index.mdx b/docs/platforms/android/features/index.mdx index 252de23cbd1aa..5aca528671d88 100644 --- a/docs/platforms/android/features/index.mdx +++ b/docs/platforms/android/features/index.mdx @@ -12,14 +12,14 @@ Sentry's Android SDK enables automatic reporting of errors and exceptions, and i We released Performance-V2, a set of experimental features to give you more details about app start performance and frame delay on a span level. -We released Source Context, which shows snippets of code around the location of stack frames. +We released Source Context, which shows snippets of code around the location of stack frames. Let us know if you have feedback by filing a GitHub issue. - Native Development Kit (NDK), the set of tools that allows you to use C and C++ with Android. -- Events enriched with device data. +- Events enriched with device data. - Offline caching. (If a device is offline, we'll send a report once the application has been restarted.) - Automatic breadcrumbs for: - Android activity lifecycle events. @@ -27,29 +27,29 @@ Let us know if you have feedback by filing a fragment lifecycle events. - - OkHttp requests. - - Apollo requests. - - Timber logs. - - Navigation destination changes. + - Android fragment lifecycle events. + - OkHttp requests. + - Apollo requests. + - Timber logs. + - Navigation destination changes. - Release health, tracking crash-free users and sessions. -- Attachments that can enrich your event by storing additional files, such as config or log files. -- User Feedback, providing the ability to collect user information when an event occurs. +- Attachments that can enrich your event by storing additional files, such as config or log files. +- User Feedback, providing the ability to collect user information when an event occurs. - Tracing that can track: - Android activity transactions. - User interaction transactions such as: view click, scroll, swipe, and so on. - - Navigation transactions. - - Android fragment spans. + - Navigation transactions. + - Android fragment spans. - Cold and warm app starts. - Slow and frozen frames. - - OkHttp request spans. - - SQLite query spans. - - File I/O spans. - - Apollo request spans. - - Distributed tracing through OkHttp and Apollo integrations. -- Application Not Responding (ANR), reported if the application is blocked for more than five seconds. + - OkHttp request spans. + - SQLite query spans. + - File I/O spans. + - Apollo request spans. + - Distributed tracing through OkHttp and Apollo integrations. +- Application Not Responding (ANR), reported if the application is blocked for more than five seconds. - HTTP Client Errors. -- Screenshot attachments for errors. -- View Hierarchy attachments for errors. +- Screenshot attachments for errors. +- View Hierarchy attachments for errors. - Code samples provided in both Kotlin and Java (since the Android SDK uses both languages). - A sample application for our Android users. diff --git a/docs/platforms/android/index.mdx b/docs/platforms/android/index.mdx index ba256c1cd18db..b36b0648a3f4e 100644 --- a/docs/platforms/android/index.mdx +++ b/docs/platforms/android/index.mdx @@ -41,7 +41,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori - On Android 15 (API level 35) and higher, profiling uses the Android ProfilingManager to capture Perfetto traces. On older devices, the SDK automatically falls back to the legacy profiler. + On Android 15 (API level 35) and higher, profiling uses the Android ProfilingManager to capture Perfetto traces. On older devices, the SDK automatically falls back to the legacy profiler. @@ -183,7 +183,7 @@ class MyActivity : AppCompatActivity() { ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn about the features of Sentry's Android SDK -- Learn how to enhance stack traces of your Sentry errors -- Enrich events with additional context to make debugging simpler -- Diagnose ANRs with profiling and automatic fingerprinting +- Learn about the features of Sentry's Android SDK +- Learn how to enhance stack traces of your Sentry errors +- Enrich events with additional context to make debugging simpler +- Diagnose ANRs with profiling and automatic fingerprinting diff --git a/docs/platforms/android/integrations/apollo3/index.mdx b/docs/platforms/android/integrations/apollo3/index.mdx index f349f0f22fd9d..778244b126f20 100644 --- a/docs/platforms/android/integrations/apollo3/index.mdx +++ b/docs/platforms/android/integrations/apollo3/index.mdx @@ -166,7 +166,7 @@ By default, error events won't contain `Headers` or `Cookies`, but you can chang ``` -Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. +Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay/) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. Alternatively, you can customize the event and scrub the data yourself. diff --git a/docs/platforms/android/integrations/apollo4/index.mdx b/docs/platforms/android/integrations/apollo4/index.mdx index f18825566d98a..df8f62639429d 100644 --- a/docs/platforms/android/integrations/apollo4/index.mdx +++ b/docs/platforms/android/integrations/apollo4/index.mdx @@ -168,7 +168,7 @@ Sentry.init { options -> ``` -Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. +Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay/) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. Alternatively, you can customize the event and scrub the data yourself. diff --git a/docs/platforms/android/manual-setup/index.mdx b/docs/platforms/android/manual-setup/index.mdx index 8f623846a1bd3..a2de21f5ff223 100644 --- a/docs/platforms/android/manual-setup/index.mdx +++ b/docs/platforms/android/manual-setup/index.mdx @@ -44,7 +44,7 @@ dependencies { -If you're using multiple Sentry dependencies, you can add a [bill of materials](/platforms/android/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you're using multiple Sentry dependencies, you can add a [bill of materials](/platforms/android/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/docs/platforms/android/overhead/index.mdx b/docs/platforms/android/overhead/index.mdx index 1438040c3d089..419490d5cb0bd 100644 --- a/docs/platforms/android/overhead/index.mdx +++ b/docs/platforms/android/overhead/index.mdx @@ -23,13 +23,13 @@ The SDK also provides methods to manually capture events: Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. +If you activate these features, the SDK will capture Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. -If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. The SDK provides callbacks to fine-tune when to capture Screenshots and View Hierarchy, which can also be used to reduce performance impact in scenarios where you don't need screenshots or view hierarchies. +If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. The SDK provides callbacks to fine-tune when to capture Screenshots and View Hierarchy, which can also be used to reduce performance impact in scenarios where you don't need screenshots or view hierarchies. ## Breadcrumbs -Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. +Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. Capturing excessive numbers of breadcrumbs (for example, creating breadcrumbs for all log messages) can cause significant performance overhead. To mitigate this, review and adapt your app's usage of breadcrumbs. For example, increase the min-level of log messages that create breadcrumbs from `warn` to `error`. diff --git a/docs/platforms/android/profiling/index.mdx b/docs/platforms/android/profiling/index.mdx index d470fe1a2886c..bea7a494629f4 100644 --- a/docs/platforms/android/profiling/index.mdx +++ b/docs/platforms/android/profiling/index.mdx @@ -12,14 +12,14 @@ sidebar_section: features Starting with SDK version `8.51.0`, Sentry's Android UI Profiling is built on top of the Android ProfilingManager APIs, available on Android 15 (API level 35), which capture stack samples as Perfetto traces. This is the recommended way to profile your Android app. - On devices running below Android 15, the SDK automatically falls back to the legacy profiler, which samples threads using the Android runtime's `tracer`. That implementation, along with the transaction-based profiler, is now considered legacy. See Legacy Profiling for details, including how to disable it. + On devices running below Android 15, the SDK automatically falls back to the legacy profiler, which samples threads using the Android runtime's `tracer`. That implementation, along with the transaction-based profiler, is now considered legacy. See Legacy Profiling for details, including how to disable it. ## Prerequisites UI Profiling is available starting in SDK version `8.7.0`. On **Android 15 (API level 35) or higher**, it uses the ProfilingManager (Perfetto) backend, available starting in SDK version `8.51.0`. -On devices running below Android 15, the SDK automatically falls back to the legacy profiler. You can turn this fallback off, and disable profiling on those devices entirely, with the `enableLegacyProfiling` option. +On devices running below Android 15, the SDK automatically falls back to the legacy profiler. You can turn this fallback off, and disable profiling on those devices entirely, with the `enableLegacyProfiling` option. ## Enabling UI Profiling @@ -171,8 +171,8 @@ class MyApplication : Application() { On Android 15 (API level 35) and higher, UI Profiling relies on the Android ProfilingManager, so the following limitations apply: -- **Older devices use the legacy profiler.** On devices below Android 15, the SDK automatically falls back to Legacy Profiling, which has different characteristics. You can disable this fallback with the `enableLegacyProfiling` option. -- **App start profiling is not supported.** The `startProfilerOnAppStart` option has no effect with the ProfilingManager (Perfetto) backend. App start profiling is only supported by the legacy profiler used on devices below Android 15. To learn more, see Legacy Profiling. +- **Older devices use the legacy profiler.** On devices below Android 15, the SDK automatically falls back to Legacy Profiling, which has different characteristics. You can disable this fallback with the `enableLegacyProfiling` option. +- **App start profiling is not supported.** The `startProfilerOnAppStart` option has no effect with the ProfilingManager (Perfetto) backend. App start profiling is only supported by the legacy profiler used on devices below Android 15. To learn more, see Legacy Profiling. - **Profiling requests are rate limited and not guaranteed to be fulfilled.** Apart from the SDK sampling rate, the Android Framework also restricts profiling, so not every request results in a profile. These limits are outside the SDK's control. To learn more, see the Android ProfilingManager documentation. diff --git a/docs/platforms/android/profiling/legacy/index.mdx b/docs/platforms/android/profiling/legacy/index.mdx index fb5ac74a994c6..e35ca7108db15 100644 --- a/docs/platforms/android/profiling/legacy/index.mdx +++ b/docs/platforms/android/profiling/legacy/index.mdx @@ -17,7 +17,7 @@ There are two legacy profiling implementations: Legacy UI Profiling and transaction-based profiling use the Android runtime's `tracer` under the hood to sample threads. There are known issues that this - `tracer` can cause crashes in certain circumstances. See this troubleshooting entry for more information. The ProfilingManager (Perfetto) based UI Profiling is not affected by these issues. + `tracer` can cause crashes in certain circumstances. See this troubleshooting entry for more information. The ProfilingManager (Perfetto) based UI Profiling is not affected by these issues. ## Legacy UI Profiling diff --git a/docs/platforms/android/profiling/troubleshooting/index.mdx b/docs/platforms/android/profiling/troubleshooting/index.mdx index c41b20ef1d8f8..3173ff8787423 100644 --- a/docs/platforms/android/profiling/troubleshooting/index.mdx +++ b/docs/platforms/android/profiling/troubleshooting/index.mdx @@ -5,12 +5,12 @@ sidebar_order: 9000 --- - The crash-related issues below only affect Legacy Profiling, which uses the Android runtime's `tracer`. The recommended ProfilingManager (Perfetto) based UI Profiling is not affected. + The crash-related issues below only affect Legacy Profiling, which uses the Android runtime's `tracer`. The recommended ProfilingManager (Perfetto) based UI Profiling is not affected. ## I see an elevated number of crashes in the Android Runtime when profiling is activated -Legacy Profiling uses the Android runtime's `tracer` under the hood to sample threads. There are known issues that this `tracer` can cause crashes in certain circumstances. The recommended ProfilingManager (Perfetto) based UI Profiling avoids these issues. Read on for more information, and subscribe to this GitHub issue for updates. +Legacy Profiling uses the Android runtime's `tracer` under the hood to sample threads. There are known issues that this `tracer` can cause crashes in certain circumstances. The recommended ProfilingManager (Perfetto) based UI Profiling avoids these issues. Read on for more information, and subscribe to this GitHub issue for updates. As of October 2024, two of these crashes (see 1, 2) have been acknowledged and fixed by Google. The fixes are being rolled out to affected devices by Google, but the crashing behavior might still be present on devices that didn't receive the fix yet. @@ -22,5 +22,5 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. diff --git a/docs/platforms/android/session-replay/troubleshooting.mdx b/docs/platforms/android/session-replay/troubleshooting.mdx index 0ae04df5f5c80..c0a4e0d3e8979 100644 --- a/docs/platforms/android/session-replay/troubleshooting.mdx +++ b/docs/platforms/android/session-replay/troubleshooting.mdx @@ -26,7 +26,7 @@ Recording only happens on Android 8 (API level 26) or newer. For devices running -An issue may be missing a replay because the user's device was [offline](/product/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video. +An issue may be missing a replay because the user's device was [offline](/product/session-replay/mobile/#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video. diff --git a/docs/platforms/android/size-analysis/index.mdx b/docs/platforms/android/size-analysis/index.mdx index 527960f6b9721..3e244ae82f582 100644 --- a/docs/platforms/android/size-analysis/index.mdx +++ b/docs/platforms/android/size-analysis/index.mdx @@ -7,7 +7,7 @@ description: Upload Android builds to Sentry for Size Analysis. new: true --- -[Size Analysis](/product/size-analysis) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. +[Size Analysis](/product/size-analysis/) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. ## Getting Started diff --git a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx index 11a6fa2623fd9..a775e10769d27 100644 --- a/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/android/tracing/instrumentation/automatic-instrumentation.mdx @@ -157,7 +157,7 @@ You can opt out of Activity Instrumentation and App Start Instrumentation using ``` -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). ### Standalone App Start Tracing @@ -312,7 +312,7 @@ Supported on Android OS version `7.0` and above. Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are _slow frames_ and _frozen frames_. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the [Activity](/platforms/android/tracing/instrumentation/automatic-instrumentation/#activity-instrumentation) transactions. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). ### Trace Propagation Targets diff --git a/docs/platforms/apple/common/configuration/app-hangs.mdx b/docs/platforms/apple/common/configuration/app-hangs.mdx index 312703051eeaa..fd6b1a1047809 100644 --- a/docs/platforms/apple/common/configuration/app-hangs.mdx +++ b/docs/platforms/apple/common/configuration/app-hangs.mdx @@ -134,7 +134,7 @@ SentrySDK.start { options in ### Pause and Resume App Hang Tracking Starting with version 8.30.0, you can pause and resume app hang tracking at runtime with `SentrySDK.pauseAppHangTracking()` and `SentrySDK.resumeAppHangTracking()`. -These methods don't stop the MetricKit integration from reporting [MXHangDiagnostic](https://developer.apple.com/documentation/metrickit/mxhangdiagnostic). +These methods don't stop the MetricKit integration from reporting [MXHangDiagnostic](https://developer.apple.com/documentation/metrickit/mxhangdiagnostic). ```swift {tabTitle:Swift} import Sentry diff --git a/docs/platforms/apple/common/configuration/webview.mdx b/docs/platforms/apple/common/configuration/webview.mdx index d4a6a7c240a0a..0c64adf2b4272 100644 --- a/docs/platforms/apple/common/configuration/webview.mdx +++ b/docs/platforms/apple/common/configuration/webview.mdx @@ -15,7 +15,7 @@ To monitor errors and performance in web views choose the appropriate Sentry Jav - [Sentry React SDK](/platforms/javascript/guides/react/) (if the web project uses React) - [Sentry Angular SDK](/platforms/javascript/guides/angular/) (if the web project uses Angular) -- [Other Sentry JavaScript SDKs](/platforms/javascript) +- [Other Sentry JavaScript SDKs](/platforms/javascript/) ## Notes diff --git a/docs/platforms/apple/common/data-management/data-collected.mdx b/docs/platforms/apple/common/data-management/data-collected.mdx index 436ffba2d3ae1..8e70a69b52ce3 100644 --- a/docs/platforms/apple/common/data-management/data-collected.mdx +++ b/docs/platforms/apple/common/data-management/data-collected.mdx @@ -18,7 +18,7 @@ The category types and amount of data collected vary, depending on the integrati ## HTTP Headers -The HTTP Client Errors, which are enabled by default, send the HTTP headers of the failed request and response to Sentry. The SDK uses a [denylist](https://github.com/getsentry/sentry-cocoa/blob/main/Sources/Swift/Core/Tools/HTTPHeaderSanitizer.swift) to filter out any headers that contain sensitive data. +The HTTP Client Errors, which are enabled by default, send the HTTP headers of the failed request and response to Sentry. The SDK uses a [denylist](https://github.com/getsentry/sentry-cocoa/blob/main/Sources/Swift/Core/Tools/HTTPHeaderSanitizer.swift) to filter out any headers that contain sensitive data. ## Users' IP Addresses @@ -32,7 +32,7 @@ When the Apple SDK sends URLs to Sentry it always sends a sanitized URL which me Network breadcrumbs and HTTP Client Errors, both enabled by default, send a sanitized URL for outgoing HTTP requests. You can disable network breadcrumbs by setting the option `enableNetworkBreadcrumbs` to `false` and you can disable HTTP Client Errors by setting the option `enableCaptureFailedRequests` to `false`. -When you enable tracing, which is disabled per default, network tracing sends a sanitized URL for outgoing HTTP requests. +When you enable tracing, which is disabled per default, network tracing sends a sanitized URL for outgoing HTTP requests. ## Source Context @@ -46,17 +46,17 @@ When you enable tracing, which is disabled per default, the Apple SDK tracing, which is disabled per default, the Apple SDK instruments Core Data queries and sends the Core Data queries to Sentry. Neither the full SQL query (`SELECT 'User' WHERE name == 'username'`), nor the values of its parameters will ever be sent. A parameterized version of the query (`SELECT 'User' WHERE name == %@`) is sent instead. +When you enable tracing, which is disabled per default, the Apple SDK instruments Core Data queries and sends the Core Data queries to Sentry. Neither the full SQL query (`SELECT 'User' WHERE name == 'username'`), nor the values of its parameters will ever be sent. A parameterized version of the query (`SELECT 'User' WHERE name == %@`) is sent instead. ## Screenshots -The screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. +The screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. ## View Hierarchy -The view hierarchy feature is disabled per default, but when enabled the view hierarchy may contain PII data when using the `accessibilityIdentifier` property with personal information. +The view hierarchy feature is disabled per default, but when enabled the view hierarchy may contain PII data when using the `accessibilityIdentifier` property with personal information. diff --git a/docs/platforms/apple/common/data-management/debug-files/source-context/index.mdx b/docs/platforms/apple/common/data-management/debug-files/source-context/index.mdx index d3bea628c04bf..73d6d824710c6 100644 --- a/docs/platforms/apple/common/data-management/debug-files/source-context/index.mdx +++ b/docs/platforms/apple/common/data-management/debug-files/source-context/index.mdx @@ -24,7 +24,7 @@ needs to be uploaded alongside the debug information files. The recommended way to do this is by using `sentry-cli`. See [Creating Source Bundles](/cli/dif/#creating-source-bundles) for more information. -To get source context for your Apple project, follow the instructions in the [Uploading Debug Symbols](/platforms/apple/sourcecontext) guide. +To get source context for your Apple project, follow the instructions in the [Uploading Debug Symbols](/platforms/apple/sourcecontext/) guide. After they've been uploaded you can review and manage source bundles the same as any other debug information file. See [Managing Debug Information Files](../#managing-debug-information-files). diff --git a/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx index ea476947f3bb9..c43fc9dbb60bd 100644 --- a/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/apple/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx b/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx index 6220882010806..ac7107d2b85ef 100644 --- a/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx +++ b/docs/platforms/apple/common/enriching-events/viewhierarchy/index.mdx @@ -70,7 +70,7 @@ SentrySDK.start { options in ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/apple/common/features/index.mdx b/docs/platforms/apple/common/features/index.mdx index 014d907bd8743..49fb86c48228e 100644 --- a/docs/platforms/apple/common/features/index.mdx +++ b/docs/platforms/apple/common/features/index.mdx @@ -28,11 +28,11 @@ All features listed below are **enabled by default** unless otherwise noted. Som - App Hang Detection - On iOS and tvOS: Differentiates between fully-blocking and non-fully-blocking app hangs, and measures app hang duration (AppHangsV2, enabled by default since SDK version 9.0.0) - Watchdog Terminations (only available on iOS, tvOS, and visionOS) -- HTTP Client Errors +- HTTP Client Errors ## Performance Monitoring -- Automatic Performance Tracking for: +- Automatic Performance Tracking for: - Rendering of UIViewControllers - Performance of HTTP requests - Distributed tracing @@ -45,7 +45,7 @@ All features listed below are **enabled by default** unless otherwise noted. Som - User Interaction transactions for UI clicks - Frame rate tracking for UI performance (only available on iOS, tvOS, and visionOS) - App start time measurement for cold and warm starts (only available on iOS, tvOS, and visionOS) -- Profiling (requires configuration, only available on iOS and macOS) +- Profiling (requires configuration, only available on iOS and macOS) - Transaction-based profiling (deprecated) - Continuous profiling - UI Profiling (recommended) @@ -56,28 +56,28 @@ All features listed below are **enabled by default** unless otherwise noted. Som - Release health tracks crash-free users and sessions - Session tracking automatically tracks user sessions for release health metrics -- Session Replay (only available on iOS 16+ and tvOS 16+) +- Session Replay (only available on iOS 16+ and tvOS 16+) - Requires SDK version 8.31.1 or later - tvOS is not officially supported ## Event Enrichment -- Events enriched with device data, environment information, and app state +- Events enriched with device data, environment information, and app state - Breadcrumbs are automatically captured for: - Application lifecycle events (`didBecomeActive`, `didEnterBackground`, `viewDidAppear`) - Touch events - System events (battery level or state changed, memory warnings, device orientation changed, keyboard did show and did hide, screenshot taken, time zone changed or significant time change) - Outgoing HTTP requests -- Attachments enrich your event by storing additional files, such as config or log files -- Source Context shows snippets of code around the location of stack frames -- Feature Flags track feature flag evaluations on error events and active spans +- Attachments enrich your event by storing additional files, such as config or log files +- Source Context shows snippets of code around the location of stack frames +- Feature Flags track feature flag evaluations on error events and active spans - View Hierarchy and Screenshot attachments for errors (only available on iOS and tvOS) -- User Feedback provides the ability to collect user information when an event occurs (User Feedback UI only available on iOS 13+) +- User Feedback provides the ability to collect user information when an event occurs (User Feedback UI only available on iOS 13+) ## Platform-Specific Features -- MetricKit integration (only available on iOS 15+ and macOS 12+, requires enabling `enableMetricKit` option) -- Logs capturing (requires `enableLogs` option, only available on iOS, tvOS, visionOS, and macOS) +- MetricKit integration (only available on iOS 15+ and macOS 12+, requires enabling `enableMetricKit` option) +- Logs capturing (requires `enableLogs` option, only available on iOS, tvOS, visionOS, and macOS) ## Data Management @@ -87,8 +87,8 @@ All features listed below are **enabled by default** unless otherwise noted. Som ## Platform-Specific Documentation For platform-specific feature details and limitations, see: -- iOS Features -- macOS Features -- tvOS Features -- watchOS Features -- visionOS Features +- iOS Features +- macOS Features +- tvOS Features +- watchOS Features +- visionOS Features diff --git a/docs/platforms/apple/common/overhead/index.mdx b/docs/platforms/apple/common/overhead/index.mdx index 591d2cede49c0..f3d9c9cae20ee 100644 --- a/docs/platforms/apple/common/overhead/index.mdx +++ b/docs/platforms/apple/common/overhead/index.mdx @@ -25,15 +25,15 @@ The SDK also provides methods to manually capture events: Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. +If you activate these features, the SDK will capture Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. -If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. The SDK provides callbacks to fine-tune when to capture Screenshots and View Hierarchy, which can also be used to reduce performance impact in scenarios where you don't need screenshots or view hierarchies. +If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. The SDK provides callbacks to fine-tune when to capture Screenshots and View Hierarchy, which can also be used to reduce performance impact in scenarios where you don't need screenshots or view hierarchies. ## Breadcrumbs -Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. +Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. Capturing excessive numbers of breadcrumbs (for example, creating breadcrumbs for all log messages) can cause significant performance overhead. To mitigate this, review and adapt your app's usage of breadcrumbs. For example, increase the min-level of log messages that create breadcrumbs from `warn` to `error`. diff --git a/docs/platforms/apple/common/profiling/troubleshooting/index.mdx b/docs/platforms/apple/common/profiling/troubleshooting/index.mdx index ee87700b83367..0054c323cebf1 100644 --- a/docs/platforms/apple/common/profiling/troubleshooting/index.mdx +++ b/docs/platforms/apple/common/profiling/troubleshooting/index.mdx @@ -8,5 +8,5 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. diff --git a/docs/platforms/apple/common/session-replay/index.mdx b/docs/platforms/apple/common/session-replay/index.mdx index 090717927ef89..cbe9bda26eeb1 100644 --- a/docs/platforms/apple/common/session-replay/index.mdx +++ b/docs/platforms/apple/common/session-replay/index.mdx @@ -84,7 +84,7 @@ Sampling begins as soon as a session starts. `sessionSampleRate` is evaluated fi ## Privacy The SDK is recording and aggressively masking all text, images, PDF viewers, and webviews by default. If your app has any sensitive data, you should only turn the default masking off after explicitly masking out the sensitive data, using the APIs described below. -If you want to manually mask parts of your app's data, read our guide on [custom masking](/platforms/apple/guides/ios/session-replay/customredact). +If you want to manually mask parts of your app's data, read our guide on [custom masking](/platforms/apple/guides/ios/session-replay/customredact/). diff --git a/docs/platforms/apple/common/session-replay/troubleshooting.mdx b/docs/platforms/apple/common/session-replay/troubleshooting.mdx index b6de8679a3856..c48b043050523 100644 --- a/docs/platforms/apple/common/session-replay/troubleshooting.mdx +++ b/docs/platforms/apple/common/session-replay/troubleshooting.mdx @@ -83,7 +83,7 @@ Session Replay recording happens even on the lowest version supported by the Sen -An issue may be missing a replay because the user's device was [offline](/product/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video. +An issue may be missing a replay because the user's device was [offline](/product/session-replay/mobile/#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video. diff --git a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx index 92f1d9932bc32..2e62da2ae94bd 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -113,7 +113,7 @@ SentrySDK.start { options in }]; ``` -You can deactivate tracing for specific UIViewControllers by configuring `swizzleClassNameExcludes`: +You can deactivate tracing for specific UIViewControllers by configuring `swizzleClassNameExcludes`: ```swift {tabTitle:Swift} import Sentry @@ -208,7 +208,7 @@ The Cocoa SDK creates the following app start spans: ![App Start Transaction](./img/app-start-transaction.png) -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). ### Prewarmed App Start Tracing @@ -517,7 +517,7 @@ The detail view of the transaction displays the slow, frozen, and total frames: ![Slow and Frozen Frames](./img/slow-frozen-frames.png) -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). ## Network Tracking diff --git a/docs/platforms/apple/common/troubleshooting/index.mdx b/docs/platforms/apple/common/troubleshooting/index.mdx index 1e872e03e4f5a..2b0827366e7bc 100644 --- a/docs/platforms/apple/common/troubleshooting/index.mdx +++ b/docs/platforms/apple/common/troubleshooting/index.mdx @@ -7,7 +7,7 @@ sidebar_section: configuration ## "Missing API declaration" after App Store review -Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/apple/data-management/apple-privacy-manifest) guide. +Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/apple/data-management/apple-privacy-manifest/) guide. ## Wrong App Start Data @@ -244,4 +244,4 @@ The workaround is to remove `arm64e` from the target's **Architectures** build s ## Troubleshooting Session Replay -See [Session Replay - Troubleshooting](/platforms/apple/guides/ios/session-replay/troubleshooting) for more information. +See [Session Replay - Troubleshooting](/platforms/apple/guides/ios/session-replay/troubleshooting/) for more information. diff --git a/docs/platforms/apple/guides/ios/build-distribution/index.mdx b/docs/platforms/apple/guides/ios/build-distribution/index.mdx index 04df988cfebb9..2e1fb61ef6775 100644 --- a/docs/platforms/apple/guides/ios/build-distribution/index.mdx +++ b/docs/platforms/apple/guides/ios/build-distribution/index.mdx @@ -6,7 +6,7 @@ description: Upload iOS builds to Sentry for distribution to internal teams and beta: true --- -[Build Distribution](/product/build-distribution) helps you securely distribute iOS builds to your internal teams and beta testers. +[Build Distribution](/product/build-distribution/) helps you securely distribute iOS builds to your internal teams and beta testers. Streamline your distribution workflow with automated uploads from CI. ## Getting Started diff --git a/docs/platforms/apple/guides/ios/features/index.mdx b/docs/platforms/apple/guides/ios/features/index.mdx index 4d8c7a38e63e1..5f00929cd06de 100644 --- a/docs/platforms/apple/guides/ios/features/index.mdx +++ b/docs/platforms/apple/guides/ios/features/index.mdx @@ -12,7 +12,7 @@ The SDK builds a crash report that persists to disk. On iOS, crash reports are s -For a complete list of all available features, see the main Features page. This page highlights iOS-specific features and capabilities. +For a complete list of all available features, see the main Features page. This page highlights iOS-specific features and capabilities. ## Error Detection Features @@ -21,24 +21,24 @@ iOS supports comprehensive error detection: - Crash detection for all types of crashes and exceptions - App hang detection for when the app becomes unresponsive - Watchdog termination tracking for abnormal process terminations -- HTTP client errors automatically captured +- HTTP client errors automatically captured ## Event Enrichment -- Events enriched with device data, environment information, and app state +- Events enriched with device data, environment information, and app state - Breadcrumbs are automatically captured for app lifecycle, touch events, system events, and network requests -- Attachments for storing additional files with events -- Source Context shows code snippets around stack frames -- Screenshot capture when errors occur -- View Hierarchy capture when errors occur +- Attachments for storing additional files with events +- Source Context shows code snippets around stack frames +- Screenshot capture when errors occur +- View Hierarchy capture when errors occur ## Logs -Logs capturing is available and requires the `enableLogs` option to be enabled. +Logs capturing is available and requires the `enableLogs` option to be enabled. ## Performance Features Available on iOS -iOS supports all performance monitoring features: +iOS supports all performance monitoring features: - App start tracking for cold and warm app start times - Frame rate tracking for UI rendering performance and slow/frozen frame identification @@ -49,7 +49,7 @@ iOS supports all performance monitor ## Session Replay -Session Replay records user sessions for visual debugging, helping you understand what happened before, during, and after an error. +Session Replay records user sessions for visual debugging, helping you understand what happened before, during, and after an error. - Available on iOS 16+ - Requires SDK version 8.31.1 or later @@ -57,14 +57,14 @@ iOS supports all performance monitor ## User Feedback UI -User Feedback provides a built-in UI to collect user information when an error occurs. You must call the User Feedback API to display the UI. +User Feedback provides a built-in UI to collect user information when an error occurs. You must call the User Feedback API to display the UI. - Requires calling the User Feedback API to show the UI -For configuration options and detailed documentation, see the Configuration section. +For configuration options and detailed documentation, see the Configuration section. ## Other Features -- MetricKit integration available on iOS 15+ (requires `enableMetricKit` option) +- MetricKit integration available on iOS 15+ (requires `enableMetricKit` option) - Release health tracks crash-free users and sessions - Swift Async/Await support for automatically stitching together stack traces of Swift concurrency code diff --git a/docs/platforms/apple/guides/ios/manual-setup.mdx b/docs/platforms/apple/guides/ios/manual-setup.mdx index 5a42410fa36ae..197dc4a4af99f 100644 --- a/docs/platforms/apple/guides/ios/manual-setup.mdx +++ b/docs/platforms/apple/guides/ios/manual-setup.mdx @@ -16,7 +16,7 @@ We recommend installing the SDK with SPM, but we also support alternate [install https://github.com/getsentry/sentry-cocoa.git ``` -The Package has a few products you can depend on, but the recommended one is `Sentry`. For more details see the full docs on using [Swift Package Manager](/platforms/apple/guides/ios/install/swift-package-manager). +The Package has a few products you can depend on, but the recommended one is `Sentry`. For more details see the full docs on using [Swift Package Manager](/platforms/apple/guides/ios/install/swift-package-manager/). ## Configuration diff --git a/docs/platforms/apple/guides/ios/size-analysis/index.mdx b/docs/platforms/apple/guides/ios/size-analysis/index.mdx index d1eb4c0872133..e8c021c643637 100644 --- a/docs/platforms/apple/guides/ios/size-analysis/index.mdx +++ b/docs/platforms/apple/guides/ios/size-analysis/index.mdx @@ -6,7 +6,7 @@ description: Upload iOS builds to Sentry for size analysis. new: true --- -[Size Analysis](/product/size-analysis) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. +[Size Analysis](/product/size-analysis/) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. ## Getting Started diff --git a/docs/platforms/apple/guides/macos/features/index.mdx b/docs/platforms/apple/guides/macos/features/index.mdx index 5bc879143d035..7826cd050a11c 100644 --- a/docs/platforms/apple/guides/macos/features/index.mdx +++ b/docs/platforms/apple/guides/macos/features/index.mdx @@ -19,20 +19,20 @@ The SDK builds a crash report that persists to disk. While it attempts to send t -For a complete list of all available features, see the main Features page. This page highlights macOS-specific features and capabilities. +For a complete list of all available features, see the main Features page. This page highlights macOS-specific features and capabilities. ## macOS-Specific Features ### MetricKit Integration -MetricKit integration integrates with Apple's MetricKit framework for system-level performance metrics. +MetricKit integration integrates with Apple's MetricKit framework for system-level performance metrics. - Available on macOS 12+ - Enabled by default (requires `enableMetricKit` option) ### Profiling -Profiling provides code-level performance profiling with multiple modes (requires configuration): +Profiling provides code-level performance profiling with multiple modes (requires configuration): - Transaction-based profiling (deprecated) - Continuous profiling @@ -50,16 +50,16 @@ For a complete list of all available features, see the App hang detection -- HTTP client errors automatically captured +- HTTP client errors automatically captured ## Performance Monitoring -macOS supports comprehensive performance monitoring: +macOS supports comprehensive performance monitoring: - Network request monitoring for HTTP request performance - File I/O performance tracking for file operations - Core Data performance tracking for Core Data query performance -- Distributed tracing across services +- Distributed tracing across services For macOS apps using UIKit (Mac Catalyst), the following features are also available: @@ -75,19 +75,19 @@ For macOS apps using UIKit (Mac Catalyst), the following features are also avail ## Event Enrichment -- Events enriched with device data, environment information, and app state +- Events enriched with device data, environment information, and app state - Breadcrumbs are automatically captured for: - Application lifecycle events (`didBecomeActive`, `didEnterBackground`) - System events (memory warnings, keyboard did show and did hide, screenshot taken) - Outgoing HTTP requests -- Attachments enrich your event by storing additional files, such as config or log files -- Source Context shows snippets of code around the location of stack frames -- User Feedback provides the ability to collect user information when an event occurs (programmatic API only, no UI on macOS) +- Attachments enrich your event by storing additional files, such as config or log files +- Source Context shows snippets of code around the location of stack frames +- User Feedback provides the ability to collect user information when an event occurs (programmatic API only, no UI on macOS) ## Other Features - Swift Async/Await support for automatically stitching together stack traces of Swift concurrency code -- Logs capturing available (requires `enableLogs` option) +- Logs capturing available (requires `enableLogs` option) - Offline caching when a device is unable to connect; we send a report once we receive another event ## macOS Limitations @@ -100,4 +100,4 @@ macOS has some limitations compared to iOS: - View Hierarchy capture not available (except Mac Catalyst) - Watchdog terminations not available -For configuration options and detailed documentation, see the Configuration section. +For configuration options and detailed documentation, see the Configuration section. diff --git a/docs/platforms/apple/guides/tvos/features/index.mdx b/docs/platforms/apple/guides/tvos/features/index.mdx index 8554e9a5c6a7f..658e907c81c20 100644 --- a/docs/platforms/apple/guides/tvos/features/index.mdx +++ b/docs/platforms/apple/guides/tvos/features/index.mdx @@ -12,7 +12,7 @@ The SDK builds a crash report that persists to disk. While it attempts to send t -For a complete list of all available features, see the main Features page. This page highlights tvOS-specific features and limitations. +For a complete list of all available features, see the main Features page. This page highlights tvOS-specific features and limitations. ## tvOS Limitations @@ -26,7 +26,7 @@ tvOS has some limitations compared to iOS: ### Session Replay -Session Replay records user sessions for visual debugging, helping you understand what happened before, during, and after an error. +Session Replay records user sessions for visual debugging, helping you understand what happened before, during, and after an error. @@ -39,7 +39,7 @@ Session Replay works on tvOS 16+, but it is only officially supported on iOS. Wh ### Performance Monitoring -tvOS supports comprehensive performance monitoring: +tvOS supports comprehensive performance monitoring: - App start tracking for cold and warm app start times - Frame rate tracking for UI rendering performance and slow/frozen frame identification @@ -55,16 +55,16 @@ tvOS supports comprehensive error detection: - Crash detection for all types of crashes and exceptions - App hang detection for when the app becomes unresponsive - Watchdog termination tracking for out-of-memory terminations -- HTTP client errors automatically captured +- HTTP client errors automatically captured ### Event Enrichment - View Hierarchy capture when errors occur - Screenshot capture when errors occur - Breadcrumbs automatically captured for app lifecycle, system events, and network requests -- Events enriched with device and environment data -- Attachments for storing additional files with events -- Source Context shows code snippets around stack frames +- Events enriched with device and environment data +- Attachments for storing additional files with events +- Source Context shows code snippets around stack frames ### Other Features @@ -72,7 +72,7 @@ tvOS supports comprehensive error detection: - Release health tracks crash-free users and sessions - Offline caching when a device is unable to connect; we send a report once we receive another event - Swift Async/Await support for automatically stitching together stack traces of Swift concurrency code -- Logs capturing available (requires `enableLogs` option) -- User Feedback via programmatic API (no UI available) +- Logs capturing available (requires `enableLogs` option) +- User Feedback via programmatic API (no UI available) -For configuration options and detailed documentation, see the Configuration section. +For configuration options and detailed documentation, see the Configuration section. diff --git a/docs/platforms/apple/guides/visionos/features/index.mdx b/docs/platforms/apple/guides/visionos/features/index.mdx index b44fad39e693e..56b15ff8767fd 100644 --- a/docs/platforms/apple/guides/visionos/features/index.mdx +++ b/docs/platforms/apple/guides/visionos/features/index.mdx @@ -18,7 +18,7 @@ The SDK builds a crash report that persists to disk. While it attempts to send t -For a complete list of all available features, see the main Features page. This page highlights visionOS-specific features and limitations. +For a complete list of all available features, see the main Features page. This page highlights visionOS-specific features and limitations. ## visionOS Limitations @@ -33,7 +33,7 @@ visionOS has some limitations compared to iOS: ### Performance Monitoring -visionOS supports comprehensive performance monitoring: +visionOS supports comprehensive performance monitoring: - App start tracking for cold and warm app start times - Frame rate tracking for UI rendering performance and slow/frozen frame identification @@ -49,14 +49,14 @@ visionOS supports comprehensive error detection: - Crash detection for all types of crashes and exceptions - App hang detection for when the app becomes unresponsive - Watchdog termination tracking for out-of-memory terminations -- HTTP client errors automatically captured +- HTTP client errors automatically captured ### Event Enrichment - Breadcrumbs automatically captured for app lifecycle, system events, and network requests -- Events enriched with device and environment data -- Attachments for storing additional files with events -- Source Context shows code snippets around stack frames +- Events enriched with device and environment data +- Attachments for storing additional files with events +- Source Context shows code snippets around stack frames - View Hierarchy capture when errors occur - Screenshot capture when errors occur @@ -66,7 +66,7 @@ visionOS supports comprehensive error detection: - Release health tracks crash-free users and sessions - Offline caching when a device is unable to connect; we send a report once we receive another event - Swift Async/Await support for automatically stitching together stack traces of Swift concurrency code -- Logs capturing available (requires `enableLogs` option) -- User Feedback via programmatic API (no UI available) +- Logs capturing available (requires `enableLogs` option) +- User Feedback via programmatic API (no UI available) -For configuration options and detailed documentation, see the Configuration section. +For configuration options and detailed documentation, see the Configuration section. diff --git a/docs/platforms/apple/guides/watchos/features/index.mdx b/docs/platforms/apple/guides/watchos/features/index.mdx index 16bcb0fd6c6a5..f422579d43169 100644 --- a/docs/platforms/apple/guides/watchos/features/index.mdx +++ b/docs/platforms/apple/guides/watchos/features/index.mdx @@ -13,7 +13,7 @@ watchOS has significant limitations compared to other Apple platforms. Crash det -For a complete list of all available features, see the main Features page. This page highlights watchOS-specific features and limitations. +For a complete list of all available features, see the main Features page. This page highlights watchOS-specific features and limitations. ## watchOS Limitations @@ -38,14 +38,14 @@ Despite the limitations, watchOS still supports several useful features: ### Error Reporting -- Manual error reporting using SentrySDK.capture(error:) or `SentrySDK.capture(message:)` +- Manual error reporting using SentrySDK.capture(error:) or `SentrySDK.capture(message:)` - Handled exceptions can be captured and reported ### Event Enrichment -- Events enriched with device data and environment information -- Attachments enrich your event by storing additional files, such as config or log files -- Source Context shows snippets of code around the location of stack frames (when available) +- Events enriched with device data and environment information +- Attachments enrich your event by storing additional files, such as config or log files +- Source Context shows snippets of code around the location of stack frames (when available) ### Session & User Tracking @@ -60,15 +60,15 @@ Despite the limitations, watchOS still supports several useful features: ### Other Features - Swift Async/Await support for automatically stitching together stack traces of Swift concurrency code (when applicable) -- User Feedback via programmatic API (no UI available) +- User Feedback via programmatic API (no UI available) ## Best Practices for watchOS Given the limitations on watchOS: -1. **Use Manual Error Reporting** - Since crash detection is not available, use SentrySDK.capture(error:) to manually report important errors -2. **Add Context** - Use scopes to add context and tags to help debug issues +1. **Use Manual Error Reporting** - Since crash detection is not available, use SentrySDK.capture(error:) to manually report important errors +2. **Add Context** - Use scopes to add context and tags to help debug issues 3. **Test Thoroughly** - Since symbolication is limited, ensure your error messages and context are descriptive 4. **Consider Companion App** - For critical error tracking, consider implementing error reporting in your companion iOS app -For configuration options and detailed documentation, see the Configuration section. +For configuration options and detailed documentation, see the Configuration section. diff --git a/docs/platforms/dart/common/configuration/filtering.mdx b/docs/platforms/dart/common/configuration/filtering.mdx index 1aba8224c08cc..f0166f3b97b98 100644 --- a/docs/platforms/dart/common/configuration/filtering.mdx +++ b/docs/platforms/dart/common/configuration/filtering.mdx @@ -76,7 +76,7 @@ When a string or a non-error object is raised, Sentry creates a synthetic except Use to make a sampling decision when a transaction or service span starts. Return `0` to drop it. -In transaction mode, use to drop transactions by name or to modify or drop them with custom logic. In stream mode, use to drop spans by name or to modify them. +In transaction mode, use to drop transactions by name or to modify or drop them with custom logic. In stream mode, use to drop spans by name or to modify them. ### Using diff --git a/docs/platforms/dart/common/configuration/options.mdx b/docs/platforms/dart/common/configuration/options.mdx index fc44bc03de1e9..d33af0ac3167e 100644 --- a/docs/platforms/dart/common/configuration/options.mdx +++ b/docs/platforms/dart/common/configuration/options.mdx @@ -202,7 +202,7 @@ By the time is executed, all scope data -Only available in stream mode. +Only available in stream mode. @@ -262,7 +262,7 @@ In stream mode, the sampling context is different: read the span's `name` and `a Controls how spans are collected and sent to Sentry. - In transaction mode (`SentryTraceLifecycle.static`, the default), spans are buffered and sent together as a transaction. -- In stream mode (`SentryTraceLifecycle.stream`), spans are sent to Sentry in batches as they finish. +- In stream mode (`SentryTraceLifecycle.stream`), spans are sent to Sentry in batches as they finish. @@ -270,7 +270,7 @@ Controls how spans are collected and sent to Sentry. -Only available in stream mode. +Only available in stream mode. diff --git a/docs/platforms/dart/common/data-management/data-collected.mdx b/docs/platforms/dart/common/data-management/data-collected.mdx index 31cb749320421..b70df8d2041ea 100644 --- a/docs/platforms/dart/common/data-management/data-collected.mdx +++ b/docs/platforms/dart/common/data-management/data-collected.mdx @@ -46,7 +46,7 @@ The request body of incoming HTTP requests can be sent to Sentry. Whether it's s ## File I/O -By default the Sentry SDK does not send the name or path of files when instrumenting File I/O. +By default the Sentry SDK does not send the name or path of files when instrumenting File I/O. If you want to send file names and paths, set `sendDefaultPii = true`. diff --git a/docs/platforms/dart/common/data-management/sensitive-data/index.mdx b/docs/platforms/dart/common/data-management/sensitive-data/index.mdx index b145d84990b10..0b69b2ba8bd9d 100644 --- a/docs/platforms/dart/common/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dart/common/data-management/sensitive-data/index.mdx @@ -37,7 +37,7 @@ If you _do not_ wish to use the default PII behavior, you can also choose to ide ### , , & -The SDK provides a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. It also provides a hook, that does the same thing for transactions, and a hook, that does the same thing for spans in stream mode. We recommend using these hooks in the SDKs to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. +The SDK provides a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. It also provides a hook, that does the same thing for transactions, and a hook, that does the same thing for spans in stream mode. We recommend using these hooks in the SDKs to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. diff --git a/docs/platforms/dart/common/enriching-events/attributes/index.mdx b/docs/platforms/dart/common/enriching-events/attributes/index.mdx index 52122facafbb4..0bcdab8edfa06 100644 --- a/docs/platforms/dart/common/enriching-events/attributes/index.mdx +++ b/docs/platforms/dart/common/enriching-events/attributes/index.mdx @@ -5,7 +5,7 @@ description: "Attributes automatically enrich your telemetry with typed key-valu -**Attributes** are key-value pairs you can attach to your telemetry (like spans (SDK version `9.23.0`+), logs, and metrics). +**Attributes** are key-value pairs you can attach to your telemetry (like spans (SDK version `9.23.0`+), logs, and metrics). Common uses include subscription tier, feature flags, or any business context that helps you filter and query your telemetry. @@ -24,7 +24,7 @@ Each attribute value is created with a typed `SentryAttribute` factory: -Attributes on spans require stream mode. In stream mode, spans have no contexts, data, or tags — everything is a typed attribute, so `setData` and `setTag` are replaced by `setAttribute` and `setAttributes`. +Attributes on spans require stream mode. In stream mode, spans have no contexts, data, or tags — everything is a typed attribute, so `setData` and `setTag` are replaced by `setAttribute` and `setAttributes`. Attributes on logs and metrics don't require stream mode and work by default. @@ -114,4 +114,4 @@ Sentry.metrics.count( ); ``` -See Metrics for more. +See Metrics for more. diff --git a/docs/platforms/dart/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dart/common/enriching-events/breadcrumbs/index.mdx index 85c00b11839fe..7fffc686e8cc1 100644 --- a/docs/platforms/dart/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/dart/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/dart/common/features/index.mdx b/docs/platforms/dart/common/features/index.mdx index c102434ecd5e5..a9fd5aebf8d1b 100644 --- a/docs/platforms/dart/common/features/index.mdx +++ b/docs/platforms/dart/common/features/index.mdx @@ -11,8 +11,8 @@ Sentry's Dart SDK enables automatic reporting of errors and exceptions, and iden - Breadcrumbs automatically captured: - Dart SDK. - - Logging Integration. - - Dio Integration. + - Logging Integration. + - Dio Integration. - Attachments enrich your event by storing additional files, such as config or log files. - User Feedback provides the @@ -20,7 +20,7 @@ Sentry's Dart SDK enables automatic reporting of errors and exceptions, and iden - Tracing captures spans for: - HTTP requests. - Dio HTTP library. - - File I/O Integration. + - File I/O Integration. - Metrics allow you to send counters, gauges, and distributions to track application health alongside errors and traces. diff --git a/docs/platforms/dart/common/index.mdx b/docs/platforms/dart/common/index.mdx index 2696984f35f61..717efa0bf9750 100644 --- a/docs/platforms/dart/common/index.mdx +++ b/docs/platforms/dart/common/index.mdx @@ -27,7 +27,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori -Sentry provides a dedicated [Flutter SDK](/platforms/dart/guides/flutter) as well. +Sentry provides a dedicated [Flutter SDK](/platforms/dart/guides/flutter/) as well. @@ -94,5 +94,5 @@ try { ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn about the features of Sentry's Dart SDK -- Add performance instrumentation to your app +- Learn about the features of Sentry's Dart SDK +- Add performance instrumentation to your app diff --git a/docs/platforms/dart/common/overhead/index.mdx b/docs/platforms/dart/common/overhead/index.mdx index 898707d481fb9..4bce1d139a3a7 100644 --- a/docs/platforms/dart/common/overhead/index.mdx +++ b/docs/platforms/dart/common/overhead/index.mdx @@ -23,7 +23,7 @@ The SDK also provides methods to manually capture events: Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. +Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. Capturing excessive numbers of breadcrumbs (for example, creating breadcrumbs for all log messages) can cause significant performance overhead. To mitigate this, review and adapt your app's usage of breadcrumbs. For example, increase the min-level of log messages that create breadcrumbs from `warn` to `error`. diff --git a/docs/platforms/dart/common/tracing/trace-propagation/index.mdx b/docs/platforms/dart/common/tracing/trace-propagation/index.mdx index e9336106daa0c..5b3de640db91a 100644 --- a/docs/platforms/dart/common/tracing/trace-propagation/index.mdx +++ b/docs/platforms/dart/common/tracing/trace-propagation/index.mdx @@ -9,7 +9,7 @@ If the overall application landscape that you want to observe with Sentry consis This guide only applies to the default transaction mode. -In stream mode, continuing an incoming distributed trace (from a `sentry-trace` or `baggage` header) isn't supported yet. +In stream mode, continuing an incoming distributed trace (from a `sentry-trace` or `baggage` header) isn't supported yet. diff --git a/docs/platforms/dart/guides/flutter/configuration/filtering.mdx b/docs/platforms/dart/guides/flutter/configuration/filtering.mdx index ce9a2b6d9fe4d..733a9e58811d4 100644 --- a/docs/platforms/dart/guides/flutter/configuration/filtering.mdx +++ b/docs/platforms/dart/guides/flutter/configuration/filtering.mdx @@ -92,7 +92,7 @@ If used on a platform other than Web, this setting will be ignored. Use to make a sampling decision when a transaction or service span starts. Return `0` to drop it. -In transaction mode, use to drop transactions by name or to modify or drop them with custom logic. In stream mode, use to drop spans by name or to modify them. +In transaction mode, use to drop transactions by name or to modify or drop them with custom logic. In stream mode, use to drop spans by name or to modify them. ### Using diff --git a/docs/platforms/dart/guides/flutter/configuration/options.mdx b/docs/platforms/dart/guides/flutter/configuration/options.mdx index 2f0c77e248df4..18e20465b969e 100644 --- a/docs/platforms/dart/guides/flutter/configuration/options.mdx +++ b/docs/platforms/dart/guides/flutter/configuration/options.mdx @@ -229,7 +229,7 @@ By the time is executed, all scope data -Only available in stream mode. +Only available in stream mode. @@ -289,7 +289,7 @@ In stream mode, the sampling context is different: read the span's `name` and `a Controls how spans are collected and sent to Sentry. - In transaction mode (`SentryTraceLifecycle.static`, the default), spans are buffered and sent together as a transaction. -- In stream mode (`SentryTraceLifecycle.stream`), spans are sent to Sentry in batches as they finish. +- In stream mode (`SentryTraceLifecycle.stream`), spans are sent to Sentry in batches as they finish. @@ -297,7 +297,7 @@ Controls how spans are collected and sent to Sentry. -Only available in stream mode. +Only available in stream mode. diff --git a/docs/platforms/dart/guides/flutter/configuration/webview.mdx b/docs/platforms/dart/guides/flutter/configuration/webview.mdx index e089d659ea2f8..2c98d1b2a55dd 100644 --- a/docs/platforms/dart/guides/flutter/configuration/webview.mdx +++ b/docs/platforms/dart/guides/flutter/configuration/webview.mdx @@ -15,7 +15,7 @@ To monitor errors and performance in web views choose the appropriate Sentry Jav - [Sentry React SDK](/platforms/javascript/guides/react/) (if the web project uses React) - [Sentry Angular SDK](/platforms/javascript/guides/angular/) (if the web project uses Angular) -- [Other Sentry JavaScript SDKs](/platforms/javascript) +- [Other Sentry JavaScript SDKs](/platforms/javascript/) ## Notes diff --git a/docs/platforms/dart/guides/flutter/data-management/sensitive-data/index.mdx b/docs/platforms/dart/guides/flutter/data-management/sensitive-data/index.mdx index f6f1128abcc8c..f680434281916 100644 --- a/docs/platforms/dart/guides/flutter/data-management/sensitive-data/index.mdx +++ b/docs/platforms/dart/guides/flutter/data-management/sensitive-data/index.mdx @@ -37,7 +37,7 @@ If you _do not_ wish to use the default PII behavior, you can also choose to ide ### , , & -The SDK provides a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. It also provides a hook, that does the same thing for transactions, and a hook, that does the same thing for spans in stream mode. We recommend using these hooks in the SDKs to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. +The SDK provides a hook, which is invoked before an error or message event is sent and can be used to modify event data to remove sensitive information. It also provides a hook, that does the same thing for transactions, and a hook, that does the same thing for spans in stream mode. We recommend using these hooks in the SDKs to **scrub any data before it is sent**, to ensure that sensitive data never leaves the local environment. diff --git a/docs/platforms/dart/guides/flutter/debug-symbols/index.mdx b/docs/platforms/dart/guides/flutter/debug-symbols/index.mdx index 44115848796ce..69ff6d0809035 100644 --- a/docs/platforms/dart/guides/flutter/debug-symbols/index.mdx +++ b/docs/platforms/dart/guides/flutter/debug-symbols/index.mdx @@ -22,6 +22,6 @@ The more you upload, the more Sentry can symbolicate out of the box — includin Sentry offers several methods to upload debug symbols for Flutter applications: -1. **[Sentry Dart Plugin (Recommended)](/platforms/dart/guides/flutter/debug-symbols/dart-plugin)** - The easiest and most reliable way to upload debug symbols for Flutter applications. It automatically processes, filters, and uploads the correct symbol files for iOS, Android, and Web - significantly reducing the chances of misconfiguration. +1. **[Sentry Dart Plugin (Recommended)](/platforms/dart/guides/flutter/debug-symbols/dart-plugin/)** - The easiest and most reliable way to upload debug symbols for Flutter applications. It automatically processes, filters, and uploads the correct symbol files for iOS, Android, and Web - significantly reducing the chances of misconfiguration. -2. **[Manual Upload Options](/platforms/dart/guides/flutter/debug-symbols/manual-upload)** - Because this method is more complex, requires additional manual steps, and is not currently documented, we do not recommend using it unless absolutely necessary. +2. **[Manual Upload Options](/platforms/dart/guides/flutter/debug-symbols/manual-upload/)** - Because this method is more complex, requires additional manual steps, and is not currently documented, we do not recommend using it unless absolutely necessary. diff --git a/docs/platforms/dart/guides/flutter/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dart/guides/flutter/enriching-events/breadcrumbs/index.mdx index 85c00b11839fe..7fffc686e8cc1 100644 --- a/docs/platforms/dart/guides/flutter/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/dart/guides/flutter/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/dart/guides/flutter/enriching-events/viewhierarchy/index.mdx b/docs/platforms/dart/guides/flutter/enriching-events/viewhierarchy/index.mdx index 659ba7dd345dd..cd104c974d41f 100644 --- a/docs/platforms/dart/guides/flutter/enriching-events/viewhierarchy/index.mdx +++ b/docs/platforms/dart/guides/flutter/enriching-events/viewhierarchy/index.mdx @@ -56,7 +56,7 @@ await SentryFlutter.init((options) { ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/dart/guides/flutter/features/index.mdx b/docs/platforms/dart/guides/flutter/features/index.mdx index fa1dd06a366f7..05ae173fab0e8 100644 --- a/docs/platforms/dart/guides/flutter/features/index.mdx +++ b/docs/platforms/dart/guides/flutter/features/index.mdx @@ -17,19 +17,19 @@ Sentry's Flutter SDK enables automatic reporting of errors and exceptions, and i - ObjC, Swift, and C for iOS. - Automatic detection of Application Not Responding (ANR) and App Hangs. - Offline storage of events. -- Events enriched with device data. +- Events enriched with device data. - Breadcrumbs automatically captured: - by the Flutter SDK. - via the Native SDKs Automatic Breadcrumbs for Android and Automatic Breadcrumbs for iOS. - as well as `http` with the Dart SDK. -- Integrations for sqflite, routing and more. For a complete list, see integrations. +- Integrations for sqflite, routing and more. For a complete list, see integrations. - Release Health tracks crash free users and sessions. -- Attachments +- Attachments that can enrich your event by storing additional files, such as config or log files. -- Tracing that can track - +- Tracing that can track + app start time , @@ -37,37 +37,37 @@ Sentry's Flutter SDK enables automatic reporting of errors and exceptions, and i Time to Initial Display and Time to Full Display , - + Slow and Frozen Frames , and - + User Interaction . For a complete list, see - + automatic instrumentations . -- User Feedback, providing the +- User Feedback, providing the ability to collect user feedback when an unexpected event occurs. -- Screenshot and - +- Screenshot and + View Hierarchy attachments for errors. -- Profiling collects detailed +- Profiling collects detailed information about your code at the function level. Profiling is currently supported on **iOS** and **macOS**, and captures profiles across multiple language layers, including native languages (such as Swift and Objective-C) as well as Dart. -- +- Source Context shows snippets of code around the location of stack frames. -- Sentry Dart Plugin makes +- Sentry Dart Plugin makes uploading debug symbols easy and automatic. -- Metrics allow you to send counters, +- Metrics allow you to send counters, gauges, and distributions to track application health alongside errors and traces. diff --git a/docs/platforms/dart/guides/flutter/index.mdx b/docs/platforms/dart/guides/flutter/index.mdx index 5dd2b03984907..34a91e24dff1b 100644 --- a/docs/platforms/dart/guides/flutter/index.mdx +++ b/docs/platforms/dart/guides/flutter/index.mdx @@ -165,6 +165,6 @@ try { ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn about the features of Sentry's Flutter SDK +- Learn about the features of Sentry's Flutter SDK - Add readable stack traces to errors -- Add performance instrumentation to your app +- Add performance instrumentation to your app diff --git a/docs/platforms/dart/guides/flutter/manual-setup.mdx b/docs/platforms/dart/guides/flutter/manual-setup.mdx index cbf07999b9b45..900db16430893 100644 --- a/docs/platforms/dart/guides/flutter/manual-setup.mdx +++ b/docs/platforms/dart/guides/flutter/manual-setup.mdx @@ -86,6 +86,6 @@ try { ## Next Steps -- Learn about the features of Sentry's Flutter SDK +- Learn about the features of Sentry's Flutter SDK - Add readable stack traces to errors -- Add performance instrumentation to your app +- Add performance instrumentation to your app diff --git a/docs/platforms/dart/guides/flutter/overhead/index.mdx b/docs/platforms/dart/guides/flutter/overhead/index.mdx index 8eecdb1395b43..7905f546862c8 100644 --- a/docs/platforms/dart/guides/flutter/overhead/index.mdx +++ b/docs/platforms/dart/guides/flutter/overhead/index.mdx @@ -23,13 +23,13 @@ The SDK also provides methods to manually capture events: Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. +If you activate these features, the SDK will capture Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. ## Breadcrumbs -Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. +Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. Capturing excessive numbers of breadcrumbs (for example, creating breadcrumbs for all log messages) can cause significant performance overhead. To mitigate this, review and adapt your app's usage of breadcrumbs. For example, increase the min-level of log messages that create breadcrumbs from `warn` to `error`. diff --git a/docs/platforms/dart/guides/flutter/profiling/troubleshooting/index.mdx b/docs/platforms/dart/guides/flutter/profiling/troubleshooting/index.mdx index e8d61cdf3461e..8a979af52f0a1 100644 --- a/docs/platforms/dart/guides/flutter/profiling/troubleshooting/index.mdx +++ b/docs/platforms/dart/guides/flutter/profiling/troubleshooting/index.mdx @@ -8,7 +8,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. ### Limitations diff --git a/docs/platforms/dart/guides/flutter/size-analysis/index.mdx b/docs/platforms/dart/guides/flutter/size-analysis/index.mdx index 97018eb35e301..e3ff1afca162f 100644 --- a/docs/platforms/dart/guides/flutter/size-analysis/index.mdx +++ b/docs/platforms/dart/guides/flutter/size-analysis/index.mdx @@ -6,7 +6,7 @@ description: Upload Flutter builds to Sentry for size analysis. new: true --- -[Size Analysis](/product/size-analysis) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. +[Size Analysis](/product/size-analysis/) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. ## Getting Started - iOS diff --git a/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx index a48e54f323d9d..39af37ac2057e 100644 --- a/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/dart/guides/flutter/tracing/instrumentation/automatic-instrumentation.mdx @@ -51,7 +51,7 @@ Learn more in our [App Start Instrumentation](/platforms/dart/guides/flutter/int Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements to the traces you capture. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). Learn more how to set it up in our [Slow and Frozen Frames Instrumentation](/platforms/dart/guides/flutter/integrations/slow-and-frozen-frames-instrumentation/) docs. diff --git a/docs/platforms/dart/guides/flutter/tracing/trace-propagation/index.mdx b/docs/platforms/dart/guides/flutter/tracing/trace-propagation/index.mdx index e9336106daa0c..5b3de640db91a 100644 --- a/docs/platforms/dart/guides/flutter/tracing/trace-propagation/index.mdx +++ b/docs/platforms/dart/guides/flutter/tracing/trace-propagation/index.mdx @@ -9,7 +9,7 @@ If the overall application landscape that you want to observe with Sentry consis This guide only applies to the default transaction mode. -In stream mode, continuing an incoming distributed trace (from a `sentry-trace` or `baggage` header) isn't supported yet. +In stream mode, continuing an incoming distributed trace (from a `sentry-trace` or `baggage` header) isn't supported yet. diff --git a/docs/platforms/dart/guides/flutter/troubleshooting.mdx b/docs/platforms/dart/guides/flutter/troubleshooting.mdx index 70f38ae673c78..6b6eeb4774128 100644 --- a/docs/platforms/dart/guides/flutter/troubleshooting.mdx +++ b/docs/platforms/dart/guides/flutter/troubleshooting.mdx @@ -70,7 +70,7 @@ Please read the [Android developer documentation](https://developer.android.com/ ## "Missing API declaration" after App Store review -Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/dart/guides/flutter/data-management/apple-privacy-manifest) guide. +Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/dart/guides/flutter/data-management/apple-privacy-manifest/) guide. ## Known Limitations diff --git a/docs/platforms/dotnet/common/configuration/msbuild.mdx b/docs/platforms/dotnet/common/configuration/msbuild.mdx index 2c6d9f4a0ad57..a159cd60d3787 100644 --- a/docs/platforms/dotnet/common/configuration/msbuild.mdx +++ b/docs/platforms/dotnet/common/configuration/msbuild.mdx @@ -4,8 +4,8 @@ description: "Configure MSBuild properties in your .NET project to automatically sidebar_order: 10 --- -The [Sentry CLI](/cli) has many useful features that can improve your Sentry experience. -For .NET, you can use it to upload [debug information files](/cli/dif), such as .NET `PDB` symbol files. +The [Sentry CLI](/cli/) has many useful features that can improve your Sentry experience. +For .NET, you can use it to upload [debug information files](/cli/dif/), such as .NET `PDB` symbol files. This allows Sentry to show a more complete stack trace, including file names and line numbers. You can also use it to upload _source code_, which enables Sentry to display [source context](../../data-management/debug-files/source-context/) when viewing stack traces. diff --git a/docs/platforms/dotnet/common/crons/index.mdx b/docs/platforms/dotnet/common/crons/index.mdx index 5be05065334e3..9d62cd175ad10 100644 --- a/docs/platforms/dotnet/common/crons/index.mdx +++ b/docs/platforms/dotnet/common/crons/index.mdx @@ -10,7 +10,7 @@ Once implemented, it'll allow you to get alerts and metrics to help you solve er -If you are using [Hangfire](https://www.hangfire.io/), please see how to setup monitoring for Hangfire jobs. +If you are using [Hangfire](https://www.hangfire.io/), please see how to setup monitoring for Hangfire jobs. diff --git a/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx b/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx index 60d5ad430b1e8..68993f91a216a 100644 --- a/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx +++ b/docs/platforms/dotnet/common/data-management/debug-files/upload/index.mdx @@ -22,7 +22,7 @@ true for mobile apps targeting Android or iOS, such as those developed with To make this easier, the `Sentry` NuGet package (as of version 3.26.1) includes the Sentry CLI as a bundled tool, and will invoke it when building your project if the msbuild property `SentryUploadSymbols` is set to true (default to false). -Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild) for details. +Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild/) for details. The remaining information on this page describes invoking the Sentry CLI manually. diff --git a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx index 0065487695acc..dad003b758914 100644 --- a/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/dotnet/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/dotnet/common/profiling/troubleshooting/index.mdx b/docs/platforms/dotnet/common/profiling/troubleshooting/index.mdx index 380fdf912c294..726e06341e901 100644 --- a/docs/platforms/dotnet/common/profiling/troubleshooting/index.mdx +++ b/docs/platforms/dotnet/common/profiling/troubleshooting/index.mdx @@ -18,7 +18,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. - If the transactions happen too soon after `Sentry.Init()`, they may not be captured yet. This is because the `ProfilingIntegration()` from `Sentry.Profiling` NuGet package initializes asynchronously by default. diff --git a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx index 568ab63e637a5..7fcd150aad460 100644 --- a/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx +++ b/docs/platforms/dotnet/common/tracing/instrumentation/opentelemetry-otlp.mdx @@ -5,7 +5,7 @@ sidebar_order: 22 keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP exporter configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP exporter configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). ## Install diff --git a/docs/platforms/dotnet/guides/android/index.mdx b/docs/platforms/dotnet/guides/android/index.mdx index e7bb203f8e68a..234ed754dd376 100644 --- a/docs/platforms/dotnet/guides/android/index.mdx +++ b/docs/platforms/dotnet/guides/android/index.mdx @@ -8,9 +8,9 @@ Sentry supports [.NET for Android](https://learn.microsoft.com/dotnet/android/ge ## Overview of the features -- All the features of our main [.NET SDK](/platforms/dotnet), for your managed code +- All the features of our main [.NET SDK](/platforms/dotnet/), for your managed code - Attach LogCat logs to events -- Java crash reporting for Android, leveraging our [Android SDK](/platforms/android) including: +- Java crash reporting for Android, leveraging our [Android SDK](/platforms/android/) including: - [Capture Application Not Responding (ANR) errors](/platforms/android/configuration/app-not-respond/) when the app is unresponsive - Automatically [attach screenshots to Java exceptions](/platforms/android/enriching-events/screenshots/) - Automatic breadcrumbs for Activity lifecycle, App lifecycle, System and Network events and User Interactions diff --git a/docs/platforms/dotnet/guides/apple/index.mdx b/docs/platforms/dotnet/guides/apple/index.mdx index 85fe039ac772f..85b91c0e55fe1 100644 --- a/docs/platforms/dotnet/guides/apple/index.mdx +++ b/docs/platforms/dotnet/guides/apple/index.mdx @@ -8,8 +8,8 @@ Sentry supports [.NET for iOS, macOS, and Mac Catalyst](https://learn.microsoft. ## Overview of the features -- All the features of our main [.NET SDK](/platforms/dotnet), for your managed code -- Native crash reporting for Apple platforms, leveraging our [Cocoa SDK](/platforms/apple) including: +- All the features of our main [.NET SDK](/platforms/dotnet/), for your managed code +- Native crash reporting for Apple platforms, leveraging our [Cocoa SDK](/platforms/apple/) including: - Automatically [attach screenshots to Native exceptions](/platforms/apple/guides/ios/configuration/options/#attach-screenshot) - Detect [App Hangs](/platforms/apple/configuration/app-hangs/) - [Automatic performance tracing](/platforms/apple/performance/) diff --git a/docs/platforms/dotnet/guides/aspnetcore/index.mdx b/docs/platforms/dotnet/guides/aspnetcore/index.mdx index 51b92ab1c2966..23ed990a99b42 100644 --- a/docs/platforms/dotnet/guides/aspnetcore/index.mdx +++ b/docs/platforms/dotnet/guides/aspnetcore/index.mdx @@ -87,7 +87,7 @@ An example of some of the options that can be configured via `appsettings.json`: -Setting `TracesSampleRate` to `1.0` in this example configures Sentry to capture 100% of transactions for tracing. We recommend adjusting this value in production. See Automatic Instrumentation for further information. +Setting `TracesSampleRate` to `1.0` in this example configures Sentry to capture 100% of transactions for tracing. We recommend adjusting this value in production. See Automatic Instrumentation for further information. diff --git a/docs/platforms/dotnet/guides/maui/index.mdx b/docs/platforms/dotnet/guides/maui/index.mdx index fa454b40ad56a..00d9fa5fe59d4 100644 --- a/docs/platforms/dotnet/guides/maui/index.mdx +++ b/docs/platforms/dotnet/guides/maui/index.mdx @@ -9,9 +9,9 @@ Sentry has an integration for the [.NET Multi-platform App UI (MAUI)](https://do ## Overview of the features - Easy MAUI integration by calling `UseSentry` on your `MauiAppBuilder` -- All the features of our main [.NET SDK](/platforms/dotnet), for your managed code -- Native crash reporting for Android, leveraging our [Android SDK](/platforms/android) -- Native crash reporting for iOS and Mac Catalyst, leveraging our [Cocoa SDK for iOS](/platforms/apple/guides/ios) +- All the features of our main [.NET SDK](/platforms/dotnet/), for your managed code +- Native crash reporting for Android, leveraging our [Android SDK](/platforms/android/) +- Native crash reporting for iOS and Mac Catalyst, leveraging our [Cocoa SDK for iOS](/platforms/apple/guides/ios/) - Managed crash reporting (unhandled exceptions), on all MAUI platforms (iOS, Android, Windows, Mac Catalyst, and Tizen) - Line numbers for your .NET stack traces when PDBs are uploaded to Sentry - Automatic breadcrumbs for MAUI app lifecycle and UI events diff --git a/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx b/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx index fb6fad4f078f5..41f7f9d86c513 100644 --- a/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/elixir/enriching-events/breadcrumbs/index.mdx @@ -5,7 +5,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx index fb47e3426abc3..12366f5eeb039 100644 --- a/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/go/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/go/common/usage/index.mdx b/docs/platforms/go/common/usage/index.mdx index 4aed9b7286063..bde0e9506e6f8 100644 --- a/docs/platforms/go/common/usage/index.mdx +++ b/docs/platforms/go/common/usage/index.mdx @@ -36,4 +36,4 @@ Messages show up as issues on your issue stream, with the message as the issue n ## Capturing Logs -Another common operation is to capture logs. Check Logs for how to setup your logging integration to send log entries to Sentry. \ No newline at end of file +Another common operation is to capture logs. Check Logs for how to setup your logging integration to send log entries to Sentry. \ No newline at end of file diff --git a/docs/platforms/godot/data-management/data-collected.mdx b/docs/platforms/godot/data-management/data-collected.mdx index 44658a0d64a16..c733c9ad3af7d 100644 --- a/docs/platforms/godot/data-management/data-collected.mdx +++ b/docs/platforms/godot/data-management/data-collected.mdx @@ -42,7 +42,7 @@ The Sentry SDK collects information about the device, such as the name, version ## Screenshots -The screenshot feature is disabled by default. If you choose to enable this feature in options, any screenshots captured may contain sensitive data visible in the application at the time of the error. +The screenshot feature is disabled by default. If you choose to enable this feature in options, any screenshots captured may contain sensitive data visible in the application at the time of the error. ## Godot Log File diff --git a/docs/platforms/godot/enriching-events/breadcrumbs/index.mdx b/docs/platforms/godot/enriching-events/breadcrumbs/index.mdx index 3caec201492b2..43ad78dcb312c 100644 --- a/docs/platforms/godot/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/godot/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/godot/enriching-events/view-hierarchy/index.mdx b/docs/platforms/godot/enriching-events/view-hierarchy/index.mdx index c1dfbe9498b25..aff3554400ab2 100644 --- a/docs/platforms/godot/enriching-events/view-hierarchy/index.mdx +++ b/docs/platforms/godot/enriching-events/view-hierarchy/index.mdx @@ -38,7 +38,7 @@ SentrySdk.Init(options => ## Viewing Scene Tree Attachments -Scene tree information is attached as `view-hierarchy.json` file. You can find it in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +Scene tree information is attached as `view-hierarchy.json` file. You can find it in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/java/common/configuration/options.mdx b/docs/platforms/java/common/configuration/options.mdx index 9249c24ec5d08..f4b8165ec720b 100644 --- a/docs/platforms/java/common/configuration/options.mdx +++ b/docs/platforms/java/common/configuration/options.mdx @@ -150,7 +150,7 @@ This parameter controls whether integrations should capture HTTP request bodies. - `always`: The SDK will always capture the request body as long as Sentry can make sense of it. For request bodies to be captured, the flag must also be enabled. -Please consult the documentation for to evaluate whether you would want to enable it, making sure to manually remove the data you don't want to send using our features for managing Sensitive Data. +Please consult the documentation for to evaluate whether you would want to enable it, making sure to manually remove the data you don't want to send using our features for managing Sensitive Data. diff --git a/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx index fb47e3426abc3..12366f5eeb039 100644 --- a/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/java/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/java/common/integrations/reactor.mdx b/docs/platforms/java/common/integrations/reactor.mdx index 31659a6c67ea0..29db600120f7c 100644 --- a/docs/platforms/java/common/integrations/reactor.mdx +++ b/docs/platforms/java/common/integrations/reactor.mdx @@ -107,6 +107,6 @@ tx.finish() For more complex use cases, you can also use `SentryReactorUtils.withSentryForkedRoots` to fork the root scopes or `SentryReactorUtils.withSentryScopes` to wrap the operation in arbitrary scopes. -For more information on scopes and scope forking, please consult our [scopes documentation](/platforms/java/enriching-events/scopes). +For more information on scopes and scope forking, please consult our [scopes documentation](/platforms/java/enriching-events/scopes/). You can also consult our GitHub repository for practical examples on how to use our Reactor integration with Spring WebFlux with [Spring Boot 2](https://github.com/getsentry/sentry-java/tree/main/sentry-samples/sentry-samples-spring-boot-webflux) and [Spring Boot 3](https://github.com/getsentry/sentry-java/tree/main/sentry-samples/sentry-samples-spring-boot-webflux-jakarta). diff --git a/docs/platforms/java/common/legacy/index.mdx b/docs/platforms/java/common/legacy/index.mdx index e258fd92f87bd..705bff34ccb74 100644 --- a/docs/platforms/java/common/legacy/index.mdx +++ b/docs/platforms/java/common/legacy/index.mdx @@ -8,8 +8,8 @@ This section covers the legacy Sentry SDK for Java (1.7.x), which is no longer u Find more details about how to set up, configure and use the Legacy SDK: -- [Configuration](/platforms/java/legacy/configuration) -- [Manual Usage](/platforms/java/legacy/usage) +- [Configuration](/platforms/java/legacy/configuration/) +- [Manual Usage](/platforms/java/legacy/usage/) ## Integrations diff --git a/docs/platforms/java/common/legacy/log4j2/index.mdx b/docs/platforms/java/common/legacy/log4j2/index.mdx index ede3ada320bb5..cbac292afc50c 100644 --- a/docs/platforms/java/common/legacy/log4j2/index.mdx +++ b/docs/platforms/java/common/legacy/log4j2/index.mdx @@ -9,7 +9,7 @@ An [updated Java SDK](/platforms/java/) SDK supersedes this deprecated version. -The `sentry-log4j2` library provides [Log4j 2](https://logging.apache.org/log4j/2.x/) support for Sentry via an [Appender](https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/Appender.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events. +The `sentry-log4j2` library provides [Log4j 2](https://logging.apache.org/log4j/2.x/) support for Sentry via an [Appender](https://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/Appender.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage/), in order to do things like record breadcrumbs, set the current user, or manually send events. The source can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-log4j2). diff --git a/docs/platforms/java/common/legacy/logback/index.mdx b/docs/platforms/java/common/legacy/logback/index.mdx index 96cdd7e214ddd..59535e2b40114 100644 --- a/docs/platforms/java/common/legacy/logback/index.mdx +++ b/docs/platforms/java/common/legacy/logback/index.mdx @@ -9,7 +9,7 @@ A new Java SDK has superseded this deprecated version. Sentry preserves this doc -The `sentry-logback` library provides [Logback](http://logback.qos.ch/) support for Sentry via an [Appender](https://logback.qos.ch/manual/appenders.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events. +The `sentry-logback` library provides [Logback](http://logback.qos.ch/) support for Sentry via an [Appender](https://logback.qos.ch/manual/appenders.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage/), in order to do things like record breadcrumbs, set the current user, or manually send events. The source can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-logback). diff --git a/docs/platforms/java/common/legacy/logging/index.mdx b/docs/platforms/java/common/legacy/logging/index.mdx index d79fba0719a28..9c8bf8508ff2a 100644 --- a/docs/platforms/java/common/legacy/logging/index.mdx +++ b/docs/platforms/java/common/legacy/logging/index.mdx @@ -9,7 +9,7 @@ An [updated Java SDK](/platforms/java/) supersedes this deprecated version. Sent -The `sentry` library provides a [java.util.logging Handler](http://docs.oracle.com/javase/8/docs/api/java/util/logging/Handler.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events. +The `sentry` library provides a [java.util.logging Handler](http://docs.oracle.com/javase/8/docs/api/java/util/logging/Handler.html) that sends logged exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage/), in order to do things like record breadcrumbs, set the current user, or manually send events. The source for `sentry` can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry). diff --git a/docs/platforms/java/common/legacy/spring/index.mdx b/docs/platforms/java/common/legacy/spring/index.mdx index bc4608d51a309..f29edebfe3a50 100644 --- a/docs/platforms/java/common/legacy/spring/index.mdx +++ b/docs/platforms/java/common/legacy/spring/index.mdx @@ -9,7 +9,7 @@ An [updated Java SDK](/platforms/java/) supersedes this deprecated version. Sent -The `sentry-spring` library provides [Spring](https://spring.io/) support for Sentry via a [HandlerExceptionResolver](https://docs.spring.io/spring/docs/4.3.9.RELEASE/javadoc-api/org/springframework/web/servlet/HandlerExceptionResolver.html) that sends exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage), in order to do things like record breadcrumbs, set the current user, or manually send events. +The `sentry-spring` library provides [Spring](https://spring.io/) support for Sentry via a [HandlerExceptionResolver](https://docs.spring.io/spring/docs/4.3.9.RELEASE/javadoc-api/org/springframework/web/servlet/HandlerExceptionResolver.html) that sends exceptions to Sentry. Once this integration is configured you can _also_ use Sentry’s static API, [as shown on the usage page](/platforms/java/legacy/usage/), in order to do things like record breadcrumbs, set the current user, or manually send events. The source can be found [on GitHub](https://github.com/getsentry/sentry-java/tree/master/sentry-spring). diff --git a/docs/platforms/java/common/migration/6.x-to-7.0.mdx b/docs/platforms/java/common/migration/6.x-to-7.0.mdx index 4b9561c1af75c..f54aaea0f3546 100644 --- a/docs/platforms/java/common/migration/6.x-to-7.0.mdx +++ b/docs/platforms/java/common/migration/6.x-to-7.0.mdx @@ -8,7 +8,7 @@ description: "Learn about migrating from version 6.x to 7.0.0" ### Breaking Changes -- The `sentry-android-okhttp` classes were deprecated in favor of `sentry-okhttp`, which is a pure Java module and can be used in non-Android projects. Check the [OkHttp Integration](/platforms/java/tracing/instrumentation/okhttp) documentation to see how to use it. +- The `sentry-android-okhttp` classes were deprecated in favor of `sentry-okhttp`, which is a pure Java module and can be used in non-Android projects. Check the [OkHttp Integration](/platforms/java/tracing/instrumentation/okhttp/) documentation to see how to use it. - The `SentryOkHttpUtils` class was removed from the public API. If you were using it, consider filing a [feature request](https://github.com/getsentry/sentry-java/issues). - If you're using `sentry-kotlin-extensions`, it now requires `kotlinx-coroutines-core` version `1.6.1` or higher. - Changed the return type of `SentryApolloInterceptor.BeforeSpanCallback` from `ISpan` to `ISpan?`. diff --git a/docs/platforms/java/common/opentelemetry/setup/agentless.mdx b/docs/platforms/java/common/opentelemetry/setup/agentless.mdx index 546c881c68046..6ee63261a7517 100644 --- a/docs/platforms/java/common/opentelemetry/setup/agentless.mdx +++ b/docs/platforms/java/common/opentelemetry/setup/agentless.mdx @@ -5,7 +5,7 @@ description: "Using OpenTelemetry with sentry-opentelemetry-agentless." sidebar_order: 200 --- -If you do not want to use our recommended Java Agent, we also offer a dependency that allows you to use OpenTelemetry with Sentry. +If you do not want to use our recommended Java Agent, we also offer a dependency that allows you to use OpenTelemetry with Sentry. ## Install diff --git a/docs/platforms/java/common/opentelemetry/setup/index.mdx b/docs/platforms/java/common/opentelemetry/setup/index.mdx index fb2f83cb09f48..ef4baa667ea89 100644 --- a/docs/platforms/java/common/opentelemetry/setup/index.mdx +++ b/docs/platforms/java/common/opentelemetry/setup/index.mdx @@ -11,16 +11,16 @@ There are multiple ways to configure our OpenTelemetry integration. You may chos -For a guide on how to set up `sentry-opentelemetry-agent`, please have a look at the detailed Agent docs. +For a guide on how to set up `sentry-opentelemetry-agent`, please have a look at the detailed Agent docs. ## Agentless -For a guide on how to set up agentless, please have a look at the detailed Agentless docs. +For a guide on how to set up agentless, please have a look at the detailed Agentless docs. ## OTLP If you want OpenTelemetry to handle tracing and export spans via OTLP directly to Sentry, while Sentry handles errors, logs, and metrics, you can use the `sentry-opentelemetry-otlp` module. This is a lightweight integration where Sentry only reads the trace and span IDs from the OpenTelemetry `Context` to correlate its events with OpenTelemetry traces. Unlike the Agent and Agentless integrations above, it does not use OpenTelemetry for scope storage or span creation within the Sentry SDK. -For a guide on how to set up OTLP, please have a look at the detailed OTLP docs. +For a guide on how to set up OTLP, please have a look at the detailed OTLP docs. diff --git a/docs/platforms/java/common/opentelemetry/setup/otlp.mdx b/docs/platforms/java/common/opentelemetry/setup/otlp.mdx index 25b7aaa90066f..9fdac6cf12ee4 100644 --- a/docs/platforms/java/common/opentelemetry/setup/otlp.mdx +++ b/docs/platforms/java/common/opentelemetry/setup/otlp.mdx @@ -7,7 +7,7 @@ sidebar_order: 300 Use the `sentry-opentelemetry-otlp` module when you want OpenTelemetry to handle tracing (with spans exported via OTLP to Sentry) while Sentry handles errors, logs, and metrics. Sentry reads trace and span IDs from the OpenTelemetry `Context` so that all Sentry events are correlated with your OpenTelemetry traces. -Unlike the Agent and Agentless integrations, this module does not use OpenTelemetry for scope storage or span creation within the Sentry SDK. +Unlike the Agent and Agentless integrations, this module does not use OpenTelemetry for scope storage or span creation within the Sentry SDK. ## Install diff --git a/docs/platforms/java/common/tracing/instrumentation/apollo2.mdx b/docs/platforms/java/common/tracing/instrumentation/apollo2.mdx index 1d87d93ccefb0..823e04d6e9a9a 100644 --- a/docs/platforms/java/common/tracing/instrumentation/apollo2.mdx +++ b/docs/platforms/java/common/tracing/instrumentation/apollo2.mdx @@ -19,7 +19,7 @@ Sentry Apollo integration provides the `SentryApolloInterceptor`, which creates -This integration supports Apollo 2.x. For Apollo 3.x use our Apollo 3 integration. For Apollo 4.x use our Apollo 4 integration. +This integration supports Apollo 2.x. For Apollo 3.x use our Apollo 3 integration. For Apollo 4.x use our Apollo 4 integration. diff --git a/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx b/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx index 6140ed32eace5..a20b460b2045a 100644 --- a/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx +++ b/docs/platforms/java/common/tracing/instrumentation/apollo3.mdx @@ -19,7 +19,7 @@ Sentry's Apollo 3 integration provides both the `SentryApollo3Interceptor` and t -This integration supports Apollo 3.x. For Apollo 4.x use our Apollo 4 integration. +This integration supports Apollo 3.x. For Apollo 4.x use our Apollo 4 integration. @@ -224,7 +224,7 @@ Sentry.init { options -> } ``` -Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. +Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay/) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. Alternatively, you can customize the event and scrub the data yourself. diff --git a/docs/platforms/java/common/tracing/instrumentation/apollo4.mdx b/docs/platforms/java/common/tracing/instrumentation/apollo4.mdx index f379c4588da1f..33bf35b6e8a59 100644 --- a/docs/platforms/java/common/tracing/instrumentation/apollo4.mdx +++ b/docs/platforms/java/common/tracing/instrumentation/apollo4.mdx @@ -201,7 +201,7 @@ Sentry.init { options -> } ``` -Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. +Error events will contain the raw bodies of GraphQL requests and responses, which may include sensitive data. To avoid this, parameterize your queries using the [variables](https://spec.graphql.org/October2021/#sec-Language.Variables) field. [Relay](/product/relay/) will then run [PII Data Scrubbing](/product/relay/#pii-data-scrubbing), automatically transforming values into `[Filtered]`. Alternatively, you can customize the event and scrub the data yourself. diff --git a/docs/platforms/java/common/tracing/instrumentation/opentelemetry.mdx b/docs/platforms/java/common/tracing/instrumentation/opentelemetry.mdx index 078660c58ad04..b1c6ba007a30f 100644 --- a/docs/platforms/java/common/tracing/instrumentation/opentelemetry.mdx +++ b/docs/platforms/java/common/tracing/instrumentation/opentelemetry.mdx @@ -5,4 +5,4 @@ description: "Using OpenTelemetry with Sentry Performance." sidebar_order: 20 --- -This page has moved to a top level page. +This page has moved to a top level page. diff --git a/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx b/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx index 738dbf78ab5a9..7c66ffb6a4fe9 100644 --- a/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx +++ b/docs/platforms/javascript/common/best-practices/multiple-sentry-instances.mdx @@ -20,7 +20,7 @@ keywords: ["multiple clients", "BrowserClient", "NodeClient", "monorepo"] -Creating multiple Sentry clients is **not recommended** in general, as it can lead to unexpected behavior. In case you are using Micro Frontends or similar, multiplexing might be a better solution than using multiple clients. Check out [Micro Frontends](/platforms/javascript/best-practices/micro-frontends) in the Best Practices for more information. +Creating multiple Sentry clients is **not recommended** in general, as it can lead to unexpected behavior. In case you are using Micro Frontends or similar, multiplexing might be a better solution than using multiple clients. Check out [Micro Frontends](/platforms/javascript/best-practices/micro-frontends/) in the Best Practices for more information. diff --git a/docs/platforms/javascript/common/configuration/apis.mdx b/docs/platforms/javascript/common/configuration/apis.mdx index 52e65a9062f3e..dae04f26e7217 100644 --- a/docs/platforms/javascript/common/configuration/apis.mdx +++ b/docs/platforms/javascript/common/configuration/apis.mdx @@ -153,7 +153,7 @@ integrations after `Sentry.init()` has been called. Note that it is recommended to pass integrations to `init` instead of calling this method, where possible. -See Integrations for +See Integrations for more information on how to use integrations. @@ -174,7 +174,7 @@ Sentry.lazyLoadIntegration("replayIntegration") If you use a bundler, using e.g. `const { replayIntegration } = await import('@sentry/browser')` is recommended instead. -See Integrations for +See Integrations for more information on how to use integrations. @@ -394,7 +394,7 @@ There are no restrictions on context name. In the context object, all keys are a By default, Sentry SDKs normalize nested structured context data up to three levels deep. Any data beyond this depth will be trimmed and marked using its type instead. -To adjust this default, use the `normalizeDepth` SDK option. +To adjust this default, use the `normalizeDepth` SDK option. Learn more about conventions for common contexts in the [contexts interface developer documentation](https://develop.sentry.dev/sdk/foundations/transport/event-payloads/contexts/). @@ -489,7 +489,7 @@ Sentry.setContext("character", { - `Sentry.setUser()` will set the user for the currently active request - see Request Isolation for more information. For example, if you want to set the user for a single request, you can do this like this: + `Sentry.setUser()` will set the user for the currently active request - see Request Isolation for more information. For example, if you want to set the user for a single request, you can do this like this: diff --git a/docs/platforms/javascript/common/configuration/filtering.mdx b/docs/platforms/javascript/common/configuration/filtering.mdx index 481aafa04376f..9e23041d6c70b 100644 --- a/docs/platforms/javascript/common/configuration/filtering.mdx +++ b/docs/platforms/javascript/common/configuration/filtering.mdx @@ -155,7 +155,7 @@ If you want to drop the transaction/service span, including its child spans: -If you're using stream mode, make sure to wrap with `Sentry.withStreamedSpan()`. +If you're using stream mode, make sure to wrap with `Sentry.withStreamedSpan()`. diff --git a/docs/platforms/javascript/common/configuration/integrations/bunruntimemetrics.mdx b/docs/platforms/javascript/common/configuration/integrations/bunruntimemetrics.mdx index 0ae3204637b48..29b3cbfc277f0 100644 --- a/docs/platforms/javascript/common/configuration/integrations/bunruntimemetrics.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/bunruntimemetrics.mdx @@ -41,7 +41,7 @@ The following metrics are emitted every 30 seconds by default: -Unlike the [Node.js equivalent](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics), event loop delay histogram metrics are not available in Bun because `monitorEventLoopDelay` is not supported by the Bun runtime. +Unlike the [Node.js equivalent](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics/), event loop delay histogram metrics are not available in Bun because `monitorEventLoopDelay` is not supported by the Bun runtime. diff --git a/docs/platforms/javascript/common/configuration/integrations/denoruntimemetrics.mdx b/docs/platforms/javascript/common/configuration/integrations/denoruntimemetrics.mdx index ff1797b845da2..ddb8709558b89 100644 --- a/docs/platforms/javascript/common/configuration/integrations/denoruntimemetrics.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/denoruntimemetrics.mdx @@ -37,7 +37,7 @@ The following metrics are emitted every 30 seconds by default: -Unlike the [Node.js equivalent](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics), CPU and event loop metrics are not available because Deno does not expose `process.cpuUsage()`, `performance.eventLoopUtilization()`, or `monitorEventLoopDelay`. +Unlike the [Node.js equivalent](/platforms/javascript/guides/node/configuration/integrations/noderuntimemetrics/), CPU and event loop metrics are not available because Deno does not expose `process.cpuUsage()`, `performance.eventLoopUtilization()`, or `monitorEventLoopDelay`. diff --git a/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx b/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx index 0d6fcfac95647..97d371b2b5962 100644 --- a/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx @@ -38,7 +38,7 @@ The Element Timing API is only supported in Chromium-based browsers (Chrome, Edg -This integration requires Sentry Application Metrics to be available in your Sentry organization. +This integration requires Sentry Application Metrics to be available in your Sentry organization. ```javascript Sentry.init({ diff --git a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx index 79363d6c46b80..c5bddd540aa87 100644 --- a/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/vercelai.mdx @@ -59,7 +59,7 @@ That difference decides where you configure the integration and which options do -Cloudflare Workers can't load OpenTelemetry instrumentation. On both entrypoints, Sentry reads the spans the AI SDK emits on its own instead of patching your call sites, so you must pass `experimental_telemetry` on every call. The `@sentry/cloudflare/nodejs_compat` entrypoint adds the Node.js APIs the AI SDK v7 telemetry channel needs. +Cloudflare Workers can't load OpenTelemetry instrumentation. On both entrypoints, Sentry reads the spans the AI SDK emits on its own instead of patching your call sites, so you must pass `experimental_telemetry` on every call. The `@sentry/cloudflare/nodejs_compat` entrypoint adds the Node.js APIs the AI SDK v7 telemetry channel needs. Your entrypoint decides the rest: @@ -141,7 +141,7 @@ Deno can't load OpenTelemetry instrumentation, so Sentry can't patch your call s ### AI SDK v7 -Use the `@sentry/cloudflare/nodejs_compat` entrypoint and enable the Wrangler `nodejs_compat` flag: +Use the `@sentry/cloudflare/nodejs_compat` entrypoint and enable the Wrangler `nodejs_compat` flag: ```javascript import * as Sentry from "@sentry/cloudflare/nodejs_compat"; @@ -478,7 +478,7 @@ Pass these to `Sentry.vercelAIIntegration()`. The Edge runtime accepts `enableTr -Pass these to `Sentry.vercelAIIntegration()`. The default `@sentry/cloudflare` entrypoint accepts `enableTruncation` only; `nodejs_compat` also accepts `recordInputs` and `recordOutputs`. Neither has module detection to override, so `force` does not apply. +Pass these to `Sentry.vercelAIIntegration()`. The default `@sentry/cloudflare` entrypoint accepts `enableTruncation` only; `nodejs_compat` also accepts `recordInputs` and `recordOutputs`. Neither has module detection to override, so `force` does not apply. diff --git a/docs/platforms/javascript/common/configuration/options.mdx b/docs/platforms/javascript/common/configuration/options.mdx index fa4c36aa39b4d..9942c070a655c 100644 --- a/docs/platforms/javascript/common/configuration/options.mdx +++ b/docs/platforms/javascript/common/configuration/options.mdx @@ -32,7 +32,7 @@ you can provide the ID with this option. The organization ID is used for trace p -It is also used for features like strict trace continuation. +It is also used for features like strict trace continuation. @@ -267,7 +267,7 @@ Set this option to `true` to add stack local variables to stack traces. -For more advanced configuration options, see the documentation on the Local Variables integration options. +For more advanced configuration options, see the documentation on the Local Variables integration options. @@ -642,7 +642,7 @@ A list of strings or regex patterns matching spans that shouldn't be sent to Sen If a matching span is a transaction or service span, the entire local trace will be dropped. If a child span matches, its children will be reparented to the dropped span's parent span. By default, no spans are ignored. -In stream mode, `ignoreSpans` is evaluated at span start, so only the span name and attributes available at that point are taken into account. Any name updates or additional attributes added while the span is active won't influence whether the span is dropped. +In stream mode, `ignoreSpans` is evaluated at span start, so only the span name and attributes available at that point are taken into account. Any name updates or additional attributes added while the span is active won't influence whether the span is dropped. @@ -737,7 +737,7 @@ Controls how spans are sent to Sentry: You don't need to use this option if you're using a browser-based SDK (for example, React or Vue) or a framework SDK that handles client-side rendering (for example Next.js or Remix). -Instead, enable stream mode by adding `spanStreamingIntegration` to your integrations when initializing the SDK. +Instead, enable stream mode by adding `spanStreamingIntegration` to your integrations when initializing the SDK. @@ -819,8 +819,8 @@ This option is required to enable profiling (default is `0`). Determines how profiling sessions are controlled. It has two modes: -- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the profiling API documentation. -- `'trace'`: Profiling starts and stops automatically with transactions (or service spans if you're using stream mode), as long as tracing is enabled. The profiler runs as long as there is at least one sampled transaction. In this mode, profiling is affected by both `profileSessionSampleRate` and your tracing sample rate (`tracesSampleRate` or `tracesSampler`). +- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the profiling API documentation. +- `'trace'`: Profiling starts and stops automatically with transactions (or service spans if you're using stream mode), as long as tracing is enabled. The profiler runs as long as there is at least one sampled transaction. In this mode, profiling is affected by both `profileSessionSampleRate` and your tracing sample rate (`tracesSampleRate` or `tracesSampler`). @@ -858,7 +858,7 @@ This option is required to enable profiling (default is `0`). Determines how profiling sessions are controlled. It has two modes: -- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the profiling API documentation. +- `'manual'` (default): You control when profiling starts and stops using the `startProfiler()` and `stopProfiler()` functions. In this mode, profile sampling is only affected by `profileSessionSampleRate`. Read more about these functions in the profiling API documentation. - `'trace'`: Profiling starts and stops automatically with transactions, as long as tracing is enabled. The profiler runs as long as there is at least one sampled transaction. In this mode, profiling is affected by both `profileSessionSampleRate` and your tracing sample rate (`tracesSampleRate` or `tracesSampler`). diff --git a/docs/platforms/javascript/common/configuration/tree-shaking.mdx b/docs/platforms/javascript/common/configuration/tree-shaking.mdx index e3d50897086c4..c9382d1c2b5bf 100644 --- a/docs/platforms/javascript/common/configuration/tree-shaking.mdx +++ b/docs/platforms/javascript/common/configuration/tree-shaking.mdx @@ -105,15 +105,15 @@ Replacing this flag with `false` will tree shake any SDK code that's related to `__RRWEB_EXCLUDE_IFRAME__` -Replacing this flag with `true` will tree shake any SDK code related to capturing iframe content with Session Replay. It's only relevant when using Session Replay. Enable this flag if you don't want to record any iframes. This has no effect if you did not add `replayIntegration`. +Replacing this flag with `true` will tree shake any SDK code related to capturing iframe content with Session Replay. It's only relevant when using Session Replay. Enable this flag if you don't want to record any iframes. This has no effect if you did not add `replayIntegration`. `__RRWEB_EXCLUDE_SHADOW_DOM__` -Replacing this flag with `true` will tree shake any SDK code related to capturing shadow dom elements with Session Replay. It's only relevant when using Session Replay. Enable this flag if you don't want to record any shadow dom elements. This has no effect if you didn't add `replayIntegration`. +Replacing this flag with `true` will tree shake any SDK code related to capturing shadow dom elements with Session Replay. It's only relevant when using Session Replay. Enable this flag if you don't want to record any shadow dom elements. This has no effect if you didn't add `replayIntegration`. `__SENTRY_EXCLUDE_REPLAY_WORKER__` -Replacing this flag with `true` will tree shake any SDK code that's related to the included compression web worker for Session Replay. It's only relevant when using Session Replay. Enable this flag if you want to host a compression worker yourself. See Using a Custom Compression Worker for details. **We don't recommend enabling this flag unless you provide a custom worker URL.** This has no effect if you did not add `replayIntegration`. +Replacing this flag with `true` will tree shake any SDK code that's related to the included compression web worker for Session Replay. It's only relevant when using Session Replay. Enable this flag if you want to host a compression worker yourself. See Using a Custom Compression Worker for details. **We don't recommend enabling this flag unless you provide a custom worker URL.** This has no effect if you did not add `replayIntegration`. 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 8908fab2448c0..c1f7596b6dfc7 100644 --- a/docs/platforms/javascript/common/data-management/data-collected/index.mdx +++ b/docs/platforms/javascript/common/data-management/data-collected/index.mdx @@ -121,14 +121,14 @@ Without `dataCollection` (and with `sendDefaultPii` unset or `false`), Sentry on By default, SDKs set up by the Sentry CLI Wizard (`@sentry/wizard`) will enable uploading source maps to Sentry. -To disable source map upload, see the Source Maps documentation. +To disable source map upload, see the Source Maps documentation. ## Local Variables In Stack Trace 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 @@ -144,9 +144,9 @@ By default, the Sentry SDK sends information about the device and runtime to Sen 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 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 GPU Context Integration collects GPU information. It can optionally collect more detailed information if the `infoLevel` option is set to `complete`. diff --git a/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx index 5bd35032a55e4..f67e5c9c2d91c 100644 --- a/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/javascript/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/javascript/common/install/esm-without-import.mdx b/docs/platforms/javascript/common/install/esm-without-import.mdx index a1a742bb750f5..87e81c8958652 100644 --- a/docs/platforms/javascript/common/install/esm-without-import.mdx +++ b/docs/platforms/javascript/common/install/esm-without-import.mdx @@ -18,7 +18,7 @@ supported: -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). +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 diff --git a/docs/platforms/javascript/common/migration/v7-to-v8/v8-new-performance-api.mdx b/docs/platforms/javascript/common/migration/v7-to-v8/v8-new-performance-api.mdx index d04d6ea041e19..0c12c50720b13 100644 --- a/docs/platforms/javascript/common/migration/v7-to-v8/v8-new-performance-api.mdx +++ b/docs/platforms/javascript/common/migration/v7-to-v8/v8-new-performance-api.mdx @@ -256,7 +256,7 @@ Sentry.startSpan((span: Span) => { ### Forcing a sampling decision Previously in v7, you could force a positive or negative sampling decision when calling `startTransaction` by setting the `sampled` option. -This would effectively override your sampling configuration for the specific transaction. +This would effectively override your sampling configuration for the specific transaction. In v8, the `sampled` option was removed to align with OpenTelemetry. You can still force a decision by defining a `tracesSampler` callback in `Sentry.init` and returning `1` or `0` for specific spans: diff --git a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx index 81013bd3537cd..7251837b4fe8d 100644 --- a/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx +++ b/docs/platforms/javascript/common/opentelemetry/custom-setup.mdx @@ -70,7 +70,7 @@ In order for the Sentry SDK to work as expected, and for it to be in sync with O together. (For example, if you want to connect the frontend and backend, or different backend services.) This makes it possible to see related errors across services.{" "} - + Learn more about Trace Propagation. @@ -182,7 +182,7 @@ Additionally, there are a few pitfalls that can very simply be avoided by regist ]} > - + Learn more about ESM installation methods. diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx index f8ff311a547b1..8d502e10c6c14 100644 --- a/docs/platforms/javascript/common/session-replay/index.mdx +++ b/docs/platforms/javascript/common/session-replay/index.mdx @@ -36,7 +36,7 @@ Session Replay is no longer supported in `@sentry/capacitor` as of version 4.0.0 [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. -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 Session Replay Privacy. +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 Session Replay Privacy. @@ -206,7 +206,7 @@ If you're unable to update your CSP policy to allow inline web workers, you can ### React Component Names If you want to capture react component names in Sentry, you'll need to configure [React component name - capturing](/platforms/javascript/guides/react/features/component-names). This + capturing](/platforms/javascript/guides/react/features/component-names/). This will allow you to identify elements by the component name instead of the selector. The component names are searchable and will be surfaced in breadcrumbs, rage clicks, and dead clicks. diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/ionic-capacitor.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/ionic-capacitor.mdx index f24a9e180d050..2bede280e9303 100644 --- a/docs/platforms/javascript/common/sourcemaps/uploading/ionic-capacitor.mdx +++ b/docs/platforms/javascript/common/sourcemaps/uploading/ionic-capacitor.mdx @@ -155,7 +155,7 @@ sentry-cli sourcemaps upload --release= /path/to/directory/ios/App Running `upload` with `--release` **doesn't automatically create a release in Sentry**. -Either wait until the first event with the new release set in `Sentry.init` is sent to Sentry, or create a release with the same name in a separate step [with the CLI](/cli/releases). +Either wait until the first event with the new release set in `Sentry.init` is sent to Sentry, or create a release with the same name in a separate step [with the CLI](/cli/releases/). 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 0652af1d6d781..e577b0acfaf6f 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 @@ -58,7 +58,7 @@ Your server's exact configuration will depend on your setup, but the important p ### W3C traceparent header -If you set `propagateTraceparent` option to `true`, you also need to allow the `traceparent` header: +If you set `propagateTraceparent` option to `true`, you also need to allow the `traceparent` header: ``` Access-Control-Allow-Headers: sentry-trace, baggage, traceparent diff --git a/docs/platforms/javascript/common/tracing/distributed-tracing/index.mdx b/docs/platforms/javascript/common/tracing/distributed-tracing/index.mdx index 6e5d727febc5f..3fc06d0be0b77 100644 --- a/docs/platforms/javascript/common/tracing/distributed-tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/distributed-tracing/index.mdx @@ -43,8 +43,8 @@ Remember that in order to propagate trace information through your whole distrib In the browser, the SDK automatically starts a new trace in the following situations: -- On page load: Whenever the page is (re-)loaded, a new trace is started. At the same time, a `pageload` span is created (see Performance Monitoring). Once this span ends, the trace remains until the next navigation or page load. In case the server serving the initial page already started a trace and sent the necessary [HTML tags](./custom-instrumentation/#extract-tracing-information-from-html-meta-tags) to the browser, the SDK will continue this trace instead of starting a new one. -- On navigation: Whenever a user navigates (for example in a single-page application), a new trace is started. At the same time, a `navigation` span is created (see Performance Monitoring). Once this span ends, the trace remains until the next navigation or page load. +- On page load: Whenever the page is (re-)loaded, a new trace is started. At the same time, a `pageload` span is created (see Performance Monitoring). Once this span ends, the trace remains until the next navigation or page load. In case the server serving the initial page already started a trace and sent the necessary [HTML tags](./custom-instrumentation/#extract-tracing-information-from-html-meta-tags) to the browser, the SDK will continue this trace instead of starting a new one. +- On navigation: Whenever a user navigates (for example in a single-page application), a new trace is started. At the same time, a `navigation` span is created (see Performance Monitoring). Once this span ends, the trace remains until the next navigation or page load. In both cases, this means that if you start spans after the automatic `pageload` and `navigation` spans ended, they will still be part of the same trace. This makes it easy to connect what happened before and after your span. diff --git a/docs/platforms/javascript/common/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx index cbf9eabe35570..d7dd2de0b571e 100644 --- a/docs/platforms/javascript/common/tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/index.mdx @@ -100,7 +100,7 @@ If you leave your sample rate at `1.0`, a transaction will be sent every time a ## Automatic Instrumentation -See Automatic Instrumentation to learn about all the things that the SDK automatically instruments for you. +See Automatic Instrumentation to learn about all the things that the SDK automatically instruments for you. diff --git a/docs/platforms/javascript/common/tracing/troubleshooting/index.mdx b/docs/platforms/javascript/common/tracing/troubleshooting/index.mdx index a28f9f8e05e35..45174deba21b0 100644 --- a/docs/platforms/javascript/common/tracing/troubleshooting/index.mdx +++ b/docs/platforms/javascript/common/tracing/troubleshooting/index.mdx @@ -37,7 +37,7 @@ See Streamed Spans fo ## `ignoreSpans` Rules No Longer Work As Expected After Migrating to Stream Mode -In stream mode, `ignoreSpans` is evaluated at span start rather than at transaction end as in transaction mode. This means rules that match on names and attributes added or updated while a span is active may no longer match the intended spans. Review your `ignoreSpans` rules after migrating to make sure the names and attributes you're matching on are available when the span is created. +In stream mode, `ignoreSpans` is evaluated at span start rather than at transaction end as in transaction mode. This means rules that match on names and attributes added or updated while a span is active may no longer match the intended spans. Review your `ignoreSpans` rules after migrating to make sure the names and attributes you're matching on are available when the span is created. If you're auto-instrumenting and don't know what the initial name of a span is when it starts, enable SDK debug logging during development by setting `debug: true` when initializing the SDK. diff --git a/docs/platforms/javascript/common/troubleshooting/index.mdx b/docs/platforms/javascript/common/troubleshooting/index.mdx index 21a367349d432..83e7037a33a77 100644 --- a/docs/platforms/javascript/common/troubleshooting/index.mdx +++ b/docs/platforms/javascript/common/troubleshooting/index.mdx @@ -510,7 +510,7 @@ export default defineConfig({ permalink title="Invalid hashes in Angular Service Worker ngsw.json" > -If you upload source maps for your Angular application with Sentry CLI, you might encounter caching issues if you use the [Angular service worker](https://angular.dev/ecosystem/service-workers). +If you upload source maps for your Angular application with Sentry CLI, you might encounter caching issues if you use the [Angular service worker](https://angular.dev/ecosystem/service-workers). Learn more about fixing these caching issues in the Uploading Source Maps with Sentry CLI guide. @@ -555,7 +555,7 @@ shamefully-hoist=true After adding `sentry.server.config.ts` and building the project, you might get an error like this: `Failed to register ESM hook import-in-the-middle/hook.mjs`. You can add an override (npm/pnpm) or a resolution (yarn) - for `@vercel/nft` to fix this. This will add the `hook.mjs` file to your build output. See the [underlying issue in the UnJS Nitro project](https://github.com/unjs/nitro/issues/2703). + for `@vercel/nft` to fix this. This will add the `hook.mjs` file to your build output. See the [underlying issue in the UnJS Nitro project](https://github.com/nitrojs/nitro/issues/2703). Nitro updated `@vercel/nft` in Nitro version `2.10.0`, so you might not get this error anymore, and you don't need to add this override/resolution. @@ -600,7 +600,7 @@ shamefully-hoist=true Currently, trace collection is only supported when building and running the application. Development mode (`nuxt dev`) is currently not supported. When running the build output, Sentry needs to be initialized before running the rest of the application. This is done automatically, but might not work for your use case. - Read more about this in installation methods. + Read more about this in installation methods. --- diff --git a/docs/platforms/javascript/common/user-feedback/index.mdx b/docs/platforms/javascript/common/user-feedback/index.mdx index 5812d3088c60c..cd0729953e45b 100644 --- a/docs/platforms/javascript/common/user-feedback/index.mdx +++ b/docs/platforms/javascript/common/user-feedback/index.mdx @@ -41,7 +41,7 @@ On SDK version 8.0.0 and above, users can send screenshots with their feedback. Screenshots use your [attachments - quota](/pricing/quotas/manage-attachments-quota). All plans come with 1GB of + quota](/pricing/quotas/manage-attachments-quota/). All plans come with 1GB of attachments, which is approximately 2500 screenshots. diff --git a/docs/platforms/javascript/guides/angular/index.mdx b/docs/platforms/javascript/guides/angular/index.mdx index 03c173d8ef95b..ec1411534086b 100644 --- a/docs/platforms/javascript/guides/angular/index.mdx +++ b/docs/platforms/javascript/guides/angular/index.mdx @@ -17,7 +17,7 @@ You need: -If you're using Angular 16 or older, install and Set Up the SDK Manually. The Sentry Angular SDK still works for Angular versions 14 and newer but the installation wizards requires +If you're using Angular 16 or older, install and Set Up the SDK Manually. The Sentry Angular SDK still works for Angular versions 14 and newer but the installation wizards requires at least Angular 17. @@ -95,14 +95,14 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Make use of Angular-specific features -- Learn how to manually capture errors +- Continue to customize your configuration +- Make use of Angular-specific features +- Learn how to manually capture errors -- If you encountered issues with our installation wizard, try setting up Sentry manually -- Find various topics in Troubleshooting +- If you encountered issues with our installation wizard, try setting up Sentry manually +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/angular/manual-setup.mdx b/docs/platforms/javascript/guides/angular/manual-setup.mdx index e3636e578812a..408985c05b248 100644 --- a/docs/platforms/javascript/guides/angular/manual-setup.mdx +++ b/docs/platforms/javascript/guides/angular/manual-setup.mdx @@ -6,7 +6,7 @@ description: "Learn how to set up the Sentry Angular SDK manually." For the fastest setup, we recommend using the [wizard - installer](/platforms/javascript/guides/angular). + installer](/platforms/javascript/guides/angular/). If you can't (or prefer not to) use the installation wizard, follow the instructions below to configure the Sentry Angular SDK in your application. This guide is also useful to adjust the pre-set configuration if you used the installation wizard for automatic setup. @@ -65,7 +65,7 @@ If you're using an older version of Angular, you also need to use an older versi | 12 or 13 | `@sentry/angular-ivy@^7` (see [Note](#what-is-sentryangular-ivy)) \* | | 10 or 11 | `@sentry/angular@^7` \* | | 9 and below | `@sentry/angular@^6` \* | -| AngularJS/1.x | `@sentry/browser@^6` with the [AngularJS integration](/platforms/javascript/guides/angular/angular1) \* | +| AngularJS/1.x | `@sentry/browser@^6` with the [AngularJS integration](/platforms/javascript/guides/angular/angular1/) \* | \* These versions of the SDK are no longer maintained or tested. Version 7 might still receive bug fixes but we don't guarantee support. @@ -495,14 +495,14 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Make use of Angular-specific features -- Learn how to manually capture errors +- Continue to customize your configuration +- Make use of Angular-specific features +- Learn how to manually capture errors - If you encountered issues with setting up Sentry manually, [try our installation wizard](/platforms/javascript/guides/angular/) -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v7.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v7.x.mdx index 644a543016eef..13df335005a93 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v7.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v7.x.mdx @@ -8,7 +8,7 @@ noindex: true og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v7.x.png --- -The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/serverless` with `npm` or `yarn` manually. +The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html) instead of adding `@sentry/serverless` with `npm` or `yarn` manually. If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it. diff --git a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx index 61e109a9aa73e..193e4ee563f6d 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/layer__v8.x.mdx @@ -8,13 +8,13 @@ noindex: true og_image: /og-images/platforms-javascript-guides-aws-lambda-install-layer__v8.x.png --- -The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/Lambda/latest/dg/configuration-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](/platforms/javascript/guides/aws-lambda/install/npm). +The easiest way to get started with Sentry is to use the Sentry [Lambda Layer](https://docs.aws.amazon.com/lambda/latest/dg/chapter-layers.html) instead of adding `@sentry/aws-serverless` with `npm` or `yarn` [manually](/platforms/javascript/guides/aws-lambda/install/npm/). If you follow this guide, you don't have to worry about deploying Sentry dependencies alongside your function code. To actually start the SDK, you can decide between setting up the SDK using environment variables or in your Lambda function code. We recommend using environment variables as it's the easiest way to get started. [Initializing the SDK in code](#alternative-initialize-the-sdk-in-code) instead of setting environment variables gives you more control over the SDK setup if you need it. -This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](/platforms/javascript/guides/aws-lambda/install/npm). +This installation method **does not** work with Lambda functions running in EcmaScript Modules (ESM) mode, using `import` syntax. If you're running your function in ESM, follow the [ESM guide](/platforms/javascript/guides/aws-lambda/install/npm/). diff --git a/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx b/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx index 299f2cfe35be4..203839ba8e73f 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx @@ -11,7 +11,7 @@ In this guide you will learn how to set up the `@sentry/aws-serverless` SDK for We recommend starting the SDK automatically via environment variables so that you only have to make minimal code changes to your lambda function. If you need more control over the SDK setup, you can also [initialize the SDK in code](#option-b-manual-setup). -However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, use the [Lambda Layer](/platforms/javascript/guides/aws-lambda/install/layer) instead. +However, you need to modify your code and deploy the Sentry dependencies alongside your function code. If you're looking for the most simple way to set up Sentry, use the [Lambda Layer](/platforms/javascript/guides/aws-lambda/install/layer/) instead. ## 1. Prerequisites diff --git a/docs/platforms/javascript/guides/aws-lambda/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/javascript/guides/aws-lambda/tracing/instrumentation/automatic-instrumentation.mdx index 9390336d15504..73c31f4ac255f 100644 --- a/docs/platforms/javascript/guides/aws-lambda/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/tracing/instrumentation/automatic-instrumentation.mdx @@ -19,7 +19,7 @@ Database instrumentation can be manually enabled by adding the corresponding int - `mongo` - `mongoose` - `ioredis` -- `prisma` (requires additional configuration - see Prisma Integration) +- `prisma` (requires additional configuration - see Prisma Integration) You can add the integrations as follows: diff --git a/docs/platforms/javascript/guides/azure-functions/index.mdx b/docs/platforms/javascript/guides/azure-functions/index.mdx index 140b666d002e7..68f124e540706 100644 --- a/docs/platforms/javascript/guides/azure-functions/index.mdx +++ b/docs/platforms/javascript/guides/azure-functions/index.mdx @@ -238,12 +238,12 @@ At this point, you should have integrated Sentry into your Azure Function and sh Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors - Get familiar with [Sentry's product features](/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/bun/index.mdx b/docs/platforms/javascript/guides/bun/index.mdx index 63610ff3db377..df9b2a69b16a3 100644 --- a/docs/platforms/javascript/guides/bun/index.mdx +++ b/docs/platforms/javascript/guides/bun/index.mdx @@ -205,13 +205,13 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your frontend using one of our [frontend SDKs](/) -- Learn how to manually capture errors -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/capacitor/index.mdx b/docs/platforms/javascript/guides/capacitor/index.mdx index e7fa8c2588ce5..5e564dd24bd67 100644 --- a/docs/platforms/javascript/guides/capacitor/index.mdx +++ b/docs/platforms/javascript/guides/capacitor/index.mdx @@ -98,7 +98,7 @@ If you're using Angular, React, Vue, or Nuxt, make sure to forward the `init` me ### Provide Native Debug Information for iOS (Optional) -You need to provide debug information to Sentry to make the stack-trace information for native crashes on iOS easier to understand. You can provide debug information by [uploading dSYM files](/platforms/javascript/guides/capacitor/dsym). +You need to provide debug information to Sentry to make the stack-trace information for native crashes on iOS easier to understand. You can provide debug information by [uploading dSYM files](/platforms/javascript/guides/capacitor/dsym/). ## Verify @@ -314,13 +314,13 @@ At this point, you should have integrated Sentry into your Capacitor application Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to use Sentry with Ionic -- Continue to customize your configuration -- Learn how to manually capture errors +- Learn how to use Sentry with Ionic +- Continue to customize your configuration +- Learn how to manually capture errors - Make use of framework-specific features, such as [Angular](/platforms/javascript/guides/angular/features/), [Vue](/platforms/javascript/guides/vue/features/), [React](/platforms/javascript/guides/react/features/), or [Nuxt](/platforms/javascript/guides/nuxt/features/) -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/cloudflare/configuration/integrations/prisma.mdx b/docs/platforms/javascript/guides/cloudflare/configuration/integrations/prisma.mdx index febbd812a4af1..6576c7a5707d0 100644 --- a/docs/platforms/javascript/guides/cloudflare/configuration/integrations/prisma.mdx +++ b/docs/platforms/javascript/guides/cloudflare/configuration/integrations/prisma.mdx @@ -5,7 +5,7 @@ description: "Adds instrumentation for Prisma ORM queries on Cloudflare Workers -On Cloudflare, the `prismaIntegration` is only available through the `@sentry/cloudflare/nodejs_compat` entrypoint, which requires SDK version `10.64.0` or higher. +On Cloudflare, the `prismaIntegration` is only available through the `@sentry/cloudflare/nodejs_compat` entrypoint, which requires SDK version `10.64.0` or higher. diff --git a/docs/platforms/javascript/guides/cloudflare/features/durableobject.mdx b/docs/platforms/javascript/guides/cloudflare/features/durableobject.mdx index eb43577074881..7bf372acd7c3b 100644 --- a/docs/platforms/javascript/guides/cloudflare/features/durableobject.mdx +++ b/docs/platforms/javascript/guides/cloudflare/features/durableobject.mdx @@ -38,4 +38,4 @@ The SDK also filters out framework-internal storage operations (version 10.69.0 ## RPC Trace Propagation -To enable distributed tracing across RPC calls to your Durable Objects, see Distributed Tracing. +To enable distributed tracing across RPC calls to your Durable Objects, see Distributed Tracing. diff --git a/docs/platforms/javascript/guides/cloudflare/features/nodejs-compat.mdx b/docs/platforms/javascript/guides/cloudflare/features/nodejs-compat.mdx index 15019bda43139..60dda045c9f4f 100644 --- a/docs/platforms/javascript/guides/cloudflare/features/nodejs-compat.mdx +++ b/docs/platforms/javascript/guides/cloudflare/features/nodejs-compat.mdx @@ -15,8 +15,8 @@ The `@sentry/cloudflare/nodejs_compat` entrypoint requires SDK version `10.64.0` The `/nodejs_compat` entrypoint enables Node.js-only integrations and features on Cloudflare, including: -- The `prismaIntegration` for tracing Prisma ORM queries. -- Vercel AI SDK v7 support for the `vercelAIIntegration`. +- The `prismaIntegration` for tracing Prisma ORM queries. +- Vercel AI SDK v7 support for the `vercelAIIntegration`. ## Usage diff --git a/docs/platforms/javascript/guides/cloudflare/frameworks/hydrogen-react-router.mdx b/docs/platforms/javascript/guides/cloudflare/frameworks/hydrogen-react-router.mdx index 563b5b394bda7..78c0ae801ac78 100644 --- a/docs/platforms/javascript/guides/cloudflare/frameworks/hydrogen-react-router.mdx +++ b/docs/platforms/javascript/guides/cloudflare/frameworks/hydrogen-react-router.mdx @@ -480,14 +480,14 @@ At this point, you should have integrated Sentry into your React Router Framewor Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: -- Explore [practical guides](/guides) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration +- Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup +- Learn how to manually capture errors +- Continue to customize your configuration - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/cloudflare/frameworks/tanstack-start.mdx b/docs/platforms/javascript/guides/cloudflare/frameworks/tanstack-start.mdx index 47f889863e9d2..03ff997cc3a00 100644 --- a/docs/platforms/javascript/guides/cloudflare/frameworks/tanstack-start.mdx +++ b/docs/platforms/javascript/guides/cloudflare/frameworks/tanstack-start.mdx @@ -287,13 +287,13 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Learn how to [manually capture errors](/platforms/javascript/guides/cloudflare/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/cloudflare/configuration/) -- Make use of [Cloudflare-specific features](/platforms/javascript/guides/cloudflare/features) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Make use of [Cloudflare-specific features](/platforms/javascript/guides/cloudflare/features/) +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - Check out setup instructions for other popular [frameworks on Cloudflare](/platforms/javascript/guides/cloudflare/frameworks/) -- Find various support topics in troubleshooting +- Find various support topics in troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/cloudflare/index.mdx b/docs/platforms/javascript/guides/cloudflare/index.mdx index 274a5dea6a27d..c9282083afee9 100644 --- a/docs/platforms/javascript/guides/cloudflare/index.mdx +++ b/docs/platforms/javascript/guides/cloudflare/index.mdx @@ -433,13 +433,13 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/cloudflare/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/cloudflare/configuration/) -- Make use of [Cloudflare-specific features](/platforms/javascript/guides/cloudflare/features) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Make use of [Cloudflare-specific features](/platforms/javascript/guides/cloudflare/features/) +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - Check out setup instructions for popular [frameworks on Cloudflare](/platforms/javascript/guides/cloudflare/frameworks/) -- Find various support topics in troubleshooting +- Find various support topics in troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/cordova/index.mdx b/docs/platforms/javascript/guides/cordova/index.mdx index 0c3400742cd6f..1a15864cc3bc0 100644 --- a/docs/platforms/javascript/guides/cordova/index.mdx +++ b/docs/platforms/javascript/guides/cordova/index.mdx @@ -33,7 +33,7 @@ using [Sentry Capacitor](/platforms/javascript/guides/capacitor/), [Sentry React - On-device symbolication for JavaScript (in `Debug` mode) - [Ionic support](/platforms/javascript/guides/cordova/ionic/) - Under the hood, the SDK relies on our [JavaScript SDK](/platforms/javascript/), which makes all functions available for JavaScript also available in this SDK ,including: - - [Tracing](/platforms/javascript/guides/cordova/performance/instrumentation/custom-instrumentation) to create transactions + - [Tracing](/platforms/javascript/guides/cordova/performance/instrumentation/custom-instrumentation/) to create transactions @@ -56,7 +56,7 @@ The wizard helps configure your project by: - Linking your Sentry account and project - Adding a build step to Xcode to upload debug symbols for iOS crashes -- Configuring source map uploads so you can see your original JavaScript code in Sentry instead of minified production code +- Configuring source map uploads so you can see your original JavaScript code in Sentry instead of minified production code @@ -151,10 +151,10 @@ At this point, you should have integrated Sentry into your Cordova application a Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to upload debug symbols to make sure your native stack traces are readable +- Continue to customize your configuration +- Learn how to upload debug symbols to make sure your native stack traces are readable - Check our [Ionic support guide](/platforms/javascript/guides/cordova/ionic/) -- Learn how to manually capture errors +- Learn how to manually capture errors - If you are experiencing errors and want to remove unused architectures from your binary when submitting the build to iTunes Connect, you can use the scripts provided in [Troubleshooting](/platforms/javascript/guides/cordova/troubleshooting/). diff --git a/docs/platforms/javascript/guides/deno/index.mdx b/docs/platforms/javascript/guides/deno/index.mdx index 470b6cf9fd801..d26299d251bfe 100644 --- a/docs/platforms/javascript/guides/deno/index.mdx +++ b/docs/platforms/javascript/guides/deno/index.mdx @@ -223,13 +223,13 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your frontend using one of our [frontend SDKs](/) -- Learn how to manually capture errors -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/effect/index.mdx b/docs/platforms/javascript/guides/effect/index.mdx index e77b39975489f..6739e607ab092 100644 --- a/docs/platforms/javascript/guides/effect/index.mdx +++ b/docs/platforms/javascript/guides/effect/index.mdx @@ -405,7 +405,7 @@ Now, head over to your project on [Sentry.io](https://sentry.io/) to view the co -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/electron/configuration/integrations/browserwindowsession.mdx b/docs/platforms/javascript/guides/electron/configuration/integrations/browserwindowsession.mdx index 0256b5ea97036..b7966a4bcfff6 100644 --- a/docs/platforms/javascript/guides/electron/configuration/integrations/browserwindowsession.mdx +++ b/docs/platforms/javascript/guides/electron/configuration/integrations/browserwindowsession.mdx @@ -11,7 +11,7 @@ Captures sessions linked to the focus of Electron `BrowserWindow`s. Capturing sessions makes it possible to show [release health](/product/releases/health/) statistics in Sentry. -Adding this integration disables the MainProcessSession +Adding this integration disables the MainProcessSession session integration. diff --git a/docs/platforms/javascript/guides/electron/configuration/integrations/mainprocesssession.mdx b/docs/platforms/javascript/guides/electron/configuration/integrations/mainprocesssession.mdx index 6aeea5bbde561..7e5f89912f244 100644 --- a/docs/platforms/javascript/guides/electron/configuration/integrations/mainprocesssession.mdx +++ b/docs/platforms/javascript/guides/electron/configuration/integrations/mainprocesssession.mdx @@ -9,7 +9,7 @@ This integration captures sessions linked to the lifetime of the Electron main p If you'd prefer to capture sessions linked to the focus of `BrowserWindow`, use the BrowserWindowSession +to="/configuration/integrations/browserwindowsession/">BrowserWindowSession integration in the renderer processes. To disable sending sessions, filter the `MainProcessSession` from the default integrations: diff --git a/docs/platforms/javascript/guides/electron/index.mdx b/docs/platforms/javascript/guides/electron/index.mdx index 59a16cac432d8..86daeec6ea1c6 100644 --- a/docs/platforms/javascript/guides/electron/index.mdx +++ b/docs/platforms/javascript/guides/electron/index.mdx @@ -383,14 +383,14 @@ At this point, you should have integrated Sentry into your Electron application Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors -- Make use of Electron-specific features +- Continue to customize your configuration +- Learn how to manually capture errors +- Make use of Electron-specific features - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/elysia/index.mdx b/docs/platforms/javascript/guides/elysia/index.mdx index 66f397a8a7928..79437b6575ffe 100644 --- a/docs/platforms/javascript/guides/elysia/index.mdx +++ b/docs/platforms/javascript/guides/elysia/index.mdx @@ -255,13 +255,13 @@ Finally, head over to your project on [Sentry.io](https://sentry.io/) to view th ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/ember/configuration/ember-options.mdx b/docs/platforms/javascript/guides/ember/configuration/ember-options.mdx index 75210f3a27173..fd7fce754709d 100644 --- a/docs/platforms/javascript/guides/ember/configuration/ember-options.mdx +++ b/docs/platforms/javascript/guides/ember/configuration/ember-options.mdx @@ -24,7 +24,7 @@ ENV["@sentry/ember"] = { }; ``` -The following documentation is for Ember specific configuration, for Sentry options, [see basic options](/platforms/javascript/guides/ember/configuration/options) +The following documentation is for Ember specific configuration, for Sentry options, [see basic options](/platforms/javascript/guides/ember/configuration/options/) ### Tracing Considerations diff --git a/docs/platforms/javascript/guides/firebase/index.mdx b/docs/platforms/javascript/guides/firebase/index.mdx index 3fb5759d70a1c..40a1c75171ae9 100644 --- a/docs/platforms/javascript/guides/firebase/index.mdx +++ b/docs/platforms/javascript/guides/firebase/index.mdx @@ -16,7 +16,7 @@ categories: ## What's Instrumented -The Sentry SDK includes a built-in Firebase integration that automatically instruments: +The Sentry SDK includes a built-in Firebase integration that automatically instruments: - **Cloud Functions** - HTTP functions, background functions, and event triggers - **[Firestore](https://firebase.google.com/docs/firestore)** - Database operations like reads, writes, and queries are instrumented out of the box @@ -271,13 +271,13 @@ At this point, you should have integrated Sentry into your Cloud Functions for F Now's a good time to customize your setup and look into more advanced topics: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/gatsby/index.mdx b/docs/platforms/javascript/guides/gatsby/index.mdx index 989a631ba9825..c1dbecf14bec5 100644 --- a/docs/platforms/javascript/guides/gatsby/index.mdx +++ b/docs/platforms/javascript/guides/gatsby/index.mdx @@ -268,11 +268,11 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/gcp-functions/index.mdx b/docs/platforms/javascript/guides/gcp-functions/index.mdx index b6b393f7a62ff..ad70f4e969e06 100644 --- a/docs/platforms/javascript/guides/gcp-functions/index.mdx +++ b/docs/platforms/javascript/guides/gcp-functions/index.mdx @@ -188,13 +188,13 @@ At this point, you should have integrated Sentry into your Google Cloud Platform Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/hono/index.mdx b/docs/platforms/javascript/guides/hono/index.mdx index bd327f7329461..0d18ca3e5aacc 100644 --- a/docs/platforms/javascript/guides/hono/index.mdx +++ b/docs/platforms/javascript/guides/hono/index.mdx @@ -428,14 +428,14 @@ At this point, you should have Sentry integrated into your Hono application and Now's a good time to customize your setup and look into more advanced topics: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Explore Hono-specific features like custom error filtering -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Explore Hono-specific features like custom error filtering +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/nestjs/index.mdx b/docs/platforms/javascript/guides/nestjs/index.mdx index 488eec35479e8..e99b4b838f0dd 100644 --- a/docs/platforms/javascript/guides/nestjs/index.mdx +++ b/docs/platforms/javascript/guides/nestjs/index.mdx @@ -130,7 +130,7 @@ export class AppModule {} ## Isolate Async Context for Background Jobs (Optional) -If your NestJS app uses background jobs (such as `@Cron()`, `@Interval()`, `@OnEvent()`, or BullMQ), breadcrumbs from those jobs can leak into unrelated HTTP request error events. Wrap your background job handlers with `Sentry.withIsolationScope()` to isolate them. See Isolate Background Job Scopes for details and code examples. +If your NestJS app uses background jobs (such as `@Cron()`, `@Interval()`, `@OnEvent()`, or BullMQ), breadcrumbs from those jobs can leak into unrelated HTTP request error events. Wrap your background job handlers with `Sentry.withIsolationScope()` to isolate them. See Isolate Background Job Scopes for details and code examples. ## Verify Your Setup @@ -155,12 +155,12 @@ Our next recommended steps for you are: - Extend Sentry to your frontend using one of our [frontend SDKs](/) - Learn how to [manually capture errors](/platforms/javascript/guides/nestjs/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/nestjs/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Check out alternative installation methods -- Find various topics in Troubleshooting +- Check out alternative installation methods +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/nestjs/install/esm-without-import.mdx b/docs/platforms/javascript/guides/nestjs/install/esm-without-import.mdx index 3c31674c680bb..502143c0ffd31 100644 --- a/docs/platforms/javascript/guides/nestjs/install/esm-without-import.mdx +++ b/docs/platforms/javascript/guides/nestjs/install/esm-without-import.mdx @@ -11,7 +11,7 @@ supported: [installation methods](../). -When running your application in [ECMAScript Modules](https://nodejs.org/api/esm.html#introduction) (ESM) mode, you'll most likely want to follow the ESM instructions. However, if you want to avoid using the `--import` command line option, for example, if you have no way of configuring a CLI flag, you can also follow an alternative setup that involves importing the `instrument.mjs` file directly in your application. +When running your application in [ECMAScript Modules](https://nodejs.org/api/esm.html#introduction) (ESM) mode, you'll most likely want to follow the ESM instructions. However, if you want to avoid using the `--import` command line option, for example, if you have no way of configuring a CLI flag, you can also follow an alternative setup that involves importing the `instrument.mjs` file directly in your application. diff --git a/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx b/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx index 5216a58eb971f..e961a9c809b92 100644 --- a/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/configuration/build/index.mdx @@ -372,7 +372,7 @@ A list of React component names to exclude from component annotation. -Configuration options for tree shaking. Refer to the [tree shaking documentation](/platforms/javascript/guides/nextjs/configuration/tree-shaking) for more details. +Configuration options for tree shaking. Refer to the [tree shaking documentation](/platforms/javascript/guides/nextjs/configuration/tree-shaking/) for more details. diff --git a/docs/platforms/javascript/guides/nextjs/logs/index.mdx b/docs/platforms/javascript/guides/nextjs/logs/index.mdx index 3c5272c6796ef..59b3005f5ecb6 100644 --- a/docs/platforms/javascript/guides/nextjs/logs/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/logs/index.mdx @@ -226,7 +226,7 @@ Sentry.init({ }); ``` -See Pino integration docs for configuration options. +See Pino integration docs for configuration options. diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx index 0e604cd7b5785..a163970b66a5c 100644 --- a/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx +++ b/docs/platforms/javascript/guides/nextjs/manual-setup/index.mdx @@ -12,7 +12,7 @@ categories: For the fastest setup, we recommend using the [wizard - installer](/platforms/javascript/guides/nextjs). + installer](/platforms/javascript/guides/nextjs/). This guide covers manual setup for **Next.js 15+ with Turbopack and App Router**. For other setups, see: diff --git a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx index e2d95a03f8714..57c4aad2cd394 100644 --- a/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx +++ b/docs/platforms/javascript/guides/nextjs/manual-setup/pages-router.mdx @@ -6,7 +6,7 @@ description: "Manual setup for Next.js applications using the Pages Router." For the fastest setup, we recommend using the [wizard - installer](/platforms/javascript/guides/nextjs). + installer](/platforms/javascript/guides/nextjs/). This guide covers manual setup for **Next.js applications using the Pages Router**. For other setups, see: diff --git a/docs/platforms/javascript/guides/nitro/index.mdx b/docs/platforms/javascript/guides/nitro/index.mdx index c8c6a092bc57b..cec7c582f13f8 100644 --- a/docs/platforms/javascript/guides/nitro/index.mdx +++ b/docs/platforms/javascript/guides/nitro/index.mdx @@ -323,13 +323,13 @@ The SDK is a wrapper around `@sentry/node` and re-exports its full API. All Node ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/nuxt/features/nitro-deployment-presets.mdx b/docs/platforms/javascript/guides/nuxt/features/nitro-deployment-presets.mdx index 852888f39712c..945f878d90816 100644 --- a/docs/platforms/javascript/guides/nuxt/features/nitro-deployment-presets.mdx +++ b/docs/platforms/javascript/guides/nuxt/features/nitro-deployment-presets.mdx @@ -8,4 +8,4 @@ The Sentry Nuxt SDK provides support for different Nitro deployment presets, mos ## Cloudflare Pages -Using the Cloudflare Nitro plugin of Sentry enables Sentry monitoring on Cloudflare Workers and Pages. Go and see the [Cloudflare Nitro plugin documentation](/platforms/javascript/guides/cloudflare/frameworks/nuxt). +Using the Cloudflare Nitro plugin of Sentry enables Sentry monitoring on Cloudflare Workers and Pages. Go and see the [Cloudflare Nitro plugin documentation](/platforms/javascript/guides/cloudflare/frameworks/nuxt/). diff --git a/docs/platforms/javascript/guides/nuxt/index.mdx b/docs/platforms/javascript/guides/nuxt/index.mdx index 13b943b99f447..e4c19b79b232d 100644 --- a/docs/platforms/javascript/guides/nuxt/index.mdx +++ b/docs/platforms/javascript/guides/nuxt/index.mdx @@ -58,7 +58,7 @@ We **recommend testing in production mode** as it most closely resembles your de -After building with `nuxi build`, run your project and make sure to load Sentry on the server side by explicitly adding it via `--import` (read more about this flag in [Installation Methods](/platforms/javascript/guides/nuxt/install)). +After building with `nuxi build`, run your project and make sure to load Sentry on the server side by explicitly adding it via `--import` (read more about this flag in [Installation Methods](/platforms/javascript/guides/nuxt/install/)). @@ -120,7 +120,7 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/nuxt/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/nuxt/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - Learn how to [track your Vue components or your Pinia store](/platforms/javascript/guides/nuxt/features/) - Learn how to [add support for different Nitro deployment presets](/platforms/javascript/guides/nuxt/features/nitro-deployment-presets/) (like Cloudflare) diff --git a/docs/platforms/javascript/guides/nuxt/install/cli-import.mdx b/docs/platforms/javascript/guides/nuxt/install/cli-import.mdx index c36bd401a2362..49270a7808515 100644 --- a/docs/platforms/javascript/guides/nuxt/install/cli-import.mdx +++ b/docs/platforms/javascript/guides/nuxt/install/cli-import.mdx @@ -18,7 +18,7 @@ This will register Sentry's [loader hook](https://nodejs.org/api/module.html#cus - At this time, it isn't possible to properly configure `--import` in **Vercel**. If any of those points apply to you, you cannot use the `--import` flag to initialize Sentry on the server-side. -Check out the guide for using limited server tracing instead. +Check out the guide for using limited server tracing instead. ## Initializing Sentry with `--import` diff --git a/docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx b/docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx index 8a09ed9890077..369669450a34e 100644 --- a/docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx +++ b/docs/platforms/javascript/guides/nuxt/install/dynamic-import.mdx @@ -9,7 +9,7 @@ description: "Learn about how the Nuxt SDK leverages dynamic input() in the buil This installation method doesn't work with more recent versions of Nuxt/Nitro. - We recommend reading the guide for installing the SDK with the CLI flag `--import` or limited server tracing + We recommend reading the guide for installing the SDK with the CLI flag `--import` or limited server tracing The `import()` expression, or dynamic import, enables flexible, conditional module loading in ESM. @@ -48,7 +48,7 @@ As a temporary workaround, you can add the following overrides in your applicati } ``` -You can also check out the guide for installing the SDK with the CLI flag `--import` or limited-server-tracing. +You can also check out the guide for installing the SDK with the CLI flag `--import` or limited-server-tracing. ## Initializing Sentry with Dynamic `import()` diff --git a/docs/platforms/javascript/guides/nuxt/install/limited-server-tracing.mdx b/docs/platforms/javascript/guides/nuxt/install/limited-server-tracing.mdx index 97665847a8761..6aad175e2139f 100644 --- a/docs/platforms/javascript/guides/nuxt/install/limited-server-tracing.mdx +++ b/docs/platforms/javascript/guides/nuxt/install/limited-server-tracing.mdx @@ -7,7 +7,7 @@ description: "Learn how to set up the Nuxt SDK with limited server tracing by ad ## Understanding Limited Server Tracing Sentry needs to be initialized before the rest of the application runs. -If the default way of adding an `--import` CLI flag doesn't work for you, +If the default way of adding an `--import` CLI flag doesn't work for you, enable the SDK to add a top-level `import`. The automatically added top-level `import` will then import the Sentry server-side config at the top of the Nuxt server entry file. diff --git a/docs/platforms/javascript/guides/react-router/index.mdx b/docs/platforms/javascript/guides/react-router/index.mdx index d2e5e1fb1f791..d9c7a356bbaa8 100644 --- a/docs/platforms/javascript/guides/react-router/index.mdx +++ b/docs/platforms/javascript/guides/react-router/index.mdx @@ -23,7 +23,7 @@ categories: -If you're using React Router in data or declarative mode, follow the instructions in our [React guide for v7](/platforms/javascript/guides/react/features/react-router/v7) or [v8](/platforms/javascript/guides/react/features/react-router/v8). +If you're using React Router in data or declarative mode, follow the instructions in our [React guide for v7](/platforms/javascript/guides/react/features/react-router/v7/) or [v8](/platforms/javascript/guides/react/features/react-router/v8/). @@ -245,14 +245,14 @@ Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration +- Learn how to manually capture errors +- Continue to customize your configuration - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - If you encountered issues with our installation wizard, try [setting up Sentry manually](/platforms/javascript/guides/react-router/manual-setup/) -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/react-router/manual-setup.mdx b/docs/platforms/javascript/guides/react-router/manual-setup.mdx index de8e7357d1154..6769eed7d2823 100644 --- a/docs/platforms/javascript/guides/react-router/manual-setup.mdx +++ b/docs/platforms/javascript/guides/react-router/manual-setup.mdx @@ -648,13 +648,13 @@ Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration +- Learn how to manually capture errors +- Continue to customize your configuration - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/react/features/react-router/v6.mdx b/docs/platforms/javascript/guides/react/features/react-router/v6.mdx index 386e9820b3180..263221ec1137c 100644 --- a/docs/platforms/javascript/guides/react/features/react-router/v6.mdx +++ b/docs/platforms/javascript/guides/react/features/react-router/v6.mdx @@ -6,7 +6,7 @@ sidebar_order: 20 -Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that replace the v6-specific ones used on this page. If you're on SDK `10.59.0` or later, we recommend using the [new APIs documented on the React Router v8 page](/platforms/javascript/guides/react/features/react-router/v8), which also work with React Router v6. The v6-specific APIs will be removed in the next major version. +Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that replace the v6-specific ones used on this page. If you're on SDK `10.59.0` or later, we recommend using the [new APIs documented on the React Router v8 page](/platforms/javascript/guides/react/features/react-router/v8/), which also work with React Router v6. The v6-specific APIs will be removed in the next major version. @@ -18,8 +18,8 @@ Apply the following setup steps based on your routing method and create a [custo To instrument your React Router, update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV6BrowserTracingIntegration` within `Sentry.init` and provide the required React hooks and router functions. Then, wrap the router instance created by `createBrowserRouter` or `createMemoryRouter` with one of the following functions: -- Use `Sentry.wrapCreateBrowserRouterV6` for [`createBrowserRouter`](https://reactrouter.com/en/main/routers/create-browser-router) and [`createHashRouter`](https://reactrouter.com/en/main/routers/create-hash-router) -- Use `Sentry.wrapCreateMemoryRouterV6` for [`createMemoryRouter`](https://reactrouter.com/en/main/routers/create-memory-router) (introduced in SDK version `8.50.0`) +- Use `Sentry.wrapCreateBrowserRouterV6` for [`createBrowserRouter`](https://reactrouter.com/v6/routers/create-browser-router) and [`createHashRouter`](https://reactrouter.com/v6/routers/create-hash-router) +- Use `Sentry.wrapCreateMemoryRouterV6` for [`createMemoryRouter`](https://reactrouter.com/v6/routers/create-memory-router) (introduced in SDK version `8.50.0`) ```javascript {2-8, 15-21, 26-34} import React from "react"; @@ -106,7 +106,7 @@ This wrapper is only needed at the top level of your app, unlike React Router v4 _Available in `@sentry/react` version `7.12.1` and above._ -If you specify your route definitions as an object to the [`useRoutes` hook](https://reactrouter.com/en/main/hooks/use-routes), update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV6BrowserTracingIntegration` inside `Sentry.init` and provide the required React hooks and router functions. Then, use `Sentry.wrapUseRoutesV6` to create a patched `useRoutes` hook that instruments your routes with Sentry. +If you specify your route definitions as an object to the [`useRoutes` hook](https://reactrouter.com/v6/hooks/use-routes), update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV6BrowserTracingIntegration` inside `Sentry.init` and provide the required React hooks and router functions. Then, use `Sentry.wrapUseRoutesV6` to create a patched `useRoutes` hook that instruments your routes with Sentry. Call `wrapUseRoutesV6` outside of a React component, as in the example below. We also recommend that you assign the wrapped hook to a variable starting with `use`, as per [React's documentation](https://react.dev/learn/reusing-logic-with-custom-hooks#hook-names-always-start-with-use). diff --git a/docs/platforms/javascript/guides/react/features/react-router/v7.mdx b/docs/platforms/javascript/guides/react/features/react-router/v7.mdx index 8993491577915..11f14a3e65805 100644 --- a/docs/platforms/javascript/guides/react/features/react-router/v7.mdx +++ b/docs/platforms/javascript/guides/react/features/react-router/v7.mdx @@ -11,7 +11,7 @@ sidebar_order: 10 -Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that replace the v7-specific ones used on this page. If you're on SDK `10.59.0` or later, we recommend using the [new APIs documented on the React Router v8 page](/platforms/javascript/guides/react/features/react-router/v8), which also work with React Router v7. The v7-specific APIs will be removed in the next major version. +Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that replace the v7-specific ones used on this page. If you're on SDK `10.59.0` or later, we recommend using the [new APIs documented on the React Router v8 page](/platforms/javascript/guides/react/features/react-router/v8/), which also work with React Router v7. The v7-specific APIs will be removed in the next major version. @@ -25,8 +25,8 @@ automatically captures rendering errors: To instrument your React Router, update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV7BrowserTracingIntegration` within `Sentry.init` and provide the required React hooks and router functions. Then, wrap the router instance created by `createBrowserRouter` or `createMemoryRouter` with one of the following functions: -- Use `Sentry.wrapCreateBrowserRouterV7` for [`createBrowserRouter`](https://reactrouter.com/en/main/routers/create-browser-router) and [`createHashRouter`](https://reactrouter.com/en/main/routers/create-hash-router) -- Use `Sentry.wrapCreateMemoryRouterV7` for [`createMemoryRouter`](https://reactrouter.com/en/main/routers/create-memory-router) (introduced in SDK version `8.50.0`) +- Use `Sentry.wrapCreateBrowserRouterV7` for [`createBrowserRouter`](https://reactrouter.com/v6/routers/create-browser-router) and [`createHashRouter`](https://reactrouter.com/v6/routers/create-hash-router) +- Use `Sentry.wrapCreateMemoryRouterV7` for [`createMemoryRouter`](https://reactrouter.com/v6/routers/create-memory-router) (introduced in SDK version `8.50.0`) ```javascript {2-8, 15-21, 26-34} import React from "react"; @@ -111,7 +111,7 @@ This wrapper is only needed at the top level of your app, unlike React Router v4 ## Usage With `useRoutes` Hook -If you specify your route definitions as an object to the [`useRoutes` hook](https://reactrouter.com/en/main/hooks/use-routes), update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV7BrowserTracingIntegration` inside `Sentry.init` and provide the required React hooks and router functions. Then, use `Sentry.wrapUseRoutesV7` to create a patched `useRoutes` hook that instruments your routes with Sentry. +If you specify your route definitions as an object to the [`useRoutes` hook](https://reactrouter.com/v6/hooks/use-routes), update your `Sentry.browserTracingIntegration` to `Sentry.reactRouterV7BrowserTracingIntegration` inside `Sentry.init` and provide the required React hooks and router functions. Then, use `Sentry.wrapUseRoutesV7` to create a patched `useRoutes` hook that instruments your routes with Sentry. Call `wrapUseRoutesV7` outside of a React component, as in the example below. We also recommend that you assign the wrapped hook to a variable starting with `use`, as per [React's documentation](https://react.dev/learn/reusing-logic-with-custom-hooks#hook-names-always-start-with-use). diff --git a/docs/platforms/javascript/guides/react/features/react-router/v8.mdx b/docs/platforms/javascript/guides/react/features/react-router/v8.mdx index 1d1acb3dc196a..c30c5c4cd9dc0 100644 --- a/docs/platforms/javascript/guides/react/features/react-router/v8.mdx +++ b/docs/platforms/javascript/guides/react/features/react-router/v8.mdx @@ -18,7 +18,7 @@ If you're using React Router v8 in framework mode, check out the [React Router F -Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that work with React Router v6, v7, and v8. If you're using React Router v6 or v7, you can also use these APIs instead of the version-specific ones documented on the [v6](/platforms/javascript/guides/react/features/react-router/v6) and [v7](/platforms/javascript/guides/react/features/react-router/v7) pages. +Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that work with React Router v6, v7, and v8. If you're using React Router v6 or v7, you can also use these APIs instead of the version-specific ones documented on the [v6](/platforms/javascript/guides/react/features/react-router/v6/) and [v7](/platforms/javascript/guides/react/features/react-router/v7/) pages. @@ -28,8 +28,8 @@ Starting with SDK version `10.59.0`, Sentry provides version-agnostic APIs that To instrument your React Router, use `Sentry.reactRouterBrowserTracingIntegration` within `Sentry.init` and provide the required React hooks and router functions. Then, wrap the router instance created by `createBrowserRouter` or `createMemoryRouter` with one of the following functions: -- Use `Sentry.wrapCreateBrowserRouter` for [`createBrowserRouter`](https://reactrouter.com/api/router-components/BrowserRouter) and [`createHashRouter`](https://reactrouter.com/api/router-components/HashRouter) -- Use `Sentry.wrapCreateMemoryRouter` for [`createMemoryRouter`](https://reactrouter.com/api/router-components/MemoryRouter) +- Use `Sentry.wrapCreateBrowserRouter` for [`createBrowserRouter`](https://api.reactrouter.com/v8/functions/react-router.BrowserRouter.html) and [`createHashRouter`](https://api.reactrouter.com/v8/functions/react-router.HashRouter.html) +- Use `Sentry.wrapCreateMemoryRouter` for [`createMemoryRouter`](https://api.reactrouter.com/v8/functions/react-router.MemoryRouter.html) ```javascript {2-8, 15-21, 26-34} import React from "react"; diff --git a/docs/platforms/javascript/guides/remix/index.mdx b/docs/platforms/javascript/guides/remix/index.mdx index a0208a450ad51..faa270ff38644 100644 --- a/docs/platforms/javascript/guides/remix/index.mdx +++ b/docs/platforms/javascript/guides/remix/index.mdx @@ -140,8 +140,8 @@ Now's a good time to customize your setup and look into more advanced topics. Ou -- If you encountered issues with our installation wizard, try setting up Sentry manually -- Find various topics in Troubleshooting +- If you encountered issues with our installation wizard, try setting up Sentry manually +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/remix/manual-setup.mdx b/docs/platforms/javascript/guides/remix/manual-setup.mdx index d602cb7a3b845..3d89354c85365 100644 --- a/docs/platforms/javascript/guides/remix/manual-setup.mdx +++ b/docs/platforms/javascript/guides/remix/manual-setup.mdx @@ -6,7 +6,7 @@ description: "Learn how to manually set up Sentry in your Remix app and capture For the fastest setup, we recommend using the [wizard - installer](/platforms/javascript/guides/remix). + installer](/platforms/javascript/guides/remix/). configure source maps upload for your production builds. +To enable readable stack traces, configure source maps upload for your production builds. -After you've completed this setup, the SDK will automatically capture unhandled errors and promise rejections, and monitor performance. You can also [manually capture errors](/platforms/javascript/guides/remix/usage). +After you've completed this setup, the SDK will automatically capture unhandled errors and promise rejections, and monitor performance. You can also [manually capture errors](/platforms/javascript/guides/remix/usage/). ## Verify diff --git a/docs/platforms/javascript/guides/solid/features/index.mdx b/docs/platforms/javascript/guides/solid/features/index.mdx index 7f045ba78cf83..1270625e167f9 100644 --- a/docs/platforms/javascript/guides/solid/features/index.mdx +++ b/docs/platforms/javascript/guides/solid/features/index.mdx @@ -8,7 +8,7 @@ description: "Learn how Sentry's Solid SDK exposes features for first class inte This SDK is currently in **beta**. Beta features are still in progress and may have bugs. Please reach out on [GitHub](https://github.com/getsentry/sentry-javascript/issues/new/choose) if you have any feedback or concerns. This SDK is for [Solid](https://www.solidjs.com/), for [SolidStart](https://start.solidjs.com/) see our - [SolidStart SDK](/platforms/javascript/guides/solidstart). + [SolidStart SDK](/platforms/javascript/guides/solidstart/). diff --git a/docs/platforms/javascript/guides/solid/index.mdx b/docs/platforms/javascript/guides/solid/index.mdx index e2b442ec98605..21029eb1c46fd 100644 --- a/docs/platforms/javascript/guides/solid/index.mdx +++ b/docs/platforms/javascript/guides/solid/index.mdx @@ -9,7 +9,7 @@ categories: -This SDK guide is specifically for Solid. For instrumenting your SolidStart app, see our [SolidStart guide](/platforms/javascript/guides/solidstart). +This SDK guide is specifically for Solid. For instrumenting your SolidStart app, see our [SolidStart guide](/platforms/javascript/guides/solidstart/). @@ -263,12 +263,12 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Make use of Solid-specific features -- Learn how to manually capture errors +- Continue to customize your configuration +- Make use of Solid-specific features +- Learn how to manually capture errors -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/solidstart/index.mdx b/docs/platforms/javascript/guides/solidstart/index.mdx index 2bf0bda7cd27e..d89926bc44f95 100644 --- a/docs/platforms/javascript/guides/solidstart/index.mdx +++ b/docs/platforms/javascript/guides/solidstart/index.mdx @@ -15,7 +15,7 @@ This SDK is currently in **beta**. Beta features are still in progress and may h This SDK guide is specifically for SolidStart. For instrumenting your Solid - app, see our [Solid SDK](/platforms/javascript/guides/solid). + app, see our [Solid SDK](/platforms/javascript/guides/solid/). @@ -307,7 +307,7 @@ Run your build command to generate the `instrument.server.mjs` file before runni -If you're not able to use the `--import` flag, check the alternative installation methods. +If you're not able to use the `--import` flag, check the alternative installation methods. diff --git a/docs/platforms/javascript/guides/solidstart/install/cli-import.mdx b/docs/platforms/javascript/guides/solidstart/install/cli-import.mdx index ea23fddb76902..3ffb8b31a5154 100644 --- a/docs/platforms/javascript/guides/solidstart/install/cli-import.mdx +++ b/docs/platforms/javascript/guides/solidstart/install/cli-import.mdx @@ -18,7 +18,7 @@ This will register Sentry's [loader hook](https://nodejs.org/api/module.html#cus - At this time, it isn't possible to properly configure `--import` in **Vercel**. If any of those points apply to you, you cannot use the `--import` flag to initialize Sentry on the server-side. -Check out the guide for using limited server tracing instead. +Check out the guide for using limited server tracing instead. ## Initializing Sentry with `--import` diff --git a/docs/platforms/javascript/guides/solidstart/install/dynamic-import.mdx b/docs/platforms/javascript/guides/solidstart/install/dynamic-import.mdx index a4bd655734da4..09b90bb0abb76 100644 --- a/docs/platforms/javascript/guides/solidstart/install/dynamic-import.mdx +++ b/docs/platforms/javascript/guides/solidstart/install/dynamic-import.mdx @@ -9,7 +9,7 @@ description: "Learn about how the SolidStart SDK leverages dynamic input() in th This setting is experimental as it is not guaranteed to work with every setup and the underlying functionality could change. - We recommend reading the guide for installing the SDK with the CLI flag `--import` or limited server tracing + We recommend reading the guide for installing the SDK with the CLI flag `--import` or limited server tracing The `import()` expression, or dynamic import, enables flexible, conditional module loading in ESM. @@ -24,7 +24,7 @@ This early initialization of Sentry is required to correctly set up the SDK's in Depending on your setup and which version of Vinxi is used (and respectively Nitro, as this runs under the hood), the server-side is sometimes not correctly initialized. The build output **must not** include a regular `import` of the Nitro runtime (e.g. `import './chunks/nitro/nitro.mjs'`). -You can also check out the guide for installing the SDK with the CLI flag `--import` or limited-server-tracing. +You can also check out the guide for installing the SDK with the CLI flag `--import` or limited-server-tracing. ## Initializing Sentry with Dynamic `import()` diff --git a/docs/platforms/javascript/guides/solidstart/install/limited-server-tracing.mdx b/docs/platforms/javascript/guides/solidstart/install/limited-server-tracing.mdx index 8e21b35392ade..6a46d0550750d 100644 --- a/docs/platforms/javascript/guides/solidstart/install/limited-server-tracing.mdx +++ b/docs/platforms/javascript/guides/solidstart/install/limited-server-tracing.mdx @@ -7,7 +7,7 @@ description: "Learn how to set up the SolidStart SDK with limited server tracing ## Understanding Limited Server Tracing Sentry needs to be initialized before the rest of the application runs. -If the default way of adding an `--import` CLI flag doesn't work for you, +If the default way of adding an `--import` CLI flag doesn't work for you, enable the SDK to add a top-level `import`. The automatically added top-level `import` will then import the Sentry server-side config at the top of the SolidStart server entry file. diff --git a/docs/platforms/javascript/guides/svelte/index.mdx b/docs/platforms/javascript/guides/svelte/index.mdx index cee4ca62579bb..bc5fe62f09f64 100644 --- a/docs/platforms/javascript/guides/svelte/index.mdx +++ b/docs/platforms/javascript/guides/svelte/index.mdx @@ -321,13 +321,13 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Make use of Svelte-specific features -- Learn how to manually capture errors +- Continue to customize your configuration +- Make use of Svelte-specific features +- Learn how to manually capture errors -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/sveltekit/index.mdx b/docs/platforms/javascript/guides/sveltekit/index.mdx index b73b4c33291bd..33e96ee4992c0 100644 --- a/docs/platforms/javascript/guides/sveltekit/index.mdx +++ b/docs/platforms/javascript/guides/sveltekit/index.mdx @@ -65,9 +65,9 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/sveltekit/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/sveltekit/configuration/) -- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis#load-function-instrumentation) SvelteKit-specific features +- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis/#load-function-instrumentation) SvelteKit-specific features - Learn more about [deploying SvelteKit apps to Cloudflare Pages](/platforms/javascript/guides/cloudflare/frameworks/sveltekit/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts diff --git a/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx b/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx index fa58ed4f67ef5..4094ccfeea6dd 100644 --- a/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx +++ b/docs/platforms/javascript/guides/sveltekit/manual-setup__v10.7.0.mdx @@ -6,7 +6,7 @@ description: "Learn how to manually set up Sentry in your SvelteKit app and capt For the fastest setup, we recommend using the [wizard - installer](/platforms/javascript/guides/sveltekit). + installer](/platforms/javascript/guides/sveltekit/). ## Prerequisites @@ -336,7 +336,7 @@ Our next recommended steps for you are: - Learn how to [manually capture errors](/platforms/javascript/guides/sveltekit/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/sveltekit/configuration/) -- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis#load-function-instrumentation) SvelteKit-specific features +- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis/#load-function-instrumentation) SvelteKit-specific features - Learn more about [deploying SvelteKit apps to Cloudflare Pages](/platforms/javascript/guides/cloudflare/frameworks/sveltekit/) - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts diff --git a/docs/platforms/javascript/guides/tanstackstart-react/manual-setup/index.mdx b/docs/platforms/javascript/guides/tanstackstart-react/manual-setup/index.mdx index 31c148f92bcef..e847a83581ab0 100644 --- a/docs/platforms/javascript/guides/tanstackstart-react/manual-setup/index.mdx +++ b/docs/platforms/javascript/guides/tanstackstart-react/manual-setup/index.mdx @@ -20,7 +20,7 @@ Please reach out on [GitHub](https://github.com/getsentry/sentry-javascript/issu This guide walks you through setting up Sentry in a [TanStack Start (React)](https://tanstack.com/start/latest/docs/framework/react/overview) app. -For [TanStack Router (React)](https://tanstack.com/router/latest/docs/framework/react/overview), see our [React TanStack Router guide](/platforms/javascript/guides/react/features/tanstack-router). +For [TanStack Router (React)](https://tanstack.com/router/latest/docs/framework/react/overview), see our [React TanStack Router guide](/platforms/javascript/guides/react/features/tanstack-router/). @@ -721,7 +721,7 @@ Our next recommended steps for you are: -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/vue/index.mdx b/docs/platforms/javascript/guides/vue/index.mdx index 566dd5548faf0..ee85f954b33c2 100644 --- a/docs/platforms/javascript/guides/vue/index.mdx +++ b/docs/platforms/javascript/guides/vue/index.mdx @@ -376,13 +376,13 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your backend using one of our [SDKs](/) -- Continue to customize your configuration -- Make use of Vue-specific features -- Learn how to manually capture errors +- Continue to customize your configuration +- Make use of Vue-specific features +- Learn how to manually capture errors -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/javascript/guides/wasm/index.mdx b/docs/platforms/javascript/guides/wasm/index.mdx index 243892df555c0..bdeef93d2a089 100644 --- a/docs/platforms/javascript/guides/wasm/index.mdx +++ b/docs/platforms/javascript/guides/wasm/index.mdx @@ -285,12 +285,12 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Instrument your frontend and backend using our [SDKs](/) -- Continue to [customize your configuration](/platforms/javascript/guides/wasm/configuration) -- Learn how to [manually capture errors](/platforms/javascript/guides/wasm/usage) +- Continue to [customize your configuration](/platforms/javascript/guides/wasm/configuration/) +- Learn how to [manually capture errors](/platforms/javascript/guides/wasm/usage/) -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/docs/platforms/kotlin/guides/compose-multiplatform/index.mdx b/docs/platforms/kotlin/guides/compose-multiplatform/index.mdx index df4fb6c489658..3ff6727b31b2c 100644 --- a/docs/platforms/kotlin/guides/compose-multiplatform/index.mdx +++ b/docs/platforms/kotlin/guides/compose-multiplatform/index.mdx @@ -54,7 +54,7 @@ For Android applications, you need to manually upload ProGuard mapping files usi ### iOS -For iOS applications, follow the [Uploading Debug Symbols guide](/platforms/apple/guides/ios/dsym) to set up debug symbols upload. +For iOS applications, follow the [Uploading Debug Symbols guide](/platforms/apple/guides/ios/dsym/) to set up debug symbols upload. ## Next Steps diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/debug-symbols/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/debug-symbols/index.mdx index 8ded4768391b3..1a287caaea1d4 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/debug-symbols/index.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/debug-symbols/index.mdx @@ -10,13 +10,13 @@ The symbolication process unscrambles the stack traces to reveal the function, f ## Apple -For Apple applications please follow the iOS documentation on [Uploading Debug Symbols](/platforms/apple/guides/ios/dsym) to set up debug symbols upload. +For Apple applications please follow the iOS documentation on [Uploading Debug Symbols](/platforms/apple/guides/ios/dsym/) to set up debug symbols upload. ## Android ### Gradle -To upload ProGuard mapping files or Native debug symbols via Gradle you need to install the [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle) in your `androidApp` module: +To upload ProGuard mapping files or Native debug symbols via Gradle you need to install the [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/) in your `androidApp` module: ```kotlin {filename:androidApp/build.gradle.kts} plugins { diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx index f69dbf545023c..d42f4ce34cad0 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/breadcrumbs/index.mdx @@ -5,7 +5,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx index ef8be403c37e4..ad881d2b0fa92 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/enriching-events/viewhierarchy/index.mdx @@ -21,7 +21,7 @@ View hierarchy debugging is an opt-in feature. You can enable it as shown below: ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx index 251c20e532a75..2ad89fcef9e8b 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/features/index.mdx @@ -8,9 +8,9 @@ sidebar_section: features Sentry's Kotlin Multiplatform SDK enables automatic reporting of errors and exceptions. Because the SDK provides a unified API for all supported platforms directly leveraging the native SDKs for each platform, it also supports the same features as the native SDKs. Click on a link below to see relevant features for your platform: -- [Apple features](/platforms/apple/features) -- [Android features](/platforms/android/features) -- [Java features](/platforms/java) +- [Apple features](/platforms/apple/features/) +- [Android features](/platforms/android/features/) +- [Java features](/platforms/java/) Some functionality may not be available in the shared Kotlin Multiplatform layer yet. You may have to use the native SDKs directly, or write your own platform-specific code. diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx index 3ad27af0e2f89..d3c86ca6e55e7 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/index.mdx @@ -42,7 +42,7 @@ To view and resolve the recorded error, log into [sentry.io](https://sentry.io) ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn more about Sentry's Kotlin Multiplatform SDK features -- Learn about different ways to initialize the SDK -- See configuration options for the Kotlin Multiplatform Gradle Plugin -- Add readable stack traces to your errors +- Learn more about Sentry's Kotlin Multiplatform SDK features +- Learn about different ways to initialize the SDK +- See configuration options for the Kotlin Multiplatform Gradle Plugin +- Add readable stack traces to your errors diff --git a/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx b/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx index 7b727a900dc26..84c90a9268e82 100644 --- a/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx +++ b/docs/platforms/kotlin/guides/kotlin-multiplatform/troubleshooting.mdx @@ -11,7 +11,7 @@ If you need additional help, [ask on GitHub](https://github.com/getsentry/sentry ## "Missing API declaration" after App Store review -Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't meet the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest) guide. +Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't meet the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest/) guide. ## Tests Not Working diff --git a/docs/platforms/kotlin/index.mdx b/docs/platforms/kotlin/index.mdx index f4362da74e7e6..1ea365c3775f0 100644 --- a/docs/platforms/kotlin/index.mdx +++ b/docs/platforms/kotlin/index.mdx @@ -11,12 +11,12 @@ keywords: - kotlin --- -Sentry supports JVM related use of Kotlin with the [Java](/platforms/java) SDK. For native Android applications, use the [Android](/platforms/android) SDK. If you use KMP, the [Kotlin Multiplatform](/platforms/kotlin/guides/kotlin-multiplatform/) SDK provides the best integration. +Sentry supports JVM related use of Kotlin with the [Java](/platforms/java/) SDK. For native Android applications, use the [Android](/platforms/android/) SDK. If you use KMP, the [Kotlin Multiplatform](/platforms/kotlin/guides/kotlin-multiplatform/) SDK provides the best integration. Select your platform to get started: -- [Java](/platforms/java) -- [Android](/platforms/android) +- [Java](/platforms/java/) +- [Android](/platforms/android/) - [Kotlin Multiplatform](/platforms/kotlin/guides/kotlin-multiplatform/) - [Compose Multiplatform](/platforms/kotlin/guides/compose-multiplatform/) diff --git a/docs/platforms/native/common/configuration/options.mdx b/docs/platforms/native/common/configuration/options.mdx index 0a34800c5ced5..7b081802e7dcc 100644 --- a/docs/platforms/native/common/configuration/options.mdx +++ b/docs/platforms/native/common/configuration/options.mdx @@ -142,7 +142,7 @@ A function responsible for determining the percentage chance a given transaction -This option enables the [logging integration](/platforms/native/logs), which allows the SDK to capture logs and send them to Sentry. +This option enables the [logging integration](/platforms/native/logs/), which allows the SDK to capture logs and send them to Sentry. @@ -162,7 +162,7 @@ Whether calls to `sentry_log_X()` expect an attributes object as the second argu -This option enables [Application Metrics](/platforms/native/metrics). When disabled, all calls to `sentry_metrics_*()` are no-ops. +This option enables [Application Metrics](/platforms/native/metrics/). When disabled, all calls to `sentry_metrics_*()` are no-ops. Metrics have been enabled by default since `0.13.5`. In earlier versions they were experimental and had to be turned on explicitly. diff --git a/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx index da397b7724b73..961dc2675331d 100644 --- a/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/native/common/enriching-events/breadcrumbs/index.mdx @@ -12,7 +12,7 @@ notSupported: Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/native/configuration/backends/index.mdx b/docs/platforms/native/configuration/backends/index.mdx index 79fd3f57591f4..ccb30c6dcc6ab 100644 --- a/docs/platforms/native/configuration/backends/index.mdx +++ b/docs/platforms/native/configuration/backends/index.mdx @@ -41,5 +41,5 @@ The following table summarizes backend support for each target OS: 1 Builds and should work, but is untested. -The [Advanced Usage](/platforms/native/advanced-usage/backend-tradeoffs) section +The [Advanced Usage](/platforms/native/advanced-usage/backend-tradeoffs/) section explains the trade-offs in choosing the correct backend for your use case. diff --git a/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx index 69da2edef5205..7f0a4948b5972 100644 --- a/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/php/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/php/common/integrations/otlp/index.mdx b/docs/platforms/php/common/integrations/otlp/index.mdx index f003eab6e95ee..d45899cc3e10a 100644 --- a/docs/platforms/php/common/integrations/otlp/index.mdx +++ b/docs/platforms/php/common/integrations/otlp/index.mdx @@ -4,7 +4,7 @@ description: "Learn about using OTLP to automatically send OpenTelemetry Traces keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). diff --git a/docs/platforms/php/common/troubleshooting/index.mdx b/docs/platforms/php/common/troubleshooting/index.mdx index 5d8a00c41b25f..0782a7954ff7b 100644 --- a/docs/platforms/php/common/troubleshooting/index.mdx +++ b/docs/platforms/php/common/troubleshooting/index.mdx @@ -67,7 +67,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). - - Ensure that the custom instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). + - Ensure that the custom instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). - Ensure the `Sentry\Integration\EnvironmentIntegration` is enabled. - Enable the logger to see what the SDK is doing under the hood. diff --git a/docs/platforms/php/guides/laravel/integrations/otlp.mdx b/docs/platforms/php/guides/laravel/integrations/otlp.mdx index 7a621ea907040..3eaba3fc79b0d 100644 --- a/docs/platforms/php/guides/laravel/integrations/otlp.mdx +++ b/docs/platforms/php/guides/laravel/integrations/otlp.mdx @@ -4,7 +4,7 @@ description: "Learn about using OTLP to automatically send OpenTelemetry Traces keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). diff --git a/docs/platforms/php/guides/symfony/integrations/otlp.mdx b/docs/platforms/php/guides/symfony/integrations/otlp.mdx index 413ba3de7141b..5e46c079db2ee 100644 --- a/docs/platforms/php/guides/symfony/integrations/otlp.mdx +++ b/docs/platforms/php/guides/symfony/integrations/otlp.mdx @@ -4,7 +4,7 @@ description: "Learn about using OTLP to automatically send OpenTelemetry Traces keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). diff --git a/docs/platforms/php/index.mdx b/docs/platforms/php/index.mdx index 282e37b8841f4..a946f8d7961e3 100644 --- a/docs/platforms/php/index.mdx +++ b/docs/platforms/php/index.mdx @@ -16,7 +16,7 @@ og_image: /og-images/platforms-php.png - You need a [Sentry account](https://sentry.io/signup/) and project - Your application needs to run on PHP 7.2 or later - You need to be using Composer -- Read one of these other guides if you use Laravel or Symfony +- Read one of these other guides if you use Laravel or Symfony ## Features diff --git a/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx b/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx index aa9fe4e4f88bb..f1e125c11f0bd 100644 --- a/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/powershell/enriching-events/breadcrumbs/index.mdx @@ -5,7 +5,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/powershell/index.mdx b/docs/platforms/powershell/index.mdx index 146c61e5fffeb..048ce7d277bc1 100644 --- a/docs/platforms/powershell/index.mdx +++ b/docs/platforms/powershell/index.mdx @@ -17,7 +17,7 @@ On this page, we get you up and running with Sentry's PowerShell SDK. The PowerS - PowerShell 7.4+ on Windows, macOS, and Linux - Windows PowerShell 5.1 -The PowerShell SDK is based on the Sentry .NET SDK. You can refer to the [.NET SDK docs](/platforms/dotnet/configuration) for the documentation of advanced features you don't find here. +The PowerShell SDK is based on the Sentry .NET SDK. You can refer to the [.NET SDK docs](/platforms/dotnet/configuration/) for the documentation of advanced features you don't find here. ## Install diff --git a/docs/platforms/python/configuration/filtering/index.mdx b/docs/platforms/python/configuration/filtering/index.mdx index ca3bbd1eb513d..98dbd2e7f91ba 100644 --- a/docs/platforms/python/configuration/filtering/index.mdx +++ b/docs/platforms/python/configuration/filtering/index.mdx @@ -104,7 +104,7 @@ When a string or a non-error object is raised, Sentry creates a synthetic except ## Filtering Transactions and Spans -To prevent certain transactions (or spans in stream mode) from being reported to Sentry, use the , (for transaction mode), or (for stream mode) configuration options. These allow you to provide a function to evaluate the current transaction or span and drop it if it's not one you want. +To prevent certain transactions (or spans in stream mode) from being reported to Sentry, use the , (for transaction mode), or (for stream mode) configuration options. These allow you to provide a function to evaluate the current transaction or span and drop it if it's not one you want. You can also use (for transaction mode) or (for stream mode) to modify transaction/span data. diff --git a/docs/platforms/python/configuration/options.mdx b/docs/platforms/python/configuration/options.mdx index bdb6a4bd34528..edc23dc582dc9 100644 --- a/docs/platforms/python/configuration/options.mdx +++ b/docs/platforms/python/configuration/options.mdx @@ -208,7 +208,7 @@ Whether sessions should be automatically recorded and sent to Sentry. -List of integrations to enable in addition to [auto-enabling integrations](/platforms/python/integrations). This setting can be used to override the default config options for a specific auto-enabling integration or to add an integration that is not auto-enabled. +List of integrations to enable in addition to [auto-enabling integrations](/platforms/python/integrations/). This setting can be used to override the default config options for a specific auto-enabling integration or to add an integration that is not auto-enabled. @@ -256,7 +256,7 @@ This function is called with a transaction event object, and can return a modifi -Only available in stream mode. +Only available in stream mode. @@ -416,7 +416,7 @@ Controls how spans are sent to Sentry: -Only available in stream mode. +Only available in stream mode. @@ -497,7 +497,7 @@ An optional organization ID for your Sentry project. The SDK will try to extract the organization ID from the DSN. If it cannot be found, or if you need to override it (if you use Relay or self-hosted), you can provide the ID with this option. -The organization ID is used for features like strict trace continuation. +The organization ID is used for features like strict trace continuation. diff --git a/docs/platforms/python/enriching-events/attributes/index.mdx b/docs/platforms/python/enriching-events/attributes/index.mdx index 56fa6281ed3e1..3c31f4410cffc 100644 --- a/docs/platforms/python/enriching-events/attributes/index.mdx +++ b/docs/platforms/python/enriching-events/attributes/index.mdx @@ -5,7 +5,7 @@ description: "Attributes automatically enrich your telemetry with typed key-valu -**Attributes** are key-value pairs you can attach to your telemetry (like spans, logs, and metrics). +**Attributes** are key-value pairs you can attach to your telemetry (like spans, logs, and metrics). Common uses include subscription tier, feature flags, or any business context that helps you filter and query your telemetry. @@ -13,7 +13,7 @@ Attribute values can be `str`, `int`, `float`, or `bool`, as well as arrays of t -Attributes on spans require stream mode (SDK version `2.62.0`+). In stream mode, spans have no contexts, data, or tags — everything is an attribute, so `set_data()`, `set_tag()`, and `set_context()` are replaced by `set_attribute()` and `set_attributes()`. +Attributes on spans require stream mode (SDK version `2.62.0`+). In stream mode, spans have no contexts, data, or tags — everything is an attribute, so `set_data()`, `set_tag()`, and `set_context()` are replaced by `set_attribute()` and `set_attributes()`. Attributes on logs and metrics don't require stream mode — they work regardless of your `trace_lifecycle` setting. @@ -45,7 +45,7 @@ with sentry_sdk.new_scope() as scope: sentry_sdk.logger.info("Processing payment") ``` -See Scopes for more on the global, isolation, and current scopes. +See Scopes for more on the global, isolation, and current scopes. ## Setting Attributes on Individual Telemetry @@ -100,7 +100,7 @@ sentry_sdk.logger.error( ) ``` -See Logs for more. +See Logs for more. ### Metrics @@ -119,4 +119,4 @@ sentry_sdk.metrics.count( ) ``` -See Application Metrics for more. +See Application Metrics for more. diff --git a/docs/platforms/python/enriching-events/breadcrumbs/index.mdx b/docs/platforms/python/enriching-events/breadcrumbs/index.mdx index 1e142ed6892b5..170ecbfdf6d19 100644 --- a/docs/platforms/python/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/python/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/python/integrations/anthropic/index.mdx b/docs/platforms/python/integrations/anthropic/index.mdx index 67d01fe5599cb..189f41d91b2fe 100644 --- a/docs/platforms/python/integrations/anthropic/index.mdx +++ b/docs/platforms/python/integrations/anthropic/index.mdx @@ -7,7 +7,7 @@ This integration connects Sentry with the [Anthropic Python SDK](https://github. Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -57,7 +57,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `AI Spans` tab on the `Explore > Traces > Trace` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/gcp-functions/index.mdx b/docs/platforms/python/integrations/gcp-functions/index.mdx index ef38710686202..9b35ef21b0ec1 100644 --- a/docs/platforms/python/integrations/gcp-functions/index.mdx +++ b/docs/platforms/python/integrations/gcp-functions/index.mdx @@ -17,7 +17,7 @@ Add the Sentry SDK to your `requirements.txt`: The GCP integration currently supports only the Python `3.7` runtime environment. If you try to run it with a newer version (such as `3.9`), an error message will be displayed (with debug mode on). -Limited Sentry support is available on newer Python runtimes by directly enabling [integrations for supported frameworks](/platforms/python/integrations) and/or using the generic [serverless integration](/platforms/python/integrations/serverless/). +Limited Sentry support is available on newer Python runtimes by directly enabling [integrations for supported frameworks](/platforms/python/integrations/) and/or using the generic [serverless integration](/platforms/python/integrations/serverless/). diff --git a/docs/platforms/python/integrations/google-genai/index.mdx b/docs/platforms/python/integrations/google-genai/index.mdx index 931cf06522af4..21ff92bf7dbeb 100644 --- a/docs/platforms/python/integrations/google-genai/index.mdx +++ b/docs/platforms/python/integrations/google-genai/index.mdx @@ -7,7 +7,7 @@ This integration connects Sentry with the [Google Gen AI Python SDK](https://git Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -70,7 +70,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/graphene/index.mdx b/docs/platforms/python/integrations/graphene/index.mdx index b85094643f488..31a27b69e7acd 100644 --- a/docs/platforms/python/integrations/graphene/index.mdx +++ b/docs/platforms/python/integrations/graphene/index.mdx @@ -54,8 +54,8 @@ code snippet is run, a new error event should appear in the Issues section of ## Options When used together with one of our web framework integrations like -[FastAPI](/platforms/python/integrations/fastapi) or -[Flask](/platforms/python/integrations/flask), the Graphene +[FastAPI](/platforms/python/integrations/fastapi/) or +[Flask](/platforms/python/integrations/flask/), the Graphene integration can capture the request body for each GraphQL error that happens. Since the requests may contain sensitive data, no request bodies will be attached by default. diff --git a/docs/platforms/python/integrations/huggingface_hub/index.mdx b/docs/platforms/python/integrations/huggingface_hub/index.mdx index d6b0f07f06f1d..7a9f7d19effd4 100644 --- a/docs/platforms/python/integrations/huggingface_hub/index.mdx +++ b/docs/platforms/python/integrations/huggingface_hub/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for Hugging Face Hub." This integration connects Sentry with [Hugging Face Hub](https://github.com/huggingface/huggingface_hub) in Python. -Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -89,7 +89,7 @@ if __name__ == "__main__": main() ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/langchain/index.mdx b/docs/platforms/python/integrations/langchain/index.mdx index 5464c52297e04..39e8a21ae21fa 100644 --- a/docs/platforms/python/integrations/langchain/index.mdx +++ b/docs/platforms/python/integrations/langchain/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for LangChain." This integration connects Sentry with [LangChain](https://github.com/langchain-ai/langchain) in Python. -Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -151,7 +151,7 @@ with sentry_sdk.start_transaction(name="langchain-anthropic"): print(result) ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/langgraph/index.mdx b/docs/platforms/python/integrations/langgraph/index.mdx index 8bbffb4c4cbd2..2724656028eea 100644 --- a/docs/platforms/python/integrations/langgraph/index.mdx +++ b/docs/platforms/python/integrations/langgraph/index.mdx @@ -5,7 +5,7 @@ description: "Learn about using Sentry for LangGraph." This integration connects Sentry with [LangGraph](https://github.com/langchain-ai/langgraph) in Python. -Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -86,7 +86,7 @@ with sentry_sdk.start_transaction(name="langgraph-openai"): print(result) ``` -After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents). +After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io, and in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/litellm/index.mdx b/docs/platforms/python/integrations/litellm/index.mdx index 9d010faa806f0..34385d0f0671f 100644 --- a/docs/platforms/python/integrations/litellm/index.mdx +++ b/docs/platforms/python/integrations/litellm/index.mdx @@ -7,7 +7,7 @@ This integration connects Sentry with the [LiteLLM Python SDK](https://github.co Once you've installed this SDK, you can use the Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). ## Install @@ -71,7 +71,7 @@ print(response.choices[0].message.content) After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/litestar/index.mdx b/docs/platforms/python/integrations/litestar/index.mdx index da211b7f56ae3..f82832d2be64a 100644 --- a/docs/platforms/python/integrations/litestar/index.mdx +++ b/docs/platforms/python/integrations/litestar/index.mdx @@ -120,7 +120,7 @@ Regardless of how `failed_request_status_codes` is set, any exceptions raised by Litestar was renamed from Starlite with the release of version 2.0. We support different integrations for each one. This guide applies to Litestar. -See [Starlite integration](/platforms/python/integrations/starlite) for the guide that applies to Starlite. +See [Starlite integration](/platforms/python/integrations/starlite/) for the guide that applies to Starlite. diff --git a/docs/platforms/python/integrations/loguru/index.mdx b/docs/platforms/python/integrations/loguru/index.mdx index 7536c47f4edcb..8703f02085454 100644 --- a/docs/platforms/python/integrations/loguru/index.mdx +++ b/docs/platforms/python/integrations/loguru/index.mdx @@ -5,7 +5,7 @@ description: Learn about using Sentry with Loguru. The [Loguru](https://github.com/Delgan/loguru#readme) integration lets you capture log messages and send them to Sentry. -The [`logging`](/platforms/python/integrations/logging) integration provides most of the Loguru functionality and most examples on that page work with Loguru. +The [`logging`](/platforms/python/integrations/logging/) integration provides most of the Loguru functionality and most examples on that page work with Loguru. diff --git a/docs/platforms/python/integrations/openai/index.mdx b/docs/platforms/python/integrations/openai/index.mdx index 555c5ce3c7a2d..68dbdce34966a 100644 --- a/docs/platforms/python/integrations/openai/index.mdx +++ b/docs/platforms/python/integrations/openai/index.mdx @@ -7,7 +7,7 @@ This integration connects Sentry with the [OpenAI Python SDK](https://github.com Once you've installed this SDK, you can use Sentry Agents Tracing, a Sentry dashboard that helps you understand what's going on with your AI requests. -Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents). +Sentry AI Observability will automatically collect information about prompts, tools, tokens, and models. Learn more about the [AI Agents Dashboard](/product/agents/). @@ -66,7 +66,7 @@ def my_llm_stuff(): After running this script, the resulting data should show up in the `"AI Spans"` tab on the `"Explore" > "Traces"` page on Sentry.io. -If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents). +If you manually created an Invoke Agent Span (not done in the example above) the data will also show up in the [AI Agents Dashboard](/product/agents/). It may take a couple of moments for the data to appear in [sentry.io](https://sentry.io). diff --git a/docs/platforms/python/integrations/otlp/index.mdx b/docs/platforms/python/integrations/otlp/index.mdx index 5f903cb9e9469..9e5b6eeec946d 100644 --- a/docs/platforms/python/integrations/otlp/index.mdx +++ b/docs/platforms/python/integrations/otlp/index.mdx @@ -4,7 +4,7 @@ description: "Learn about using OTLP to automatically send OpenTelemetry Traces keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). ## Install @@ -93,7 +93,7 @@ You can pass the following keyword arguments to `OTLPIntegration()`: Set to `True` to intercept and capture exceptions on the OpenTelemetry Span recorded with `Span.record_exception` in Sentry as well, defaults to `False`. - Caveat: Since Sentry already captures most exceptions, duplicate exceptions might be dropped by [`DedupeIntegration`](/platforms/python/integrations/default-integrations/#deduplication) but that should not affect your overall product experience on the [Issues](/product/issues) page. + Caveat: Since Sentry already captures most exceptions, duplicate exceptions might be dropped by [`DedupeIntegration`](/platforms/python/integrations/default-integrations/#deduplication) but that should not affect your overall product experience on the [Issues](/product/issues/) page. ## Supported Versions diff --git a/docs/platforms/python/integrations/starlite/index.mdx b/docs/platforms/python/integrations/starlite/index.mdx index c761a65b017d8..56bd41fb14a6a 100644 --- a/docs/platforms/python/integrations/starlite/index.mdx +++ b/docs/platforms/python/integrations/starlite/index.mdx @@ -56,7 +56,7 @@ It takes a couple of moments for the data to appear in [sentry.io](https://sentr Starlite was renamed to Litestar with the release of version 2.0. We support different integrations for each one. This guide applies to Starlite. -See [Litestar integration](/platforms/python/integrations/litestar) for the guide that applies to Litestar. +See [Litestar integration](/platforms/python/integrations/litestar/) for the guide that applies to Litestar. diff --git a/docs/platforms/python/profiling/index.mdx b/docs/platforms/python/profiling/index.mdx index 9b210b4b0e244..cb9c53cf108c1 100644 --- a/docs/platforms/python/profiling/index.mdx +++ b/docs/platforms/python/profiling/index.mdx @@ -95,7 +95,7 @@ Continuous profiling was experimental in SDK versions prior to `2.24.1` and will Transaction-based profiling is available starting in SDK version `1.18.0`. -It's not available in stream mode. Use continuous profiling instead. +It's not available in stream mode. Use continuous profiling instead. diff --git a/docs/platforms/python/sampling.mdx b/docs/platforms/python/sampling.mdx index 3e8a5df7683ff..7a7e4b15ff617 100644 --- a/docs/platforms/python/sampling.mdx +++ b/docs/platforms/python/sampling.mdx @@ -44,7 +44,7 @@ You can define at most one of the an -If you're using stream mode, refer to our Configure Sampling guide for setup instructions. +If you're using stream mode, refer to our Configure Sampling guide for setup instructions. diff --git a/docs/platforms/python/tracing/configure-sampling/index.mdx b/docs/platforms/python/tracing/configure-sampling/index.mdx index 329b915f33b4f..3ad84f4090d0d 100644 --- a/docs/platforms/python/tracing/configure-sampling/index.mdx +++ b/docs/platforms/python/tracing/configure-sampling/index.mdx @@ -18,7 +18,7 @@ This page covers both transaction mode (default) and stream mode. See stream mode) will be sampled. This works the same way in both transaction mode and stream mode: +`traces_sample_rate` is a floating-point value between `0.0` and `1.0`, inclusive, which controls the probability with which each transaction (or service spans in stream mode) will be sampled. This works the same way in both transaction mode and stream mode: diff --git a/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx index 87aa8c71e319a..e43a74515a17a 100644 --- a/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/python/tracing/instrumentation/automatic-instrumentation.mdx @@ -17,7 +17,7 @@ supported: description: "Learn what instrumentation automatically captures transactions." --- -Many integrations for popular frameworks automatically capture transactions (or service spans in stream mode). If you already have any of the following frameworks set up for Sentry error reporting, you will start to see traces immediately: +Many integrations for popular frameworks automatically capture transactions (or service spans in stream mode). If you already have any of the following frameworks set up for Sentry error reporting, you will start to see traces immediately: - All WSGI-based web frameworks (Django, Flask, Pyramid, Falcon, Bottle) - Celery diff --git a/docs/platforms/python/troubleshooting.mdx b/docs/platforms/python/troubleshooting.mdx index f0ff2fb88f678..5a05ac0423b73 100644 --- a/docs/platforms/python/troubleshooting.mdx +++ b/docs/platforms/python/troubleshooting.mdx @@ -192,7 +192,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. ### Upgrading From Older SDK Versions diff --git a/docs/platforms/react-native/common/configuration/webview.mdx b/docs/platforms/react-native/common/configuration/webview.mdx index 027f1655c06dc..6dee56715513b 100644 --- a/docs/platforms/react-native/common/configuration/webview.mdx +++ b/docs/platforms/react-native/common/configuration/webview.mdx @@ -13,9 +13,9 @@ The Sentry React Native SDK doesn't interact with the mobile application's web v To monitor errors and performance in web views choose the appropriate Sentry JavaScript SDK depending on the framework used in the web project. -- [Sentry React Native SDK](/platforms/react-native) (if the web project uses React Native Web or Expo) +- [Sentry React Native SDK](/platforms/react-native/) (if the web project uses React Native Web or Expo) - [Sentry React SDK](/platforms/javascript/guides/react/) (if the web project uses React) -- [Other Sentry JavaScript SDKs](/platforms/javascript) +- [Other Sentry JavaScript SDKs](/platforms/javascript/) ## Notes diff --git a/docs/platforms/react-native/common/data-management/data-collected.mdx b/docs/platforms/react-native/common/data-management/data-collected.mdx index dde3db8a76aeb..be63023ea8b1f 100644 --- a/docs/platforms/react-native/common/data-management/data-collected.mdx +++ b/docs/platforms/react-native/common/data-management/data-collected.mdx @@ -60,11 +60,11 @@ To disable sending console logs, set `console: false` in your `Sentry.breadcrumb ## Screenshots -The screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. +The screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. ## View Hierarchy -The view hierarchy feature is disabled per default, but when enabled the view hierarchy may contain PII data when using the `accessibilityIdentifier` property with personal information. +The view hierarchy feature is disabled per default, but when enabled the view hierarchy may contain PII data when using the `accessibilityIdentifier` property with personal information. ## Session Replay diff --git a/docs/platforms/react-native/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/react-native/common/enriching-events/breadcrumbs/index.mdx index cd30c7dcc5f8c..ded405b2c0c12 100644 --- a/docs/platforms/react-native/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/react-native/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/react-native/common/enriching-events/context/index.mdx b/docs/platforms/react-native/common/enriching-events/context/index.mdx index e35317ecc2a57..ac46232b9720d 100644 --- a/docs/platforms/react-native/common/enriching-events/context/index.mdx +++ b/docs/platforms/react-native/common/enriching-events/context/index.mdx @@ -27,7 +27,7 @@ Then, use and give the context a uniqu There are no restrictions on context name. In the context object, all keys are allowed except for `type`, which is used internally. -By default, Sentry SDKs normalize nested structured context data up to three levels deep. Any data beyond this depth will be trimmed and marked using its type instead. To adjust this default, use the `normalizeDepth` SDK option. +By default, Sentry SDKs normalize nested structured context data up to three levels deep. Any data beyond this depth will be trimmed and marked using its type instead. To adjust this default, use the `normalizeDepth` SDK option. Learn more about conventions for common contexts in the [contexts interface developer documentation](https://develop.sentry.dev/sdk/foundations/transport/event-payloads/contexts/). diff --git a/docs/platforms/react-native/common/enriching-events/viewhierarchy/index.mdx b/docs/platforms/react-native/common/enriching-events/viewhierarchy/index.mdx index 68dfa8645fe22..aa2f0739fd4db 100644 --- a/docs/platforms/react-native/common/enriching-events/viewhierarchy/index.mdx +++ b/docs/platforms/react-native/common/enriching-events/viewhierarchy/index.mdx @@ -21,7 +21,7 @@ View hierarchy debugging is an opt-in feature. You can enable it as shown below: ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/react-native/common/index.mdx b/docs/platforms/react-native/common/index.mdx index 415f3cd765117..2a2e265f710e3 100644 --- a/docs/platforms/react-native/common/index.mdx +++ b/docs/platforms/react-native/common/index.mdx @@ -137,12 +137,12 @@ throw new Error("My first Sentry error!"); Sentry.nativeCrash(); ``` -Alternatively, you can use the Sentry Playground to interactively test your SDK setup with multiple error scenarios. +Alternatively, you can use the Sentry Playground to interactively test your SDK setup with multiple error scenarios. ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn about the features of Sentry's React Native SDK +- Learn about the features of Sentry's React Native SDK - Add readable stack traces to errors -- Add Apple Privacy manifest +- Add Apple Privacy manifest diff --git a/docs/platforms/react-native/common/manual-setup/manual-setup.mdx b/docs/platforms/react-native/common/manual-setup/manual-setup.mdx index 1a179a28fc71b..b3ea6b06f2774 100644 --- a/docs/platforms/react-native/common/manual-setup/manual-setup.mdx +++ b/docs/platforms/react-native/common/manual-setup/manual-setup.mdx @@ -4,7 +4,7 @@ description: "Learn about manual configuration for iOS and Android." sidebar_order: 3 --- -If you can't (or prefer not to) run the [automatic setup](/platforms/react-native), use the instructions below to configure your application. +If you can't (or prefer not to) run the [automatic setup](/platforms/react-native/), use the instructions below to configure your application. ## Install SDK Package @@ -182,7 +182,7 @@ apply from: "../../node_modules/@sentry/react-native/sentry.gradle" ### Enable Sentry AGP -You can enable native symbol upload and other features by adding the [Sentry Android Gradle Plugin (AGP)](/platforms/android/configuration/gradle) dependency to `android/build.gradle`. +You can enable native symbol upload and other features by adding the [Sentry Android Gradle Plugin (AGP)](/platforms/android/configuration/gradle/) dependency to `android/build.gradle`. ```groovy {filename:android/build.gradle} buildscript { diff --git a/docs/platforms/react-native/common/manual-setup/metro.mdx b/docs/platforms/react-native/common/manual-setup/metro.mdx index 13676a8bede11..e2e9fb83966e7 100644 --- a/docs/platforms/react-native/common/manual-setup/metro.mdx +++ b/docs/platforms/react-native/common/manual-setup/metro.mdx @@ -10,7 +10,7 @@ This page will guide you through the process of setting up the Metro Plugin for ## Prerequisites - [Sign up for an account](https://sentry.io/signup/) -- [Install Sentry React Native SDK](/platforms/react-native) version 5.17.0 or newer +- [Install Sentry React Native SDK](/platforms/react-native/) version 5.17.0 or newer - Expo is supported from SDK version 5.16.0-alpha.1 ## Configuration @@ -143,6 +143,6 @@ export type Bundle = { ## Troubleshooting -- Sentry Metro Serializer can't add Debug ID to the Hermes Composed Source Maps. Please see [Manual Upload With Hermes](/platforms/react-native/sourcemaps#manual-upload-with-hermes) guide on how to add Debug ID to the Hermes Composed Source Maps. +- Sentry Metro Serializer can't add Debug ID to the Hermes Composed Source Maps. Please see [Manual Upload With Hermes](/platforms/react-native/sourcemaps/#manual-upload-with-hermes) guide on how to add Debug ID to the Hermes Composed Source Maps. - If you see `Debug ID was not found in the bundle.` error message the `sentryBundleCallback` was not called by your custom serializer. - If Metro configuration is missing in your Expo project, create it using `npx expo customize metro.config.js`. Read more about [Customizing Expo Metro Configuration](https://docs.expo.dev/guides/customizing-metro/). diff --git a/docs/platforms/react-native/common/overhead/index.mdx b/docs/platforms/react-native/common/overhead/index.mdx index 75bba9c43d4af..b1451fcb354d8 100644 --- a/docs/platforms/react-native/common/overhead/index.mdx +++ b/docs/platforms/react-native/common/overhead/index.mdx @@ -23,13 +23,13 @@ The SDK also provides methods to manually capture events: Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. +If you activate these features, the SDK will capture Screenshots and View Hierarchy of the app's UI at the time of an error or crash. This incurs a small overhead that is unnoticeable during normal operation. If your app raises many errors in a tight loop, it can become too much to process quickly enough, and UI jank can be the result, so make sure you handle such cases appropriately. ## Breadcrumbs -Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. +Breadcrumbs are collected through automated integrations or by manually adding them. To have them readily available for every event generated by the SDK, they are continuously persisted, and managed in a performant buffer. This shouldn't impact user experience. Capturing excessive numbers of breadcrumbs (for example, creating breadcrumbs for all log messages) can cause significant performance overhead. To mitigate this, review and adapt your app's usage of breadcrumbs. For example, use `breadcrumbsIntegration` options or `beforeBreadcrumb` hook to fine-tune which types of breadcrumbs are created. diff --git a/docs/platforms/react-native/common/profiling/troubleshooting/index.mdx b/docs/platforms/react-native/common/profiling/troubleshooting/index.mdx index 7359faebf0698..11b81a3612468 100644 --- a/docs/platforms/react-native/common/profiling/troubleshooting/index.mdx +++ b/docs/platforms/react-native/common/profiling/troubleshooting/index.mdx @@ -8,12 +8,12 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t - Ensure that Tracing is enabled. - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). -- If the automatic instrumentation is not sending performance data, try using custom instrumentation. +- If the automatic instrumentation is not sending performance data, try using custom instrumentation. - Enable debug mode in the SDK and check the logs. ### 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/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/platforms/react-native/common/size-analysis/index.mdx b/docs/platforms/react-native/common/size-analysis/index.mdx index 1561114933274..1ee7725e284ad 100644 --- a/docs/platforms/react-native/common/size-analysis/index.mdx +++ b/docs/platforms/react-native/common/size-analysis/index.mdx @@ -7,7 +7,7 @@ description: Upload React Native iOS and Android builds to Sentry for size analy new: true --- -[Size Analysis](/product/size-analysis) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. +[Size Analysis](/product/size-analysis/) helps monitor your mobile app's size in pre-production to prevent unexpected size increases (regressions) from reaching users. Aside from being courteous to your users, a smaller app size helps boost installation and retention rates, especially for customers with limited storage or slower connections. ## Getting Started - iOS diff --git a/docs/platforms/react-native/common/sourcemaps/index.mdx b/docs/platforms/react-native/common/sourcemaps/index.mdx index 599069831d04c..94bcf62fcd16d 100644 --- a/docs/platforms/react-native/common/sourcemaps/index.mdx +++ b/docs/platforms/react-native/common/sourcemaps/index.mdx @@ -31,7 +31,7 @@ The wizard will guide you through the following steps: - Installing the necessary Sentry packages - Configuring RN build tools to generate and upload source maps -It supports JavaScript Core (including RAM Bundle) and Hermes. If you want to configure automatic source maps upload manually, follow the steps on the [Manual Configuration](/platforms/react-native/manual-setup/manual-setup) page. +It supports JavaScript Core (including RAM Bundle) and Hermes. If you want to configure automatic source maps upload manually, follow the steps on the [Manual Configuration](/platforms/react-native/manual-setup/manual-setup/) page. ### Disable Automatic Upload diff --git a/docs/platforms/react-native/common/sourcemaps/troubleshooting/legacy-uploading-methods.mdx b/docs/platforms/react-native/common/sourcemaps/troubleshooting/legacy-uploading-methods.mdx index 3a0abf9f3e306..d0252ef77a264 100644 --- a/docs/platforms/react-native/common/sourcemaps/troubleshooting/legacy-uploading-methods.mdx +++ b/docs/platforms/react-native/common/sourcemaps/troubleshooting/legacy-uploading-methods.mdx @@ -4,7 +4,7 @@ description: "Learn about how to upload source maps with older SDKs and Sentry t sidebar_order: 5 --- -This page describes how to upload source maps for older React Native SDKs. If you're using the latest version of the SDK, [follow these instructions](/platforms/react-native/sourcemaps). +This page describes how to upload source maps for older React Native SDKs. If you're using the latest version of the SDK, [follow these instructions](/platforms/react-native/sourcemaps/). ## Legacy Instructions for Preparing Source Maps for a Release diff --git a/docs/platforms/react-native/common/sourcemaps/uploading/codepush.mdx b/docs/platforms/react-native/common/sourcemaps/uploading/codepush.mdx index de858251a889d..16b1ede8f6e29 100644 --- a/docs/platforms/react-native/common/sourcemaps/uploading/codepush.mdx +++ b/docs/platforms/react-native/common/sourcemaps/uploading/codepush.mdx @@ -9,8 +9,8 @@ Sentry's React Native SDK works out of the box with CodePush. To see readable st ## Prerequisites - [Sign up for an account](https://sentry.io/signup/) -- [Set up Sentry React Native SDK](/platforms/react-native) -- [Set up Sentry Metro Plugin](/platforms/react-native/manual-setup/metro) +- [Set up Sentry React Native SDK](/platforms/react-native/) +- [Set up Sentry Metro Plugin](/platforms/react-native/manual-setup/metro/) - The plugin ensures that Debug IDs are enabled and used to link source maps to bundles. ## Wrap Your App diff --git a/docs/platforms/react-native/common/tracing/instrumentation/automatic-instrumentation.mdx b/docs/platforms/react-native/common/tracing/instrumentation/automatic-instrumentation.mdx index db6196caf3bc1..c24711ba14d96 100644 --- a/docs/platforms/react-native/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/react-native/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -53,7 +53,7 @@ If you don't [wrap your root component with Sentry](#wrap-your-root-component), The SDK differentiates between a cold and a warm start, but doesn't track hot starts or resumes. The measurements are available under `measurements.app_start_warm` and `measurements.app_start_cold`. -Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Cold and warm start are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). @@ -176,7 +176,7 @@ These APIs require `enableStandaloneAppStartTracing` to be enabled. Unresponsive UI and animation hitches annoy users and degrade the user experience. Two measurements to track these types of experiences are slow frames and frozen frames. If you want your app to run smoothly, you should try to avoid both. The SDK adds these two measurements for the transactions you capture. -Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals). +Slow and frozen frames are Mobile Vitals, which you can learn about in the [full documentation](/product/dashboards/sentry-dashboards/mobile/mobile-vitals/). @@ -361,4 +361,4 @@ Sentry.init({ ## User Interaction Instrumentation -The UI instrumentation captures transactions and adds breadcrumbs for touch interactions. Gesture support using React Native Gesture Handler is also available with the `sentryTraceGesture` wrapper. Learn more about [User Interaction Instrumentation](/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation). +The UI instrumentation captures transactions and adds breadcrumbs for touch interactions. Gesture support using React Native Gesture Handler is also available with the `sentryTraceGesture` wrapper. Learn more about [User Interaction Instrumentation](/platforms/react-native/tracing/instrumentation/user-interaction-instrumentation/). diff --git a/docs/platforms/react-native/common/tracing/instrumentation/react-navigation.mdx b/docs/platforms/react-native/common/tracing/instrumentation/react-navigation.mdx index bbf87733d7141..72994b8b7e2a5 100644 --- a/docs/platforms/react-native/common/tracing/instrumentation/react-navigation.mdx +++ b/docs/platforms/react-native/common/tracing/instrumentation/react-navigation.mdx @@ -31,7 +31,7 @@ This option specifies how long the instrumentation will wait for the route to mo ### enableTimeToInitialDisplay -This option will enable automatic measuring of the time to initial display for each route. To learn more see [Time to Initial Display](/platforms/react-native/tracing/instrumentation/time-to-display). The default value is `false`. +This option will enable automatic measuring of the time to initial display for each route. To learn more see [Time to Initial Display](/platforms/react-native/tracing/instrumentation/time-to-display/). The default value is `false`. ### ignoreEmptyBackNavigationTransactions diff --git a/docs/platforms/react-native/common/tracing/instrumentation/time-to-display.mdx b/docs/platforms/react-native/common/tracing/instrumentation/time-to-display.mdx index fcef86dc360d9..44c46470623a4 100644 --- a/docs/platforms/react-native/common/tracing/instrumentation/time-to-display.mdx +++ b/docs/platforms/react-native/common/tracing/instrumentation/time-to-display.mdx @@ -18,7 +18,7 @@ To automatically measure Time to Initial Display of React Navigation Screens, en ### Notes -- To learn more about Sentry's React Navigation integration, see the [Automatic Instrumentation page](/platforms/react-native/tracing/instrumentation/automatic-instrumentation). +- To learn more about Sentry's React Navigation integration, see the [Automatic Instrumentation page](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/). - The measured value of Time to Initial Display starts when React Navigation dispatches the navigation event and ends when the next frame after the native Screen component initialization is rendered. diff --git a/docs/platforms/react-native/common/troubleshooting/index.mdx b/docs/platforms/react-native/common/troubleshooting/index.mdx index 1025b9794266a..9c383088e35b6 100644 --- a/docs/platforms/react-native/common/troubleshooting/index.mdx +++ b/docs/platforms/react-native/common/troubleshooting/index.mdx @@ -15,7 +15,7 @@ Please read the [Android developer documentation](https://developer.android.com/ ## "Missing API declaration" after App Store review -Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/react-native/data-management/apple-privacy-manifest) guide. +Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use, including the reasons under which they use it. If you received an email from Apple with the message "ITMS-91053: Missing API declaration", your app doesn't fulfill the requirements. To solve this, follow our [Apple Privacy Manifest](/platforms/react-native/data-management/apple-privacy-manifest/) guide. ## App Start Numbers Are Too High To Be Accurate @@ -48,9 +48,9 @@ Common fixes to this issue include: - Checking that source maps are correctly uploaded with the exact same `release` and `dist` values as the event. They **must match** for source maps to upload correctly. - If you set a custom `release` and `dist`, confirming that you manually uploaded the sourcemaps since our automatic source map upload script will not detect the custom values. - Make sure that the name of the bundle in the stack trace matches exactly with the name in the source map. For example, if your stack frames say `app:///index.bundle`, the artifacts must be named `index.bundle` and `index.bundle.map` respectively. -- Checking that you're not disabling the [`RewriteFrames`](/platforms/javascript/configuration/integrations/rewriteframes) default integration by overwriting it, filtering it out, or setting `defaultIntegrations: false`. +- Checking that you're not disabling the [`RewriteFrames`](/platforms/javascript/configuration/integrations/rewriteframes/) default integration by overwriting it, filtering it out, or setting `defaultIntegrations: false`. -[For more details, please read the guide on React Native source maps.](/platforms/react-native/sourcemaps) +[For more details, please read the guide on React Native source maps.](/platforms/react-native/sourcemaps/) ### Source Maps With Hermes @@ -327,7 +327,7 @@ SENTRY_ALLOW_FAILURE=true npx react-native run-ios SENTRY_ALLOW_FAILURE=true npx react-native run-android ``` -Note that if the source maps upload fails, you'll have to do it [manually](/platforms/react-native/sourcemaps) later when the connection is restored. +Note that if the source maps upload fails, you'll have to do it [manually](/platforms/react-native/sourcemaps/) later when the connection is restored. When you remove the environmental variable in front of your build command, your build will work as before. diff --git a/docs/platforms/react-native/guides/expo/index.mdx b/docs/platforms/react-native/guides/expo/index.mdx index 564ecb802efc2..718a87dcc941a 100644 --- a/docs/platforms/react-native/guides/expo/index.mdx +++ b/docs/platforms/react-native/guides/expo/index.mdx @@ -180,7 +180,7 @@ Once the SDK is set up, you can also connect Sentry to [Expo Application Service -If you change your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you change your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/platforms/react-native/guides/expo/tracing/instrumentation/expo-router.mdx b/docs/platforms/react-native/guides/expo/tracing/instrumentation/expo-router.mdx index 4353f55d20362..0cb643847cf41 100644 --- a/docs/platforms/react-native/guides/expo/tracing/instrumentation/expo-router.mdx +++ b/docs/platforms/react-native/guides/expo/tracing/instrumentation/expo-router.mdx @@ -38,7 +38,7 @@ That's the whole setup. You don't need to add `reactNavigationIntegration` separ ### `enableTimeToInitialDisplay` -Enables automatic [Time to Initial Display](/platforms/react-native/guides/expo/tracing/instrumentation/time-to-display) measurement for each navigation. Not supported in Expo Go. Default: `false`. +Enables automatic [Time to Initial Display](/platforms/react-native/guides/expo/tracing/instrumentation/time-to-display/) measurement for each navigation. Not supported in Expo Go. Default: `false`. ### `routeChangeTimeoutMs` diff --git a/docs/platforms/ruby/common/enriching-events/attributes/index.mdx b/docs/platforms/ruby/common/enriching-events/attributes/index.mdx index 0266fffc11c1b..a14318eab5fe1 100644 --- a/docs/platforms/ruby/common/enriching-events/attributes/index.mdx +++ b/docs/platforms/ruby/common/enriching-events/attributes/index.mdx @@ -5,7 +5,7 @@ description: "Attributes automatically enrich logs and metrics with typed key-va -**Attributes** are key-value pairs you can attach to your telemetry. Unlike [tags](../tags/), which are indexed string pairs attached to events, attributes are designed for logs and metrics. +**Attributes** are key-value pairs you can attach to your telemetry. Unlike [tags](../tags/), which are indexed string pairs attached to events, attributes are designed for logs and metrics. Common uses include subscription tiers, feature flags, and other business context that helps you filter and query your telemetry. Attribute values can be strings, integers, floats, booleans, or values that can be serialized as JSON. diff --git a/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx index 6ba4c71df7ed9..92d6b04b52dca 100644 --- a/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/ruby/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/ruby/common/integrations/index.mdx b/docs/platforms/ruby/common/integrations/index.mdx index 3c0c1fb40034a..c7a953d2a1c90 100644 --- a/docs/platforms/ruby/common/integrations/index.mdx +++ b/docs/platforms/ruby/common/integrations/index.mdx @@ -66,7 +66,7 @@ The Rails integration also traces [Active Job](/platforms/ruby/guides/rails/inte ### OpenTelemetry -The OpenTelemetry integration is used for exporting spans instrumented by an OpenTelemetry SDK into Sentry. See the [OpenTelemetry Setup](/platforms/ruby/tracing/instrumentation/opentelemetry) instructions for more details. +The OpenTelemetry integration is used for exporting spans instrumented by an OpenTelemetry SDK into Sentry. See the [OpenTelemetry Setup](/platforms/ruby/tracing/instrumentation/opentelemetry/) instructions for more details. ### OpenTelemetry (OTLP) diff --git a/docs/platforms/ruby/common/integrations/otlp/index.mdx b/docs/platforms/ruby/common/integrations/otlp/index.mdx index f3277dfa86af4..09f1492727059 100644 --- a/docs/platforms/ruby/common/integrations/otlp/index.mdx +++ b/docs/platforms/ruby/common/integrations/otlp/index.mdx @@ -4,7 +4,7 @@ description: "Learn about using OTLP to automatically send OpenTelemetry Traces keywords: ["otlp", "otel", "opentelemetry"] --- -The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp). +The OTLP integration configures the Sentry SDK to automatically send trace data instrumented by an OpenTelemetry SDK to Sentry's [OpenTelemetry Protocol](https://opentelemetry.io/docs/specs/otel/protocol/) [ingestion endpoint](/concepts/otlp/). ## Install diff --git a/docs/platforms/ruby/common/troubleshooting.mdx b/docs/platforms/ruby/common/troubleshooting.mdx index 7745e49926eb5..969e71bd0ea14 100644 --- a/docs/platforms/ruby/common/troubleshooting.mdx +++ b/docs/platforms/ruby/common/troubleshooting.mdx @@ -31,7 +31,7 @@ sidebar_section: configuration - Ensure that the automatic instrumentation is sending performance data to Sentry by going to the **Performance** page in [sentry.io](https://sentry.io). - If the automatic instrumentation is not sending performance data, try using custom instrumentation. + to="/tracing/instrumentation/custom-instrumentation/">custom instrumentation. - Enable debug mode in the SDK and check the logs. ### Limitations diff --git a/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx b/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx index cd0fec435506b..e7583ecb9749f 100644 --- a/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/rust/common/enriching-events/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/unity/data-management/debug-files/upload/index.mdx b/docs/platforms/unity/data-management/debug-files/upload/index.mdx index d49913bf1ba1a..0fa02d4ceb852 100644 --- a/docs/platforms/unity/data-management/debug-files/upload/index.mdx +++ b/docs/platforms/unity/data-management/debug-files/upload/index.mdx @@ -29,7 +29,7 @@ true for mobile apps targeting Android or iOS, such as those developed with To make this easier, the `Sentry` NuGet package (as of version 3.26.1) includes the Sentry CLI as a bundled tool, and will invoke it when building your project if the msbuild property `SentryUploadSymbols` is set to true (default to false). -Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild) for details. +Refer to [msbuild configuration](/platforms/dotnet/configuration/msbuild/) for details. The remaining information on this page describes invoking the Sentry CLI manually. diff --git a/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx b/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx index bde4afae24bad..df05624f6743d 100644 --- a/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/unity/enriching-events/breadcrumbs/index.mdx @@ -5,7 +5,7 @@ description: "Learn more about what Sentry uses to create a trail of events (bre Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/platforms/unity/enriching-events/view-hierarchy/index.mdx b/docs/platforms/unity/enriching-events/view-hierarchy/index.mdx index 4e97f066e24b1..239bd60ccbd47 100644 --- a/docs/platforms/unity/enriching-events/view-hierarchy/index.mdx +++ b/docs/platforms/unity/enriching-events/view-hierarchy/index.mdx @@ -55,7 +55,7 @@ options.MaxViewHierarchyObjectChildCount = 20; ## Viewing View Hierarchy Attachments -View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details) page of that specific event. +View hierarchies appear in the "Attachments" tab, where you can view all attachments, as well as associated events. Click the event ID to open the [Issue Details](/product/issues/issue-details/) page of that specific event. diff --git a/docs/platforms/unity/usage/automatic-error-capture/index.mdx b/docs/platforms/unity/usage/automatic-error-capture/index.mdx index a0b0e86c46510..95e4fcc358a01 100644 --- a/docs/platforms/unity/usage/automatic-error-capture/index.mdx +++ b/docs/platforms/unity/usage/automatic-error-capture/index.mdx @@ -15,7 +15,7 @@ The Unity SDK automatically captures errors reported through Unity's logging sys ### `Debug.LogError` -`Debug.LogError` is captured as an error-level message event. Disable automatic capture in **Tools -> Sentry -> Logging**, or set `CaptureLogErrorEvents` to `false` in the [configure callback](/platforms/unity/configuration/options/programmatic-configuration). +`Debug.LogError` is captured as an error-level message event. Disable automatic capture in **Tools -> Sentry -> Logging**, or set `CaptureLogErrorEvents` to `false` in the [configure callback](/platforms/unity/configuration/options/programmatic-configuration/). Enable `AttachStacktrace` to include and parse the stack trace Unity provides with the log. On platforms other than WebGL, Unity 6 or later can include source lines in that stack trace when you enable source code line numbers in [Player Settings](https://docs.unity3d.com/6000.0/Documentation/Manual/il2cpp-managed-stack-traces.html). diff --git a/docs/platforms/unreal/configuration/debug-symbols/index.mdx b/docs/platforms/unreal/configuration/debug-symbols/index.mdx index 62489bee38928..8bc2253744b2c 100644 --- a/docs/platforms/unreal/configuration/debug-symbols/index.mdx +++ b/docs/platforms/unreal/configuration/debug-symbols/index.mdx @@ -8,7 +8,7 @@ Sentry requires [debug information files](/platforms/unreal/data-management/debu -For Android, debug symbols upload is handled by [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle). By default, it bumps Gradle version to 7.5 automatically, however one can fallback to using its legacy version in case compatibility issues with other third-party plugins arise. +For Android, debug symbols upload is handled by [Sentry Android Gradle Plugin](/platforms/android/configuration/gradle/). By default, it bumps Gradle version to 7.5 automatically, however one can fallback to using its legacy version in case compatibility issues with other third-party plugins arise. diff --git a/docs/platforms/unreal/data-management/data-collected.mdx b/docs/platforms/unreal/data-management/data-collected.mdx index 55b6554d1c674..513bff1f2ab0f 100644 --- a/docs/platforms/unreal/data-management/data-collected.mdx +++ b/docs/platforms/unreal/data-management/data-collected.mdx @@ -16,7 +16,7 @@ To enable sending the user's IP address, set screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. +The screenshot feature is disabled per default, but when enabled the screenshots may contain PII data. ## Device Information diff --git a/docs/platforms/unreal/enriching-events/breadcrumbs/index.mdx b/docs/platforms/unreal/enriching-events/breadcrumbs/index.mdx index 14d90be4a125a..31972ce89a3e8 100644 --- a/docs/platforms/unreal/enriching-events/breadcrumbs/index.mdx +++ b/docs/platforms/unreal/enriching-events/breadcrumbs/index.mdx @@ -10,7 +10,7 @@ og_image: /og-images/platforms-unreal-enriching-events-breadcrumbs.png Sentry uses _breadcrumbs_ to create a trail of events that happened prior to an issue. These events are very similar to traditional logs, but can record more rich structured data. -This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs). +This page provides an overview of manual breadcrumb recording and customization. Learn more about the information that displays on the **Issue Details** page and how you can filter breadcrumbs to quickly resolve issues in [Using Breadcrumbs](/product/issues/issue-details/breadcrumbs/). diff --git a/docs/pricing/quotas/manage-attachments-quota.mdx b/docs/pricing/quotas/manage-attachments-quota.mdx index 14427befc3dd1..09c0a4461db48 100644 --- a/docs/pricing/quotas/manage-attachments-quota.mdx +++ b/docs/pricing/quotas/manage-attachments-quota.mdx @@ -100,4 +100,4 @@ While you can't set filters for attachments directly, when you set inbound filte To avoid using up your attachments quota (which is based on size rather than the number of attachments sent), or having the attachment dropped entirely, consider limiting the size of values passed into Sentry's APIs. For example, if your application attaches application state or request bodies to Sentry events, truncate them first. -For more information, refer to our [Size Limits](/concepts/data-management/size-limits) guide. +For more information, refer to our [Size Limits](/concepts/data-management/size-limits/) guide. diff --git a/docs/product/agents/getting-started.mdx b/docs/product/agents/getting-started.mdx index 52af0eb931f06..73262f433dad2 100644 --- a/docs/product/agents/getting-started.mdx +++ b/docs/product/agents/getting-started.mdx @@ -25,7 +25,7 @@ To use [Conversations](/product/agents/conversations/), set a conversation ID fo To start sending AI agent data to Sentry, make sure you've created a Sentry project for your AI-enabled repository and follow one of the guides below: -- [Python](/platforms/python/agent-tracing) +- [Python](/platforms/python/agent-tracing/) - [Laravel](/platforms/php/guides/laravel/agent-tracing/) - [Node.js](/platforms/javascript/guides/node/agent-tracing/) - [Browser (JavaScript)](/platforms/javascript/agent-tracing-browser/) diff --git a/docs/product/dashboards/sentry-dashboards/backend/queries.mdx b/docs/product/dashboards/sentry-dashboards/backend/queries.mdx index 1056239ef9aef..195cbadc04b6a 100644 --- a/docs/product/dashboards/sentry-dashboards/backend/queries.mdx +++ b/docs/product/dashboards/sentry-dashboards/backend/queries.mdx @@ -39,7 +39,7 @@ Query monitoring works best with up-to-date SDK versions. The following minimum Sentry tries to extract metrics for all SQL-like dialects, as well as MongoDB. Other NoSQL databases like Elasticsearch, graph databases like Neo4j, and other non-SQL database systems are not currently eligible for this feature. -If you are using automatic instrumentation, query performance monitoring should work without any configuration. If you've manually instrumented Sentry, you'll need to make sure that your spans conform to our standards for the best experience: +If you are using automatic instrumentation, query performance monitoring should work without any configuration. If you've manually instrumented Sentry, you'll need to make sure that your spans conform to our standards for the best experience: - The span `op` field is set to an [eligible value](https://develop.sentry.dev/sdk/performance/span-operations/#database). - The span's description contains the full, parameterized query (e.g. `"SELECT * FROM users WHERE id = ?"`). Supported placeholder values for SQL are `%s`, `?`, `:c0` (e.g. `:c0`, `:c1`) and `$1` (e.g. `$1`, `$2`). MongoDB span descriptions should contain valid JSON, and placeholders should be the string `"?"`. diff --git a/docs/product/dashboards/sentry-dashboards/frontend/assets.mdx b/docs/product/dashboards/sentry-dashboards/frontend/assets.mdx index 3215d4955b3b5..febdb1f5a97d5 100644 --- a/docs/product/dashboards/sentry-dashboards/frontend/assets.mdx +++ b/docs/product/dashboards/sentry-dashboards/frontend/assets.mdx @@ -35,7 +35,7 @@ Sentry tries to extract metrics by looking at asset-related spans. The JavaScript SDK automatically generates `asset` spans on `pageload` and `navigation` transactions using the browser's [Resource Timing API](https://developer.mozilla.org/en-US/docs/Web/API/Performance_API/Resource_timing). -If you are using automatic instrumentation, asset monitoring should work without any configuration. +If you are using automatic instrumentation, asset monitoring should work without any configuration. If you've manually instrumented Sentry, you'll need to make sure that your spans conform to our standards for the best experience: diff --git a/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts.mdx b/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts.mdx index a2b9864137159..2578c73418129 100644 --- a/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts.mdx +++ b/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts.mdx @@ -16,7 +16,7 @@ The **App Starts** dashboard in [Sentry Dashboards](https://sentry.io/orgredirec **For Android:** - `>=7.4.0` for automatic instrumentation of app start spans and app start profiling -- [Performance-V2](/platforms/android/performance/instrumentation/perf-v2) feature flag (`<8.0.0`) and [App Start Profiling](/platforms/android/profiling/#app-start-profiling) must also be enabled in the SDK, e.g.: +- [Performance-V2](/platforms/android/performance/instrumentation/perf-v2/) feature flag (`<8.0.0`) and [App Start Profiling](/platforms/android/profiling/#app-start-profiling) must also be enabled in the SDK, e.g.: ```java {filename:MyApplication.java} import io.sentry.android.core.SentryAndroid; diff --git a/docs/product/dashboards/sentry-dashboards/outbound-api-requests.mdx b/docs/product/dashboards/sentry-dashboards/outbound-api-requests.mdx index 9f76b514d7299..a0c497d99ecb6 100644 --- a/docs/product/dashboards/sentry-dashboards/outbound-api-requests.mdx +++ b/docs/product/dashboards/sentry-dashboards/outbound-api-requests.mdx @@ -16,7 +16,7 @@ On the [Requests page](#requests-page), you get an overview of the domains that Network requests using non-HTTP protocols (FTP, WebSocket, etc.) are not supported at this time. -Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's automatic instrumentation documentation to see if it includes tracking HTTP requests. +Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's automatic instrumentation documentation to see if it includes tracking HTTP requests. If the SDK you're using doesn't automatically instrument HTTP requests, you can set up custom instrumentation. Dedicated platform documentation is available for these platforms: diff --git a/docs/product/issues/issue-details/index.mdx b/docs/product/issues/issue-details/index.mdx index 207e493802abf..bc668dd7c53cd 100644 --- a/docs/product/issues/issue-details/index.mdx +++ b/docs/product/issues/issue-details/index.mdx @@ -29,7 +29,7 @@ The main area of the page displays information about a specific event that's par ## Event Search -The embedded search bar allows you to search for events using any of the [event properties](/concepts/search/searchable-properties/events). Environment and time period can also be changed. Once the search is updated, the counts and graph below will be updated. Event navigations such as recommended, first, and last, and **View More Events** will also be updated to only show matching events. +The embedded search bar allows you to search for events using any of the [event properties](/concepts/search/searchable-properties/events/). Environment and time period can also be changed. Once the search is updated, the counts and graph below will be updated. Event navigations such as recommended, first, and last, and **View More Events** will also be updated to only show matching events. ## Trends & Aggregates @@ -123,7 +123,7 @@ You can set your own breadcrum ### Trace Preview -An abbreviated view of the related [trace](/concepts/key-terms/tracing/distributed-tracing) for the current transaction. +An abbreviated view of the related [trace](/concepts/key-terms/tracing/distributed-tracing/) for the current transaction. ![Trace Related Issue](./img/trace_related_issue.png) @@ -131,7 +131,7 @@ Sometimes the trace will be supplemented by a Trace-related Issue. A Trace-relat ### Session Replay -If you’ve enabled [Session Replay](/product/session-replay/), you’ll have access to a replay preview on the page (if there’s one associated with the event). Replays can be associated with both frontend and [backend errors](/product/session-replay#replays-for-backend-errors), as long as distributed tracing is set up. From here you can navigate to the rest of the replays recorded for this issue, or inspect this replay on the [Replay Details](/product/session-replay/replay-details/) page. +If you’ve enabled [Session Replay](/product/session-replay/), you’ll have access to a replay preview on the page (if there’s one associated with the event). Replays can be associated with both frontend and [backend errors](/product/session-replay/#replays-for-backend-errors), as long as distributed tracing is set up. From here you can navigate to the rest of the replays recorded for this issue, or inspect this replay on the [Replay Details](/product/session-replay/replay-details/) page. ### HTTP Request diff --git a/docs/product/issues/issue-details/performance-issues/function-regressions.mdx b/docs/product/issues/issue-details/performance-issues/function-regressions.mdx index 3c694afbbb2c8..784eeb8bec154 100644 --- a/docs/product/issues/issue-details/performance-issues/function-regressions.mdx +++ b/docs/product/issues/issue-details/performance-issues/function-regressions.mdx @@ -8,7 +8,7 @@ Function Regression issues capture a generic class of problems where the duratio ## Detection Criteria -Sentry can only detect Function Regression issues on projects that have [Profiling](/product/profiling) enabled. Sentry will periodically check the 95th percentile function duration of the most common application functions in your project. When a significant increase in the p95 value for function duration is detected and has been sustained for some time, a regression issue is created. +Sentry can only detect Function Regression issues on projects that have [Profiling](/product/profiling/) enabled. Sentry will periodically check the 95th percentile function duration of the most common application functions in your project. When a significant increase in the p95 value for function duration is detected and has been sustained for some time, a regression issue is created. ## Charts diff --git a/docs/product/issues/issue-details/performance-issues/n-one-api-calls.mdx b/docs/product/issues/issue-details/performance-issues/n-one-api-calls.mdx index c84a9f509e479..2a1ce17ba1492 100644 --- a/docs/product/issues/issue-details/performance-issues/n-one-api-calls.mdx +++ b/docs/product/issues/issue-details/performance-issues/n-one-api-calls.mdx @@ -42,7 +42,7 @@ View it by going to the **Issues** page in Sentry, clicking on the N+1 API Call ## Fingerprinting -Sentry computes the issue fingerprint based on the URLs of the repeating network calls. Sentry parameterizes the URLs by stripping integers, UUIDs, SHA1 hashes, and MD5 hashes. If you're finding that Sentry is failing to correctly group N+1 API Call issues, you can parameterize the `http.client` spans in your transactions by using the before-send-transaction hook if your platform supports it. +Sentry computes the issue fingerprint based on the URLs of the repeating network calls. Sentry parameterizes the URLs by stripping integers, UUIDs, SHA1 hashes, and MD5 hashes. If you're finding that Sentry is failing to correctly group N+1 API Call issues, you can parameterize the `http.client` spans in your transactions by using the before-send-transaction hook if your platform supports it. ## Example diff --git a/docs/product/issues/suspect-commits/index.mdx b/docs/product/issues/suspect-commits/index.mdx index 1f52065ea4915..a2cedf8e7d7ee 100644 --- a/docs/product/issues/suspect-commits/index.mdx +++ b/docs/product/issues/suspect-commits/index.mdx @@ -66,7 +66,7 @@ You can also upload code mappings in bulk using the [Sentry CLI](/cli/code-mappi -The following information is only valid for platforms that use traditional file paths. Platforms with package names require additional steps. For **Java**, read more on the [page on source context](/platforms/java/source-context#setting-up-code-mappings). +The following information is only valid for platforms that use traditional file paths. Platforms with package names require additional steps. For **Java**, read more on the [page on source context](/platforms/java/source-context/#setting-up-code-mappings). diff --git a/docs/product/monitors-and-alerts/monitors/crons/troubleshooting.mdx b/docs/product/monitors-and-alerts/monitors/crons/troubleshooting.mdx index 5d3b27727a570..77d5795f42d89 100644 --- a/docs/product/monitors-and-alerts/monitors/crons/troubleshooting.mdx +++ b/docs/product/monitors-and-alerts/monitors/crons/troubleshooting.mdx @@ -6,7 +6,7 @@ description: "Troubleshoot common issues with cron monitoring." -All monitors are automatically deactivated at the start of a new billing period if there's not enough [on-demand spend](/pricing/#on-demand-capacity) to cover all active monitors. Monitors can be manually activated based on on-demand availability. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors) for more details. +All monitors are automatically deactivated at the start of a new billing period if there's not enough [on-demand spend](/pricing/#on-demand-capacity) to cover all active monitors. Monitors can be manually activated based on on-demand availability. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors/) for more details. @@ -25,7 +25,7 @@ If the monitor environment continues to be broken after an additional 14 days, w **Important Notes:** - You can disable these notifications in your [personal notification settings](/product/notifications/notification-settings/) -- Muting a monitor does **not** stop billing. You will continue to be charged for muted monitors. To stop billing, you must deactivate or delete the monitor. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors) for more details. +- Muting a monitor does **not** stop billing. You will continue to be charged for muted monitors. To stop billing, you must deactivate or delete the monitor. See [Manage Your Cron Monitors](/pricing/quotas/manage-cron-monitors/) for more details. diff --git a/docs/product/profiling/getting-started.mdx b/docs/product/profiling/getting-started.mdx index 72a1ac4713042..a32ad887c80dc 100644 --- a/docs/product/profiling/getting-started.mdx +++ b/docs/product/profiling/getting-started.mdx @@ -6,9 +6,9 @@ description: "Get started with Profiling, which allows you to see code-level pro Continuous Profiling and UI Profiling are the latest iteration of Sentry’s profiling capabilities, but they are currently only supported in select SDKs as described below. -Other platforms are supported via the prior transaction-based Profiling product, but these will not benefit from new capabilities introduced by Continuous and UI Profiling (direct start/stop control over the profile lifecycle and removal of duration limits). For more information on the differences between transaction-based Profiling and Continuous/UI Profiling, read [this documentation](/product/profiling/transaction-vs-continuous-profiling). +Other platforms are supported via the prior transaction-based Profiling product, but these will not benefit from new capabilities introduced by Continuous and UI Profiling (direct start/stop control over the profile lifecycle and removal of duration limits). For more information on the differences between transaction-based Profiling and Continuous/UI Profiling, read [this documentation](/product/profiling/transaction-vs-continuous-profiling/). -If you are currently using transaction-based Profiling and want to migrate to Continuous Profiling or UI Profiling on a supported SDK, read the [migration guide](/product/profiling/continuous-ui-profiling-migration-guide). +If you are currently using transaction-based Profiling and want to migrate to Continuous Profiling or UI Profiling on a supported SDK, read the [migration guide](/product/profiling/continuous-ui-profiling-migration-guide/). All SDKs that currently support transaction-based Profiling will be migrated over time to support Continuous Profiling and UI Profiling. diff --git a/docs/product/profiling/index.mdx b/docs/product/profiling/index.mdx index 3282124b0a8c4..0ded0d4f7c7e7 100644 --- a/docs/product/profiling/index.mdx +++ b/docs/product/profiling/index.mdx @@ -67,14 +67,14 @@ The **Transactions** tab, by default, shows a list of all transactions in the se ![Transactions tab on the Profiling page](./img/profiling-page-transactions.png) -Click the name of a transaction to navigate to the **Transaction Summary** page, which contains aggregated performance data that is scoped to that transaction. By default, the **Profiles** tab is selected, which contains an [aggregate flame graph](/product/profiling/flame-charts-graphs) showing the most frequent code paths that were profiled within that transaction. This flame graph behaves the same as the flame graph in the **Aggregate Flamegraph** tab described below. +Click the name of a transaction to navigate to the **Transaction Summary** page, which contains aggregated performance data that is scoped to that transaction. By default, the **Profiles** tab is selected, which contains an [aggregate flame graph](/product/profiling/flame-charts-graphs/) showing the most frequent code paths that were profiled within that transaction. This flame graph behaves the same as the flame graph in the **Aggregate Flamegraph** tab described below. ![Profiles tab on the Transaction Summary page](./img/transaction-summary-profiles.png) ### Aggregate Flamegraph Tab -The **Aggregate Flamegraph** tab shows a [flame graph](/product/profiling/flame-charts-graphs) with aggregated information on the frequency of code paths within the selected projects. +The **Aggregate Flamegraph** tab shows a [flame graph](/product/profiling/flame-charts-graphs/) with aggregated information on the frequency of code paths within the selected projects. ![Aggregate Flamegraph tab on the Profiling page](./img/profiling-page-aggregate-flamegraph.png) @@ -96,6 +96,6 @@ The other way is to click the **Profiles** tab in the Trace View, which will sho ## Getting Started -Read the [Getting Started guide](/product/profiling/getting-started) to start using Continuous Profiling and UI Profiling. +Read the [Getting Started guide](/product/profiling/getting-started/) to start using Continuous Profiling and UI Profiling. diff --git a/docs/product/profiling/profile-details.mdx b/docs/product/profiling/profile-details.mdx index a8570fade7275..a42a2c33c9a1b 100644 --- a/docs/product/profiling/profile-details.mdx +++ b/docs/product/profiling/profile-details.mdx @@ -7,7 +7,7 @@ og_image: /og-images/product-explore-profiling-profile-details.png Profiling can be used to gain insight into the exact functions and lines of code that are impacting performance. Each profile has a detailed view that illustrates the code that was running in your application and service while the profile was collected, with different ways to filter and visualize the data. To learn how to set up profiling and access profiling data, see the [**Profiling**](/product/profiling/) documentation. -The main visualization on the Profile Details page is a flame graph. Learn more about flame graphs in [**Flame Graphs and Aggregated Flame Graphs**](/product/profiling/flame-charts-graphs). +The main visualization on the Profile Details page is a flame graph. Learn more about flame graphs in [**Flame Graphs and Aggregated Flame Graphs**](/product/profiling/flame-charts-graphs/). ## Thread Selector diff --git a/docs/product/profiling/transaction-vs-continuous-profiling.mdx b/docs/product/profiling/transaction-vs-continuous-profiling.mdx index db498b81c0673..91af2310fef42 100644 --- a/docs/product/profiling/transaction-vs-continuous-profiling.mdx +++ b/docs/product/profiling/transaction-vs-continuous-profiling.mdx @@ -20,7 +20,7 @@ Continuous Profiling & UI Profiling were designed to address these limitations a The Continuous Profiling product was designed to help debug performance bottlenecks on backend applications and services. The recommended way of using Continuous Profiling is to start the profiler when a service starts, and stop profiling when the service is terminated. By running the profiler continuously throughout the service’s lifetime, Sentry can provide complete visibility into codepaths that might be causing excessive resource usage resulting in high infrastructure costs. -Continuous Profiling usage can be constrained in multiple ways in case you are concerned about cost or [performance overhead](/product/profiling/performance-overhead): +Continuous Profiling usage can be constrained in multiple ways in case you are concerned about cost or [performance overhead](/product/profiling/performance-overhead/): * Using client-side sampling controls to collect profiles on fewer instances of the same service (e.g. only profile 10% of the instances of a service) * Use the `start_profiler` and `stop_profiler` APIs to selectively profile only known performance-critical parts of the service @@ -29,7 +29,7 @@ Continuous Profiling usage can be constrained in multiple ways in case you are c The UI Profiling product was designed to help debug performance bottlenecks on frontend applications. These bottlenecks typically cause user-facing issues like janky scrolling or animations, high interaction latency, and slow loading times. The recommended way of using UI Profiling is to start the profiler when the user session begins, and stop profiling when the user session ends (when the application is terminated, or, if on mobile, when the application is backgrounded). By profiling complete user sessions, Sentry can provide complete visibility into codepaths that might be degrading the user experience and causing excessive battery usage on the user’s device. -UI Profiling usage can be constrained in multiple ways in case you are concerned about cost or [performance overhead](/product/profiling/performance-overhead): +UI Profiling usage can be constrained in multiple ways in case you are concerned about cost or [performance overhead](/product/profiling/performance-overhead/): * Using client-side sampling controls to collect profiles on fewer user sessions (e.g. only profile 10% of all user sessions) * Use the `start_profiler` and `stop_profiler` APIs to selectively profile only known performance-critical parts of the application diff --git a/docs/product/releases/health/index.mdx b/docs/product/releases/health/index.mdx index b4c8753dd2235..2eea270593da2 100644 --- a/docs/product/releases/health/index.mdx +++ b/docs/product/releases/health/index.mdx @@ -13,7 +13,7 @@ Note, that Sessions (as described below) are not the same as a [Session Replay]( -You can monitor the health of releases by observing user adoption, usage of your application, percentage of [crashes](#crashes--unhandled), and [session data](#sessions). Release health data provides insight into the impact of crashes and bugs related to user experience and reveals trends with each new issue through the release details, graphs, and filters. This data is primarily displayed on the [Releases](/product/releases/) and [Release Details](/product/releases/release-details) pages, but is also reflected in other parts of [sentry.io](https://sentry.io). +You can monitor the health of releases by observing user adoption, usage of your application, percentage of [crashes](#crashes--unhandled), and [session data](#sessions). Release health data provides insight into the impact of crashes and bugs related to user experience and reveals trends with each new issue through the release details, graphs, and filters. This data is primarily displayed on the [Releases](/product/releases/) and [Release Details](/product/releases/release-details/) pages, but is also reflected in other parts of [sentry.io](https://sentry.io). > Many SDKs automatically manage the start and end of [sessions](#sessions) when the SDK is initialized, but release health configuration is key to ensuring you're receiving useful data, so check out our information on [which SDKs support release health](/product/releases/setup/#release-health) for links to configuring the SDK, as needed. diff --git a/docs/product/releases/setup/release-automation/bitbucket-pipelines/index.mdx b/docs/product/releases/setup/release-automation/bitbucket-pipelines/index.mdx index 8fe15d4728278..4ecf124197b72 100644 --- a/docs/product/releases/setup/release-automation/bitbucket-pipelines/index.mdx +++ b/docs/product/releases/setup/release-automation/bitbucket-pipelines/index.mdx @@ -5,7 +5,7 @@ description: "Learn how Sentry and Bitbucket Pipelines automate release manageme -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/product/releases/setup/release-automation/netlify/index.mdx b/docs/product/releases/setup/release-automation/netlify/index.mdx index 13677e9f93c02..859cac12d7607 100644 --- a/docs/product/releases/setup/release-automation/netlify/index.mdx +++ b/docs/product/releases/setup/release-automation/netlify/index.mdx @@ -5,7 +5,7 @@ description: "Learn how Sentry and Netlify automate release management and help -If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting). +If you make changes to your organization slug, you'll need to update your configuration for this integration. Learn more in our [troubleshooting guide](/integrations/troubleshooting/). diff --git a/docs/product/sentry-toolbar/index.mdx b/docs/product/sentry-toolbar/index.mdx index 43d92f08d2ccf..e9b2b1f55af18 100644 --- a/docs/product/sentry-toolbar/index.mdx +++ b/docs/product/sentry-toolbar/index.mdx @@ -44,7 +44,7 @@ After setting up the Sentry Toolbar you’ll see a “Login to Sentry” button After clicking the button, you will see a pop-up window for logging in to Sentry. ![Sentry log in pop up](./img/login-popup.png) -If it's your first time [setting up the Sentry Toolbar](/product/sentry-toolbar/setup) , there will be a button with a link to Sentry's Toolbar settings page to configure your domain. +If it's your first time [setting up the Sentry Toolbar](/product/sentry-toolbar/setup/) , there will be a button with a link to Sentry's Toolbar settings page to configure your domain. ![Toolbar configure domains button](./img/configure-domain.png) Learn more about setting up the Toolbar, including configuring a feature flag provider and integrating the toolbar in different environments, on the next page. diff --git a/docs/product/snapshots/uploading-snapshots/index.mdx b/docs/product/snapshots/uploading-snapshots/index.mdx index 4d29e5fefb893..932b84e30e996 100644 --- a/docs/product/snapshots/uploading-snapshots/index.mdx +++ b/docs/product/snapshots/uploading-snapshots/index.mdx @@ -8,7 +8,7 @@ description: Structure your snapshot directory and upload from CI with sentry-cl -Snapshots works for any platform with a frontend. You can view specific platform examples [here](/product/snapshots#recommended-platform-workflows). This page covers the general upload structure and metadata schema. +Snapshots works for any platform with a frontend. You can view specific platform examples [here](/product/snapshots/#recommended-platform-workflows). This page covers the general upload structure and metadata schema. ## Upload command diff --git a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx index b41192ff586b0..e5c650b7da4ed 100644 --- a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx +++ b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx @@ -211,7 +211,7 @@ Select known parts of the schema using the following: Select attachment and parts of attachments, see [Attachment Scrubbing](../attachment-scrubbing) for details. - `$attachments`: Root selector for attachments. -- `$minidump`: Selector for [minidump](/platforms/native/guides/minidumps) attachments. +- `$minidump`: Selector for [minidump](/platforms/native/guides/minidumps/) attachments. - `$binary`: Matches all binary data fields in attachments. ### Escaping Special Characters diff --git a/docs/security-legal-pii/scrubbing/attachment-scrubbing.mdx b/docs/security-legal-pii/scrubbing/attachment-scrubbing.mdx index 6a0d4ced02887..d95d1c0486ebc 100644 --- a/docs/security-legal-pii/scrubbing/attachment-scrubbing.mdx +++ b/docs/security-legal-pii/scrubbing/attachment-scrubbing.mdx @@ -7,7 +7,7 @@ description: "Learn about scrubbing attachments if they contain PII." --- PII can be included in attachments which are included in events. -[Minidumps](/platforms/native/guides/minidumps), a common attachment type for native crash reports, may contain PII in various sections of the file. +[Minidumps](/platforms/native/guides/minidumps/), a common attachment type for native crash reports, may contain PII in various sections of the file. ## Data Scrubbing Methods in Attachments diff --git a/includes/apple-platform-getting-started.mdx b/includes/apple-platform-getting-started.mdx index a93c778bee1c9..de03add5139f0 100644 --- a/includes/apple-platform-getting-started.mdx +++ b/includes/apple-platform-getting-started.mdx @@ -425,9 +425,9 @@ if (error) { ## Next Steps - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn more about Sentry's Apple SDK features +- Learn more about Sentry's Apple SDK features - Add readable stack traces to errors -- Add Apple Privacy manifest +- Add Apple Privacy manifest ## FAQ diff --git a/includes/build-distribution/intro.mdx b/includes/build-distribution/intro.mdx index 84a3b4a020d90..eec388a8d0f15 100644 --- a/includes/build-distribution/intro.mdx +++ b/includes/build-distribution/intro.mdx @@ -1,2 +1,2 @@ -[Build Distribution](/product/build-distribution) helps you securely distribute iOS and Android builds to your internal teams and beta testers. +[Build Distribution](/product/build-distribution/) helps you securely distribute iOS and Android builds to your internal teams and beta testers. Streamline your distribution workflow with automated uploads from CI. diff --git a/includes/dart-integrations/app-start-instrumentation.mdx b/includes/dart-integrations/app-start-instrumentation.mdx index c95bd89e4e034..f4b20d39ccabb 100644 --- a/includes/dart-integrations/app-start-instrumentation.mdx +++ b/includes/dart-integrations/app-start-instrumentation.mdx @@ -92,7 +92,7 @@ await SentryFlutter.init((options) { Standalone app start tracing requires tracing to be enabled and is only supported on Android and iOS. On every other platform the SDK keeps attaching app start data to the first `ui.load` transaction. -Because the app start uses the `app.start` operation, you can use `tracesSampler` to give app starts a dedicated sample rate without raising your overall sample rate. Where you read that operation depends on your trace lifecycle: transaction mode exposes it on the transaction context, while stream mode carries it as the span's `sentry.op` attribute. +Because the app start uses the `app.start` operation, you can use `tracesSampler` to give app starts a dedicated sample rate without raising your overall sample rate. Where you read that operation depends on your trace lifecycle: transaction mode exposes it on the transaction context, while stream mode carries it as the span's `sentry.op` attribute. ```dart {tabTitle:Transaction Mode (Default)} {mdExpandTabs} await SentryFlutter.init((options) { diff --git a/includes/dart-integrations/index.mdx b/includes/dart-integrations/index.mdx index 0faf6b3afb3eb..116317896465a 100644 --- a/includes/dart-integrations/index.mdx +++ b/includes/dart-integrations/index.mdx @@ -3,21 +3,21 @@ | **Integration** | **Auto
Enabled** | **Errors** | **Tracing** | **Additional
Context** | | ----------------------------------------------------- | :--------------: | :--------: | :---------: | :--------------------: | -| [`App Start`](/platforms/dart/guides/flutter/integrations/app-start-instrumentation) | ✓ | | ✓ | | -| [`Asset Bundle`](/platforms/dart/guides/flutter/integrations/asset-bundle-instrumentation) | | | ✓ | | -| [`Dio`](/platforms/dart/guides/flutter/integrations/dio) | | ✓ | ✓ | ✓ | -| [`Drift`](/platforms/dart/guides/flutter/integrations/drift-instrumentation) | | | ✓ | | -| [`File`](/platforms/dart/guides/flutter/integrations/file) | | ✓ | | | -| [`GraphQL`](/platforms/dart/guides/flutter/integrations/graphql) | | ✓ | ✓ | ✓ | -| [`Hive`](/platforms/dart/guides/flutter/integrations/hive-instrumentation) | | | ✓ | | -| [`Http`](/platforms/dart/guides/flutter/integrations/http-integration) | | ✓ | ✓ | ✓ | -| [`Isar`](/platforms/dart/guides/flutter/integrations/isar-instrumentation) | | | ✓ | | -| [`Logging`](/platforms/dart/guides/flutter/integrations/logging) | | ✓ | | ✓ | -| [`Routing`](/platforms/dart/guides/flutter/integrations/routing-instrumentation) | | | ✓ | ✓ | -| [`Slow and Frozen Frames`](/platforms/dart/guides/flutter/integrations/slow-and-frozen-frames-instrumentation) | ✓ * | | ✓ | | -| [`Sqflite`](/platforms/dart/guides/flutter/integrations/sqflite-instrumentation) | | | ✓ | | -| [`User Interaction`](/platforms/dart/guides/flutter/integrations/user-interaction-instrumentation) | | | ✓ | ✓ | -| [`Firebase Remote Config`](/platforms/dart/guides/flutter/integrations/firebase-remote-config) | | | | ✓ | +| [`App Start`](/platforms/dart/guides/flutter/integrations/app-start-instrumentation/) | ✓ | | ✓ | | +| [`Asset Bundle`](/platforms/dart/guides/flutter/integrations/asset-bundle-instrumentation/) | | | ✓ | | +| [`Dio`](/platforms/dart/guides/flutter/integrations/dio/) | | ✓ | ✓ | ✓ | +| [`Drift`](/platforms/dart/guides/flutter/integrations/drift-instrumentation/) | | | ✓ | | +| [`File`](/platforms/dart/guides/flutter/integrations/file/) | | ✓ | | | +| [`GraphQL`](/platforms/dart/guides/flutter/integrations/graphql/) | | ✓ | ✓ | ✓ | +| [`Hive`](/platforms/dart/guides/flutter/integrations/hive-instrumentation/) | | | ✓ | | +| [`Http`](/platforms/dart/guides/flutter/integrations/http-integration/) | | ✓ | ✓ | ✓ | +| [`Isar`](/platforms/dart/guides/flutter/integrations/isar-instrumentation/) | | | ✓ | | +| [`Logging`](/platforms/dart/guides/flutter/integrations/logging/) | | ✓ | | ✓ | +| [`Routing`](/platforms/dart/guides/flutter/integrations/routing-instrumentation/) | | | ✓ | ✓ | +| [`Slow and Frozen Frames`](/platforms/dart/guides/flutter/integrations/slow-and-frozen-frames-instrumentation/) | ✓ * | | ✓ | | +| [`Sqflite`](/platforms/dart/guides/flutter/integrations/sqflite-instrumentation/) | | | ✓ | | +| [`User Interaction`](/platforms/dart/guides/flutter/integrations/user-interaction-instrumentation/) | | | ✓ | ✓ | +| [`Firebase Remote Config`](/platforms/dart/guides/flutter/integrations/firebase-remote-config/) | | | | ✓ | *Slow and Frozen Frames* should work automatically, however if `WidgetsFlutterBinding` is initialized before `SentryFlutter.init`, then this instrumentation will not work automatically. diff --git a/includes/insights-requests-body.mdx b/includes/insights-requests-body.mdx index 325dc5d1b9ee2..d14d621e1d014 100644 --- a/includes/insights-requests-body.mdx +++ b/includes/insights-requests-body.mdx @@ -12,7 +12,7 @@ On the [**Requests** page](#requests-page), you get an overview of the domains t Network requests using non-HTTP protocols (FTP, WebSocket, etc.) are not supported at this time. -Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's automatic instrumentation documentation to see if it includes tracking HTTP requests. +Availability of HTTP request monitoring depends on the SDK your application uses. In most cases, Sentry's SDKs automatically enable HTTP request tracking. You can check your SDK's automatic instrumentation documentation to see if it includes tracking HTTP requests. If the SDK you're using doesn't automatically instrument HTTP requests, you can set up custom instrumentation. Dedicated platform documentation is available for these platforms: diff --git a/includes/logs/javascript-pino-integration.mdx b/includes/logs/javascript-pino-integration.mdx index 23ff57d15eff0..7bc0935672b10 100644 --- a/includes/logs/javascript-pino-integration.mdx +++ b/includes/logs/javascript-pino-integration.mdx @@ -9,4 +9,4 @@ Sentry.init({ }); ``` -You can look at the Pino integration documentation for more information on the options you can pass to the `pinoIntegration`. +You can look at the Pino integration documentation for more information on the options you can pass to the `pinoIntegration`. diff --git a/includes/sentry-cli-sourcemaps.mdx b/includes/sentry-cli-sourcemaps.mdx index 3ddde2b94a4c2..77ceff5d2821e 100644 --- a/includes/sentry-cli-sourcemaps.mdx +++ b/includes/sentry-cli-sourcemaps.mdx @@ -148,7 +148,7 @@ sentry-cli sourcemaps upload --release= /path/to/directory Running `upload` with `--release` **doesn't automatically create a release in Sentry**. -Either wait until the first event with the new release set in `Sentry.init` is sent to Sentry, or create a release with the same name in a separate step [with the CLI](/cli/releases). +Either wait until the first event with the new release set in `Sentry.init` is sent to Sentry, or create a release with the same name in a separate step [with the CLI](/cli/releases/). diff --git a/includes/size-analysis/watch-architecture-thinning.mdx b/includes/size-analysis/watch-architecture-thinning.mdx index 6a6b44d9f7326..0ca2b6ae0e984 100644 --- a/includes/size-analysis/watch-architecture-thinning.mdx +++ b/includes/size-analysis/watch-architecture-thinning.mdx @@ -1 +1 @@ -WatchOS apps produced by Xcode often contain both `arm64_32` and `arm64` architectures in a single fat binary. By default Sentry calculates the size of this data as-is, however, your end users will only download whatever architecture is necessary for their device. It's recommended to apply [App Thinning](/platforms/apple/guides/ios/size-analysis#app-thinning) before uploading for more representative results. +WatchOS apps produced by Xcode often contain both `arm64_32` and `arm64` architectures in a single fat binary. By default Sentry calculates the size of this data as-is, however, your end users will only download whatever architecture is necessary for their device. It's recommended to apply [App Thinning](/platforms/apple/guides/ios/size-analysis/#app-thinning) before uploading for more representative results. diff --git a/platform-includes/configuration/config-intro/java.spring-boot.mdx b/platform-includes/configuration/config-intro/java.spring-boot.mdx index 161cb699979a6..21f940f1a610b 100644 --- a/platform-includes/configuration/config-intro/java.spring-boot.mdx +++ b/platform-includes/configuration/config-intro/java.spring-boot.mdx @@ -13,4 +13,4 @@ sentry: release: "io.sentry.samples.console@3.0.0+1" ``` -More advanced configuration options that can be registered as Spring beans are described at the [Advanced Usage](/platforms/java/guides/spring-boot/advanced-usage) page. +More advanced configuration options that can be registered as Spring beans are described at the [Advanced Usage](/platforms/java/guides/spring-boot/advanced-usage/) page. diff --git a/platform-includes/debug-symbols/dart-plugin/dart.flutter.mdx b/platform-includes/debug-symbols/dart-plugin/dart.flutter.mdx index 3e2fa395140cf..b5074bfee8641 100644 --- a/platform-includes/debug-symbols/dart-plugin/dart.flutter.mdx +++ b/platform-includes/debug-symbols/dart-plugin/dart.flutter.mdx @@ -128,7 +128,7 @@ sentry { ProGuard mapping upload is enabled automatically by the Sentry Android Gradle Plugin. Alternatively, you can use the [Sentry CLI](/cli/dif/#proguard-mapping-upload) to manually upload ProGuard mapping files. -For more information, see the [Android Gradle Plugin guide](/platforms/android/configuration/gradle). +For more information, see the [Android Gradle Plugin guide](/platforms/android/configuration/gradle/). diff --git a/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx index 6804c9d160ec3..7a056c9eeec7e 100644 --- a/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx +++ b/platform-includes/distributed-tracing/custom-instrumentation/browser/javascript.mdx @@ -54,7 +54,7 @@ To learn more about distributed tracing, see our stream mode) connected to that incoming backend trace. +To do this, have your server render HTML `` tags with the Sentry trace information. In your frontend, extract that tracing information when the page is loading and use it to create new transactions (or service spans if you're using stream mode) connected to that incoming backend trace. Some Sentry backend SDKs provide a built-in way to inject these `` tags into rendered HTML. For example: diff --git a/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx b/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx index 127ca5ac3527d..7251729460cdc 100644 --- a/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx +++ b/platform-includes/distributed-tracing/custom-instrumentation/server/javascript.mdx @@ -45,7 +45,7 @@ http.createServer((request, response) => { }); ``` -In this example, we create a new transaction (or service span if you're using stream mode) that is attached to the trace specified in the `sentry-trace` and `baggage` headers. +In this example, we create a new transaction (or service span if you're using stream mode) that is attached to the trace specified in the `sentry-trace` and `baggage` headers. ### Injecting Tracing Information Into HTML diff --git a/platform-includes/enriching-events/breadcrumbs/automatic-breadcrumbs/react-native.mdx b/platform-includes/enriching-events/breadcrumbs/automatic-breadcrumbs/react-native.mdx index 207318a8d8bcc..dd68f5f3f0c0b 100644 --- a/platform-includes/enriching-events/breadcrumbs/automatic-breadcrumbs/react-native.mdx +++ b/platform-includes/enriching-events/breadcrumbs/automatic-breadcrumbs/react-native.mdx @@ -8,4 +8,4 @@ More breadcrumbs can be captured by the React Native SDK: - For interaction breadcrumbs, wrap your root component using the [`Sentry.wrap`](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#wrap-your-root-component) method. - For navigation breadcrumbs, use one of the [SDK's navigation integrations](/platforms/react-native/tracing/instrumentation/automatic-instrumentation/#enable-routing-instrumentation). - `HTTP` requests are included in breadcrumbs by default. -- To track redux actions and latest store state, use [`Sentry.createReduxEnhancer`](/platforms/javascript/guides/react/features/redux). +- To track redux actions and latest store state, use [`Sentry.createReduxEnhancer`](/platforms/javascript/guides/react/features/redux/). diff --git a/platform-includes/feature-flags/evaluation-tracking-index/android.mdx b/platform-includes/feature-flags/evaluation-tracking-index/android.mdx index 350cf8f536a00..aed3915af21d4 100644 --- a/platform-includes/feature-flags/evaluation-tracking-index/android.mdx +++ b/platform-includes/feature-flags/evaluation-tracking-index/android.mdx @@ -1,6 +1,6 @@ If you use a third-party SDK to evaluate feature flags, you can enable a Sentry SDK integration to track those evaluations. Integrations are provider specific. Documentation for supported SDKs is listed below. -- LaunchDarkly +- LaunchDarkly ### Generic API diff --git a/platform-includes/feature-flags/evaluation-tracking-index/java.mdx b/platform-includes/feature-flags/evaluation-tracking-index/java.mdx index ae7e52efcb0ae..c0cbd91c60b46 100644 --- a/platform-includes/feature-flags/evaluation-tracking-index/java.mdx +++ b/platform-includes/feature-flags/evaluation-tracking-index/java.mdx @@ -1,7 +1,7 @@ If you use a third-party SDK to evaluate feature flags, you can enable a Sentry SDK integration to track those evaluations. Integrations are provider specific. Documentation for supported SDKs is listed below. -- OpenFeature -- LaunchDarkly +- OpenFeature +- LaunchDarkly ### Generic API diff --git a/platform-includes/feature-flags/requirements/php.mdx b/platform-includes/feature-flags/requirements/php.mdx index ec5e09e86211b..69ad15fda4509 100644 --- a/platform-includes/feature-flags/requirements/php.mdx +++ b/platform-includes/feature-flags/requirements/php.mdx @@ -1 +1 @@ -- [Sentry SDK](/platforms/php) version `4.18.1` or above. +- [Sentry SDK](/platforms/php/) version `4.18.1` or above. diff --git a/platform-includes/getting-started-complete/javascript.astro.mdx b/platform-includes/getting-started-complete/javascript.astro.mdx index 2e20147c82470..3f6c9b3f26c6f 100644 --- a/platform-includes/getting-started-complete/javascript.astro.mdx +++ b/platform-includes/getting-started-complete/javascript.astro.mdx @@ -598,8 +598,8 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors - Learn more about [deploying Astro apps to Cloudflare](/platforms/javascript/guides/cloudflare/frameworks/astro/) - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts @@ -608,15 +608,15 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Continue to customize your configuration -- Learn how to manually capture errors +- Continue to customize your configuration +- Learn how to manually capture errors - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-complete/javascript.mdx b/platform-includes/getting-started-complete/javascript.mdx index 3a1b63f945dc5..023499f5004d5 100644 --- a/platform-includes/getting-started-complete/javascript.mdx +++ b/platform-includes/getting-started-complete/javascript.mdx @@ -52,11 +52,11 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Extend Sentry to your backend using one of our [SDKs](/) - Learn how to [manually capture errors](/platforms/javascript/usage/) - Continue to [customize your configuration](/platforms/javascript/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Find various support topics in troubleshooting +- Find various support topics in troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-complete/javascript.nuxt.mdx b/platform-includes/getting-started-complete/javascript.nuxt.mdx index 51b199cfadafc..0f82954753ddc 100644 --- a/platform-includes/getting-started-complete/javascript.nuxt.mdx +++ b/platform-includes/getting-started-complete/javascript.nuxt.mdx @@ -253,7 +253,7 @@ dotenv.config(); **Sentry's server-side monitoring doesn't work in development mode**. To enable it, you first need to build your application and then load the Sentry server-side config using the `--import` flag when running your application. -Check out the `--import` CLI flag docs for setup instructions. +Check out the `--import` CLI flag docs for setup instructions. @@ -524,7 +524,7 @@ Once you have your test code in place, you need to build your project since Sent -Then start your app and make sure to load Sentry on the server side by explicitly adding the Sentry server config in the build output via{" "} `--import`. +Then start your app and make sure to load Sentry on the server side by explicitly adding the Sentry server config in the build output via{" "} `--import`. @@ -558,15 +558,15 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/nuxt/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/nuxt/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - Learn how to [track your Vue components or your Pinia store](/platforms/javascript/guides/nuxt/features/) - Learn how to [add support for different Nitro deployment presets](/platforms/javascript/guides/nuxt/features/nitro-deployment-presets/) (like Cloudflare) - If you encountered issues with setting up Sentry manually, [try our installation wizard](/platforms/javascript/guides/nuxt/) -- Find various support topics in troubleshooting -- Review alternative installation methods +- Find various support topics in troubleshooting +- Review alternative installation methods - [Get support](https://www.sentry.help/en/) @@ -577,12 +577,12 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/nuxt/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/nuxt/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - Learn how to [track your Vue components or your Pinia store](/platforms/javascript/guides/nuxt/features/) -- Find various support topics in Cloudflare troubleshooting and [Nuxt troubleshooting](/platforms/javascript/guides/nuxt/troubleshooting/) +- Find various support topics in Cloudflare troubleshooting and [Nuxt troubleshooting](/platforms/javascript/guides/nuxt/troubleshooting/) - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-complete/javascript.remix.mdx b/platform-includes/getting-started-complete/javascript.remix.mdx index e60c0a31c32e6..32b4e258df482 100644 --- a/platform-includes/getting-started-complete/javascript.remix.mdx +++ b/platform-includes/getting-started-complete/javascript.remix.mdx @@ -556,15 +556,15 @@ At this point, you should have integrated Sentry into your Remix application and Now's a good time to customize your setup and look into more advanced topics. Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup -- Learn how to manually capture errors -- Continue to customize your configuration +- Learn how to manually capture errors +- Continue to customize your configuration - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts - If you encountered issues with the manual setup, try our installation wizard -- Find various topics in Troubleshooting +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) @@ -574,7 +574,7 @@ Now's a good time to customize your setup and look into more advanced topics. Ou - If you encountered issues with the manual setup, try our installation wizard -- Find various support topics in Cloudflare troubleshooting and [Remix troubleshooting](/platforms/javascript/guides/remix/troubleshooting/) +- Find various support topics in Cloudflare troubleshooting and [Remix troubleshooting](/platforms/javascript/guides/remix/troubleshooting/) - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-complete/javascript.sveltekit.mdx b/platform-includes/getting-started-complete/javascript.sveltekit.mdx index 04737b32817ad..d56e35f8c765f 100644 --- a/platform-includes/getting-started-complete/javascript.sveltekit.mdx +++ b/platform-includes/getting-started-complete/javascript.sveltekit.mdx @@ -649,7 +649,7 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/sveltekit/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/sveltekit/configuration/) -- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis#load-function-instrumentation) SvelteKit-specific features +- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis/#load-function-instrumentation) SvelteKit-specific features - Learn more about [deploying SvelteKit apps to Cloudflare Workers and Pages](/platforms/javascript/guides/cloudflare/frameworks/sveltekit/) - Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts @@ -667,12 +667,12 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Learn how to [manually capture errors](/platforms/javascript/guides/cloudflare/usage/) - Continue to [customize your configuration](/platforms/javascript/guides/cloudflare/configuration/) -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts -- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis#load-function-instrumentation) SvelteKit-specific features +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts +- Learn how to [manually instrument](/platforms/javascript/guides/sveltekit/apis/#load-function-instrumentation) SvelteKit-specific features -- Find various support topics in Cloudflare troubleshooting and [SvelteKit troubleshooting](/platforms/javascript/guides/sveltekit/troubleshooting/) +- Find various support topics in Cloudflare troubleshooting and [SvelteKit troubleshooting](/platforms/javascript/guides/sveltekit/troubleshooting/) - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-install/java.jul.mdx b/platform-includes/getting-started-install/java.jul.mdx index e91230044175e..a2cec0276dc41 100644 --- a/platform-includes/getting-started-install/java.jul.mdx +++ b/platform-includes/getting-started-install/java.jul.mdx @@ -35,6 +35,6 @@ For other dependency managers, see the [central Maven repository](https://search -If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.log4j2.mdx b/platform-includes/getting-started-install/java.log4j2.mdx index f9f83e6b1951e..fbb0dfc39c208 100644 --- a/platform-includes/getting-started-install/java.log4j2.mdx +++ b/platform-includes/getting-started-install/java.log4j2.mdx @@ -92,6 +92,6 @@ For other dependency managers see the [central Maven repository](https://search. We recommend using our Gradle plugin as it can add integrations and provide source context for events. -If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.logback.mdx b/platform-includes/getting-started-install/java.logback.mdx index 0b357eb92d40e..31705e9832079 100644 --- a/platform-includes/getting-started-install/java.logback.mdx +++ b/platform-includes/getting-started-install/java.logback.mdx @@ -92,6 +92,6 @@ For other dependency managers, see the [central Maven repository](https://search We recommend using our Gradle plugin as it can add integrations and provide source context for events. -If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.mdx b/platform-includes/getting-started-install/java.mdx index d91977f6a18b0..201b8149f6206 100644 --- a/platform-includes/getting-started-install/java.mdx +++ b/platform-includes/getting-started-install/java.mdx @@ -68,6 +68,6 @@ libraryDependencies += "io.sentry" % "sentry-async-profiler" % "{{@inject packag We recommend using our Gradle plugin as it can add integrations and provide source context for events. -If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.servlet.mdx b/platform-includes/getting-started-install/java.servlet.mdx index e214803352595..aa1a1bb4f3816 100644 --- a/platform-includes/getting-started-install/java.servlet.mdx +++ b/platform-includes/getting-started-install/java.servlet.mdx @@ -37,7 +37,7 @@ For other dependency managers, see the [central Maven repository](https://search -If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are using multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.spring-boot.mdx b/platform-includes/getting-started-install/java.spring-boot.mdx index 032db8803802c..929700cdb29d4 100644 --- a/platform-includes/getting-started-install/java.spring-boot.mdx +++ b/platform-includes/getting-started-install/java.spring-boot.mdx @@ -127,6 +127,6 @@ implementation 'io.sentry:sentry-async-profiler:{{@inject packages.version('sent We recommend using our Gradle plugin as it can add integrations and provide source context for events. -If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-install/java.spring.mdx b/platform-includes/getting-started-install/java.spring.mdx index f7f9184983c23..2260c460a971f 100644 --- a/platform-includes/getting-started-install/java.spring.mdx +++ b/platform-includes/getting-started-install/java.spring.mdx @@ -150,6 +150,6 @@ For other dependency managers see the [central Maven repository (Spring 5)](http We recommend using our Gradle plugin as it can add integrations and provide source context for events. -If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials) to avoid specifying the version of each dependency. +If you are manually adding multiple Sentry dependencies, you can add a [bill of materials](/platforms/java/configuration/bill-of-materials/) to avoid specifying the version of each dependency. diff --git a/platform-includes/getting-started-node/javascript.mdx b/platform-includes/getting-started-node/javascript.mdx index 3be10e71b7ee1..3ad8e223af0c4 100644 --- a/platform-includes/getting-started-node/javascript.mdx +++ b/platform-includes/getting-started-node/javascript.mdx @@ -58,7 +58,7 @@ Import `instrument.js` before any other modules to ensure Sentry initializes ear -The method for applying instrumentation depends on whether your application uses CommonJS (CJS) or ECMAScript Modules (ESM). If you're unsure which system you're using or if you're looking for alternative installation methods, see here. +The method for applying instrumentation depends on whether your application uses CommonJS (CJS) or ECMAScript Modules (ESM). If you're unsure which system you're using or if you're looking for alternative installation methods, see here. @@ -126,14 +126,14 @@ Our next recommended steps for you are: - Explore [practical guides](/guides/) on what to monitor, log, track, and investigate after setup - Extend Sentry to your frontend using one of our [frontend SDKs](/) -- Learn how to manually capture errors -- Continue to customize your configuration -- Get familiar with [Sentry's product features](/product) like tracing, insights, and alerts +- Learn how to manually capture errors +- Continue to customize your configuration +- Get familiar with [Sentry's product features](/product/) like tracing, insights, and alerts -- Check out alternative installation methods -- Find various topics in Troubleshooting +- Check out alternative installation methods +- Find various topics in Troubleshooting - [Get support](https://www.sentry.help/en/) diff --git a/platform-includes/getting-started-primer/java.spring.mdx b/platform-includes/getting-started-primer/java.spring.mdx index a30e3ef4084e1..b52f944837d1e 100644 --- a/platform-includes/getting-started-primer/java.spring.mdx +++ b/platform-includes/getting-started-primer/java.spring.mdx @@ -12,6 +12,6 @@ The minimum version of Spring Framework supported by the Sentry WebFlux integrat - Attaches HTTP request information to every `SentryEvent` recorded within the scope of the request - Provides the ability to [record user information](/platforms/java/guides/spring/advanced-usage/) -To use Sentry with Spring Boot, we recommend using Sentry [Spring Boot integration](/platforms/java/guides/spring-boot) as it provides richer configuration capabilities. +To use Sentry with Spring Boot, we recommend using Sentry [Spring Boot integration](/platforms/java/guides/spring-boot/) as it provides richer configuration capabilities. diff --git a/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx b/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx index 1838bfa20dc80..82904998333cd 100644 --- a/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx +++ b/platform-includes/getting-started-primer/kotlin.kotlin-multiplatform.mdx @@ -14,5 +14,5 @@ Xcode 16 support starts with Sentry Cocoa SDK version `8.36.0` or higher. Starting May 1, 2024, Apple requires all apps submitted to the App Store to provide a list of privacy-related APIs they use. Use Sentry Cocoa SDK version `8.25.0` or higher to ensure compliance with these requirements. -Follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest) guide to learn more. +Follow our [Apple Privacy Manifest](/platforms/kotlin/guides/kotlin-multiplatform/data-management/apple-privacy-manifest/) guide to learn more. diff --git a/platform-includes/getting-started-run/javascript.mdx b/platform-includes/getting-started-run/javascript.mdx index 3b891ce87d7a1..e9d233d0877c7 100644 --- a/platform-includes/getting-started-run/javascript.mdx +++ b/platform-includes/getting-started-run/javascript.mdx @@ -9,6 +9,6 @@ node --import ./instrument.mjs app.mjs -If you can't run node with `--require` or `--import`, import the Sentry Initialization file directly. +If you can't run node with `--require` or `--import`, import the Sentry Initialization file directly. diff --git a/platform-includes/getting-started-sourcemaps-short-version/javascript.mdx b/platform-includes/getting-started-sourcemaps-short-version/javascript.mdx index 528a817b14f05..81534a135a226 100644 --- a/platform-includes/getting-started-sourcemaps-short-version/javascript.mdx +++ b/platform-includes/getting-started-sourcemaps-short-version/javascript.mdx @@ -4,7 +4,7 @@ The stack traces in your Sentry errors probably won't look like your actual code without unminifying them. To fix this, upload your source maps to Sentry. The easiest way to do this is by using the Sentry Wizard. -Alternatively, take a look at our Uploading Source Maps documentation. +Alternatively, take a look at our Uploading Source Maps documentation. diff --git a/platform-includes/logs/setup/unity.mdx b/platform-includes/logs/setup/unity.mdx index 60ffd87dacf55..7b2dc0a85f608 100644 --- a/platform-includes/logs/setup/unity.mdx +++ b/platform-includes/logs/setup/unity.mdx @@ -7,7 +7,7 @@ To enable logging in your Unity game, you need to configure the Sentry SDK with ### Programmatic Configuration -Alternatively, you can enable logging programmatically through the [configure callback](/platforms/unity/configuration/options/programmatic-configuration): +Alternatively, you can enable logging programmatically through the [configure callback](/platforms/unity/configuration/options/programmatic-configuration/): ```csharp public override void Configure(SentryUnityOptions options) diff --git a/platform-includes/logs/usage/dart.mdx b/platform-includes/logs/usage/dart.mdx index 272d1d8a93d81..85d7295860f64 100644 --- a/platform-includes/logs/usage/dart.mdx +++ b/platform-includes/logs/usage/dart.mdx @@ -37,7 +37,7 @@ Sentry.logger.info('User ${user.username} added ${product.name} to cart.', attri ### Shared Attributes -Use `Sentry.setAttributes` to attach attributes that are automatically included on all logs, metrics, and spans (only in stream mode): +Use `Sentry.setAttributes` to attach attributes that are automatically included on all logs, metrics, and spans (only in stream mode): ```dart Sentry.setAttributes({ @@ -46,4 +46,4 @@ Sentry.setAttributes({ }); ``` -See Attributes for more information. +See Attributes for more information. diff --git a/platform-includes/logs/usage/python.mdx b/platform-includes/logs/usage/python.mdx index 0a0b21633b64e..9ebabbd178a21 100644 --- a/platform-includes/logs/usage/python.mdx +++ b/platform-includes/logs/usage/python.mdx @@ -39,7 +39,7 @@ Attribute values should be primitives — strings, numbers, or booleans. Sentry' ### Shared Attributes -Use `sentry_sdk.set_attribute` to attach attributes that are automatically included on all logs, metrics, and spans (only in stream mode). These write to the isolation scope, so they apply for the current request or session: +Use `sentry_sdk.set_attribute` to attach attributes that are automatically included on all logs, metrics, and spans (only in stream mode). These write to the isolation scope, so they apply for the current request or session: ```python import sentry_sdk @@ -48,4 +48,4 @@ sentry_sdk.set_attribute("org_id", user.org_id) sentry_sdk.set_attribute("user_tier", user.tier) ``` -To target a broader or narrower scope instead, see Attributes. +To target a broader or narrower scope instead, see Attributes. diff --git a/platform-includes/metrics/requirements/php.laravel.mdx b/platform-includes/metrics/requirements/php.laravel.mdx index d504771c6a737..f64e353cea2c7 100644 --- a/platform-includes/metrics/requirements/php.laravel.mdx +++ b/platform-includes/metrics/requirements/php.laravel.mdx @@ -1 +1 @@ -- [Laravel SDK](/platforms/php/guides/laravel) version `4.20.0` or above. +- [Laravel SDK](/platforms/php/guides/laravel/) version `4.20.0` or above. diff --git a/platform-includes/metrics/requirements/php.mdx b/platform-includes/metrics/requirements/php.mdx index ebfc1acfa958c..09d777f27a01d 100644 --- a/platform-includes/metrics/requirements/php.mdx +++ b/platform-includes/metrics/requirements/php.mdx @@ -1 +1 @@ -- [Sentry SDK](/platforms/php) version `4.19.0` or above. +- [Sentry SDK](/platforms/php/) version `4.19.0` or above. diff --git a/platform-includes/metrics/requirements/php.symfony.mdx b/platform-includes/metrics/requirements/php.symfony.mdx index 910da2322dc77..a0d8d07efa3dc 100644 --- a/platform-includes/metrics/requirements/php.symfony.mdx +++ b/platform-includes/metrics/requirements/php.symfony.mdx @@ -1 +1 @@ -- [Symfony SDK](/platforms/php/guides/symfony) version `5.8.0` or above. +- [Symfony SDK](/platforms/php/guides/symfony/) version `5.8.0` or above. diff --git a/platform-includes/metrics/setup/unity.mdx b/platform-includes/metrics/setup/unity.mdx index f7daa90cee79e..8f59c0c0efcd0 100644 --- a/platform-includes/metrics/setup/unity.mdx +++ b/platform-includes/metrics/setup/unity.mdx @@ -7,7 +7,7 @@ To enable metrics in your Unity game, you need to configure the Sentry SDK with ### Programmatic Configuration -Alternatively, you can enable metrics programmatically through the [configure callback](/platforms/unity/configuration/options/programmatic-configuration): +Alternatively, you can enable metrics programmatically through the [configure callback](/platforms/unity/configuration/options/programmatic-configuration/): ```csharp public override void Configure(SentryUnityOptions options) diff --git a/platform-includes/metrics/usage/dart.flutter.mdx b/platform-includes/metrics/usage/dart.flutter.mdx index dfeeec373b67a..6d0e1233a3582 100644 --- a/platform-includes/metrics/usage/dart.flutter.mdx +++ b/platform-includes/metrics/usage/dart.flutter.mdx @@ -75,9 +75,9 @@ Sentry.metrics.count( #### Scope Attributes -Use scope APIs to set attributes that apply to all logs, metrics, and spans (only in stream mode) while the scope is active. +Use scope APIs to set attributes that apply to all logs, metrics, and spans (only in stream mode) while the scope is active. -See Attributes for more information. +See Attributes for more information. diff --git a/platform-includes/metrics/usage/dart.mdx b/platform-includes/metrics/usage/dart.mdx index 4a09814c1d533..226d17748f1fd 100644 --- a/platform-includes/metrics/usage/dart.mdx +++ b/platform-includes/metrics/usage/dart.mdx @@ -75,9 +75,9 @@ Sentry.metrics.count( #### Scope Attributes -Use scope APIs to set attributes that apply to all logs, metrics, and spans (only in stream mode) while the scope is active. +Use scope APIs to set attributes that apply to all logs, metrics, and spans (only in stream mode) while the scope is active. -See Attributes for more information. +See Attributes for more information. diff --git a/platform-includes/metrics/usage/python.mdx b/platform-includes/metrics/usage/python.mdx index ca8ab34869d8b..eac0f8e702d69 100644 --- a/platform-includes/metrics/usage/python.mdx +++ b/platform-includes/metrics/usage/python.mdx @@ -70,11 +70,11 @@ Attributes let you filter and group metrics in Sentry. Use them for: - Feature flag tracking - User tier analysis -You've already seen attributes passed directly to individual metric calls in the examples above. See Attributes for more information on how attributes work across spans, logs, and metrics. +You've already seen attributes passed directly to individual metric calls in the examples above. See Attributes for more information on how attributes work across spans, logs, and metrics. ### Shared Attributes -Use `sentry_sdk.set_attribute` to attach attributes that apply to all logs, metrics, and spans (only in stream mode). These write to the isolation scope, so they apply for the current request or session: +Use `sentry_sdk.set_attribute` to attach attributes that apply to all logs, metrics, and spans (only in stream mode). These write to the isolation scope, so they apply for the current request or session: ```python import sentry_sdk @@ -83,4 +83,4 @@ sentry_sdk.set_attribute("is_admin", True) sentry_sdk.set_attribute("auth_provider", "google") ``` -To target a broader or narrower scope instead, see Attributes. +To target a broader or narrower scope instead, see Attributes. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.connect.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.connect.mdx index 13c630acb863d..75b79cb65edb8 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.connect.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.connect.mdx @@ -92,8 +92,8 @@ We now support the following integrations out of the box with 0 configuration: -If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. -If you are unsure how you are running your application, see Installation Methods for more information. +If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. +If you are unsure how you are running your application, see Installation Methods for more information. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.express.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.express.mdx index f946d39c8ee3c..3be5f7ed99456 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.express.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.express.mdx @@ -116,8 +116,8 @@ We now support the following integrations out of the box with 0 configuration: -If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. -If you are unsure how you are running your application, see Installation Methods for more information. +If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. +If you are unsure how you are running your application, see Installation Methods for more information. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.fastify.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.fastify.mdx index 07f502ba815a8..5220e2ff63006 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.fastify.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.fastify.mdx @@ -92,8 +92,8 @@ We now support the following integrations out of the box with 0 configuration: -If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. -If you are unsure how you are running your application, see Installation Methods for more information. +If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. +If you are unsure how you are running your application, see Installation Methods for more information. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.koa.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.koa.mdx index 673a6689c703f..c0aa61eb7df07 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.koa.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.koa.mdx @@ -92,8 +92,8 @@ We now support the following integrations out of the box with 0 configuration: -If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. -If you are unsure how you are running your application, see Installation Methods for more information. +If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. +If you are unsure how you are running your application, see Installation Methods for more information. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.node.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.node.mdx index 371d28ec3e698..6c712174cd6f7 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.node.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.node.mdx @@ -92,8 +92,8 @@ import http from "http"; -If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. -If you are unsure how you are running your application, see Installation Methods for more information. +If you run your application with ESM, you need to import the Sentry Initialization file before importing any other modules. See running Sentry with ESM. +If you are unsure how you are running your application, see Installation Methods for more information. diff --git a/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx b/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx index 75606774e36f2..97cf211d9493c 100644 --- a/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx +++ b/platform-includes/migration/javascript-v8/important-changes/javascript.remix.mdx @@ -31,7 +31,7 @@ export const handleError = Sentry.wrapRemixHandleError; Since [8.10.0](https://github.com/getsentry/sentry-javascript/releases/tag/8.10.0), you can also setup `@sentry/remix` with a new `autoInstrumentRemix: true` - option. See Manual Setup for + option. See Manual Setup for details on how to use this option. diff --git a/platform-includes/performance/custom-performance-metrics/dart.mdx b/platform-includes/performance/custom-performance-metrics/dart.mdx index ae6962bb0385f..84a977bf2b1d4 100644 --- a/platform-includes/performance/custom-performance-metrics/dart.mdx +++ b/platform-includes/performance/custom-performance-metrics/dart.mdx @@ -1,7 +1,7 @@ Adding custom measurements is supported in Sentry's Dart/Flutter SDK version `6.11.0` and above. - Transaction mode (default): Use `setMeasurement` on the active span. -- Stream mode: There's +- Stream mode: There's no dedicated measurement API (and no public way to fetch the active span), so record the values as attributes on a span you create. diff --git a/platform-includes/profiling/automatic-instrumentation-setup/java.spring-boot.mdx b/platform-includes/profiling/automatic-instrumentation-setup/java.spring-boot.mdx index 75175d1496867..8875dcefe54a9 100644 --- a/platform-includes/profiling/automatic-instrumentation-setup/java.spring-boot.mdx +++ b/platform-includes/profiling/automatic-instrumentation-setup/java.spring-boot.mdx @@ -61,6 +61,6 @@ Sentry.stopProfiler() ``` -If you are using our OpenTelemetry Agent, profiling when running in the Agent Auto-Init mode is supported from version `8.26.0` onwards. +If you are using our OpenTelemetry Agent, profiling when running in the Agent Auto-Init mode is supported from version `8.26.0` onwards. diff --git a/platform-includes/profiling/automatic-instrumentation-setup/java.spring.mdx b/platform-includes/profiling/automatic-instrumentation-setup/java.spring.mdx index 0ffd43e89884d..216961e427037 100644 --- a/platform-includes/profiling/automatic-instrumentation-setup/java.spring.mdx +++ b/platform-includes/profiling/automatic-instrumentation-setup/java.spring.mdx @@ -61,10 +61,10 @@ Sentry.stopProfiler() ``` ### Profiling with OpenTelemetry -When running our OpenTelemetry Agent in Agent Auto-Init mode. The `SentryProfilerConfiguration` needs to be setup. This is due to the fact that the profiler is not yet on the classpath when the agent initializes `Sentry`. Therefore the profiler needs to be initialized when `Spring` starts. +When running our OpenTelemetry Agent in Agent Auto-Init mode. The `SentryProfilerConfiguration` needs to be setup. This is due to the fact that the profiler is not yet on the classpath when the agent initializes `Sentry`. Therefore the profiler needs to be initialized when `Spring` starts. -If you are using our OpenTelemetry Agent, profiling when running in the Agent Auto-Init mode is supported from version `8.26.0` onwards. +If you are using our OpenTelemetry Agent, profiling when running in the Agent Auto-Init mode is supported from version `8.26.0` onwards. In order to set this up, import `SentryProfilerConfiguration` in one of your `@Configuration` classes: diff --git a/platform-includes/set-release/react-native.mdx b/platform-includes/set-release/react-native.mdx index b982f36248546..33bf781c61d2c 100644 --- a/platform-includes/set-release/react-native.mdx +++ b/platform-includes/set-release/react-native.mdx @@ -9,6 +9,6 @@ Sentry.init({ -When you set a custom `release` and `dist` in a React Native app, the automatic source maps upload script will no longer work because it does not detect custom values. You will need to [manually upload source maps](/platforms/react-native/sourcemaps). +When you set a custom `release` and `dist` in a React Native app, the automatic source maps upload script will no longer work because it does not detect custom values. You will need to [manually upload source maps](/platforms/react-native/sourcemaps/). diff --git a/platform-includes/source-context/apple.mdx b/platform-includes/source-context/apple.mdx index bd5b392c53c1c..7d3dfe446c4a0 100644 --- a/platform-includes/source-context/apple.mdx +++ b/platform-includes/source-context/apple.mdx @@ -34,7 +34,7 @@ sentry_debug_files_upload( -The Sentry Fastlane plugin version 2.0.0 includes breaking changes due to the sentry-cli 3.0.0 upgrade. If you're upgrading from version 1.x, see the [migration guide](/platforms/apple/dsym#migration-guide) for details. +The Sentry Fastlane plugin version 2.0.0 includes breaking changes due to the sentry-cli 3.0.0 upgrade. If you're upgrading from version 1.x, see the [migration guide](/platforms/apple/dsym/#migration-guide) for details. diff --git a/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx b/platform-includes/sourcemaps/legacy-troubleshooting/javascript.mdx index cb6da7d5b4f7f..259b7933e760e 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..72565ba9cf6e9 100644 --- a/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx +++ b/platform-includes/sourcemaps/legacy-uploading-methods/javascript.mdx @@ -11,7 +11,7 @@ Use the guide on this page if you're using one of the following: - `sentry-cli` version `2.16.1` or lower - Sentry self-hosted or single-tenant on version `23.6.1` or lower -If all of your Sentry dependencies are on more up-to-date versions than in the list above, we recommend using the regular Source Maps guide. +If all of your Sentry dependencies are on more up-to-date versions than in the list above, we recommend using the regular Source Maps guide. If you're using one or more of these older versions of the tools, you can still upload source maps; however, the process will be different. Instead of using debug IDs, you'll use [Releases](/product/releases/) to match an event's stack frame with its corresponding minified source and source map file (known as artifacts). @@ -328,7 +328,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/troubleshooting/javascript.mdx b/platform-includes/sourcemaps/troubleshooting/javascript.mdx index 87b0d74454d03..ddca9e1613828 100644 --- a/platform-includes/sourcemaps/troubleshooting/javascript.mdx +++ b/platform-includes/sourcemaps/troubleshooting/javascript.mdx @@ -3,7 +3,7 @@ If you previously set up source maps, we suggest updating your tools (SDK, bundler plugins, Sentry CLI). It is generally easier to upgrade to the latest versions and follow the current process rather than troubleshooting with older versions. -For information on the legacy method of uploading source maps, please see the guide on Legacy Uploading Methods. +For information on the legacy method of uploading source maps, please see the guide on Legacy Uploading Methods. Dependency versions that require the legacy method of uploading source maps include: diff --git a/platform-includes/sourcemaps/upload/primer/javascript.sveltekit.mdx b/platform-includes/sourcemaps/upload/primer/javascript.sveltekit.mdx index 47372f4bfdbed..cbe9819a13952 100644 --- a/platform-includes/sourcemaps/upload/primer/javascript.sveltekit.mdx +++ b/platform-includes/sourcemaps/upload/primer/javascript.sveltekit.mdx @@ -56,7 +56,7 @@ SENTRY_AUTH_TOKEN=___ORG_AUTH_TOKEN___ ### Override SvelteKit Adapter Detection -By default, `sentrySvelteKit` will try to detect your SvelteKit adapter to configure the source maps upload correctly. If you're not using one of the [supported adapters](/platforms/javascript/guides/sveltekit) or the wrong one is detected, you can override the adapter detection by passing the `adapter` option to `sentrySvelteKit`: +By default, `sentrySvelteKit` will try to detect your SvelteKit adapter to configure the source maps upload correctly. If you're not using one of the [supported adapters](/platforms/javascript/guides/sveltekit/) or the wrong one is detected, you can override the adapter detection by passing the `adapter` option to `sentrySvelteKit`: ```javascript {filename:vite.config.(js|ts)} {7} import { sveltekit } from "@sveltejs/kit/vite"; diff --git a/scripts/generate-md-exports.mjs b/scripts/generate-md-exports.mjs index e403ef90c082e..22cc86d349b3f 100644 --- a/scripts/generate-md-exports.mjs +++ b/scripts/generate-md-exports.mjs @@ -21,6 +21,7 @@ import { import pLimit from 'p-limit'; import rehypeParse from 'rehype-parse'; import rehypeRemark from 'rehype-remark'; +import rehypeStringify from 'rehype-stringify'; import remarkGfm from 'remark-gfm'; import RemarkLinkRewrite from 'remark-link-rewrite'; import remarkStringify from 'remark-stringify'; @@ -577,7 +578,7 @@ async function renderMdxOverrides(root, docTree) { const relativePath = file.replace(/\.mdx$/, '.md'); const urlPath = file.replace(/\.mdx$/, '').replace(/^index$/, ''); - const canonicalUrl = `${DOCS_ORIGIN}/${urlPath}`; + const canonicalUrl = urlPath ? `${DOCS_ORIGIN}/${urlPath}/` : `${DOCS_ORIGIN}/`; const html = [ '', @@ -947,17 +948,18 @@ async function createWork() { const md5 = data => createHash('md5').update(data).digest('hex'); /** - * Strips build-specific HTML elements that are irrelevant for markdown generation. + * Strips build-specific HTML elements from Next.js output using a proper + * HTML parser (rehype-parse) instead of regular expressions. * - * Next.js build output contains elements that change between builds: + * Removes: * -