From 46852ac41c76287082dbf19a779f89eb9dfd26ad Mon Sep 17 00:00:00 2001 From: Shannon Anahata Date: Wed, 20 May 2026 10:29:29 -0700 Subject: [PATCH 1/2] feat: flatten Explore section into Product sidebar with section headers Move 6 child directories out of product/explore/ up to product/: - trace-explorer (Traces and Spans) - logs (Logs) - session-replay (Session Replay) - profiling (Profiling) - metrics (Application Metrics) - discover-queries (Discover) Add sidebar_section support for Product pages with 5 new section headers: Debug, Investigate, Observe, AI in Sentry, Advanced. Update all ~200 internal links from /product/explore/* to /product/*. Add redirects from old /product/explore/* paths to new locations. Update redirect destinations in redirects.js and middleware.ts. Section assignments: - Debug: Issues, Monitors and Alerts - Investigate: Traces and Spans, Logs, Session Replay, Profiling - Observe: Dashboards, Metrics, Releases, Stats, Size Analysis - AI in Sentry: AI in Sentry - Advanced: Discover, User Feedback, Drains, Projects, Relay, Toolbar, Notifications, Partnership Platform, Build Distribution, Snapshots, Codecov --- docs/ai/index.mdx | 4 +- docs/ai/monitoring/agents/sampling.mdx | 4 +- .../data-management/filtering/index.mdx | 6 +- docs/concepts/key-terms/enrich-data/index.mdx | 2 +- docs/concepts/key-terms/key-terms.mdx | 2 +- docs/concepts/key-terms/sample-rates.mdx | 2 +- .../key-terms/tracing/distributed-tracing.mdx | 6 +- docs/concepts/key-terms/tracing/index.mdx | 4 +- .../key-terms/tracing/span-metrics.mdx | 2 +- .../forwarding/sources/aws-cloudwatch.mdx | 2 +- .../otlp/forwarding/sources/kafka.mdx | 2 +- .../otlp/forwarding/sources/nginx.mdx | 2 +- .../otlp/forwarding/sources/syslog.mdx | 2 +- .../forwarding/sources/windows-events.mdx | 2 +- docs/concepts/search/index.mdx | 2 +- .../searchable-properties/session-replay.mdx | 10 +-- .../search/searchable-properties/spans.mdx | 2 +- docs/guides/custom-spans.mdx | 4 +- docs/guides/issues-errors.mdx | 2 +- docs/guides/logs.mdx | 4 +- docs/guides/metrics.mdx | 4 +- docs/guides/querying-traces.mdx | 4 +- docs/guides/session-replay.mdx | 4 +- .../feature-flag/generic/index.mdx | 2 +- docs/integrations/session-replay/index.mdx | 2 +- docs/platforms/android/index.mdx | 2 +- docs/platforms/android/metrics/index.mdx | 2 +- docs/platforms/android/overhead/index.mdx | 4 +- .../android/session-replay/index.mdx | 4 +- .../session-replay/performance-overhead.mdx | 2 +- .../session-replay/troubleshooting.mdx | 2 +- .../platforms/apple/common/overhead/index.mdx | 4 +- .../apple/common/session-replay/index.mdx | 4 +- .../session-replay/performance-overhead.mdx | 2 +- .../common/session-replay/troubleshooting.mdx | 2 +- .../automatic-instrumentation.mdx | 2 +- docs/platforms/dart/common/metrics/index.mdx | 2 +- docs/platforms/dart/guides/flutter/index.mdx | 2 +- .../dart/guides/flutter/overhead/index.mdx | 2 +- .../guides/flutter/session-replay/index.mdx | 4 +- .../session-replay/performance-overhead.mdx | 2 +- .../dotnet/common/profiling/index.mdx | 2 +- docs/platforms/dotnet/index.mdx | 2 +- docs/platforms/go/common/metrics/index.mdx | 2 +- .../java/guides/jul/usage/advanced-usage.mdx | 2 +- .../java/guides/log4j2/advanced_usage.mdx | 2 +- .../guides/logback/usage/advanced-usage.mdx | 2 +- .../integrations/browserprofiling.mdx | 2 +- .../integrations/elementtiming.mdx | 2 +- .../integrations/nodeprofiling.mdx | 2 +- .../configuration/integrations/replay.mdx | 2 +- docs/platforms/javascript/common/index.mdx | 4 +- .../javascript/common/logs/index.mdx | 4 +- .../javascript/common/metrics/index.mdx | 2 +- .../javascript/common/migration/v9-to-v10.mdx | 2 +- .../common/session-replay/index.mdx | 4 +- .../common/session-replay/troubleshooting.mdx | 2 +- .../javascript/common/tracing/index.mdx | 2 +- .../javascript/guides/angular/angular1.mdx | 2 +- .../aws-lambda/install/cjs-npm__v9.x.mdx | 2 +- .../aws-lambda/install/esm-npm__v9.x.mdx | 2 +- .../guides/aws-lambda/install/npm.mdx | 2 +- .../javascript/guides/react-router/index.mdx | 2 +- .../guides/remix/manual-setup__v8.x.mdx | 2 +- docs/platforms/native/metrics/index.mdx | 2 +- docs/platforms/php/common/profiling/index.mdx | 2 +- .../php/guides/laravel/profiling/index.mdx | 2 +- .../php/guides/symfony/profiling/index.mdx | 2 +- .../python/integrations/asgi/index.mdx | 2 +- .../manual-instrumentation/index.mdx | 2 +- .../python/integrations/beam/index.mdx | 2 +- .../python/integrations/celery/crons.mdx | 2 +- .../python/integrations/celery/index.mdx | 2 +- .../cloudresourcecontext/index.mdx | 2 +- .../integrations/gcp-functions/index.mdx | 2 +- .../python/integrations/grpc/index.mdx | 2 +- .../python/integrations/litestar/index.mdx | 2 +- .../python/integrations/ray/index.mdx | 2 +- .../python/integrations/rq/index.mdx | 2 +- .../python/integrations/sanic/index.mdx | 2 +- .../python/integrations/serverless/index.mdx | 2 +- .../python/integrations/socket/index.mdx | 2 +- .../python/integrations/spark/index.mdx | 2 +- .../python/integrations/strawberry/index.mdx | 2 +- .../python/integrations/tryton/index.mdx | 2 +- .../python/integrations/wsgi/index.mdx | 2 +- docs/platforms/python/profiling/index.mdx | 2 +- docs/platforms/react-native/index.mdx | 2 +- docs/platforms/react-native/metrics/index.mdx | 2 +- .../platforms/react-native/overhead/index.mdx | 4 +- .../profiling/troubleshooting/index.mdx | 2 +- .../react-native/session-replay/index.mdx | 4 +- .../session-replay/performance-overhead.mdx | 2 +- docs/platforms/ruby/common/index.mdx | 2 +- docs/platforms/rust/common/metrics/index.mdx | 2 +- docs/platforms/rust/guides/tracing/index.mdx | 2 +- docs/platforms/unity/metrics/index.mdx | 2 +- docs/platforms/unreal/metrics/index.mdx | 2 +- docs/pricing/index.mdx | 2 +- .../manage-application-metrics-quota.mdx | 4 +- .../manage-continuous-profile-hours.mdx | 2 +- docs/pricing/quotas/manage-logs-quota.mdx | 2 +- .../quotas/manage-ui-profile-hours.mdx | 2 +- docs/product/ai-in-sentry/index.mdx | 5 +- .../ai-in-sentry/seer/autofix/index.mdx | 2 +- docs/product/ai-in-sentry/seer/index.mdx | 2 +- docs/product/build-distribution/index.mdx | 3 +- docs/product/dashboards/index.mdx | 5 +- .../frontend/web-vitals/index.mdx | 2 +- .../web-vitals/web-vitals-concepts.mdx | 2 +- .../dashboards/sentry-dashboards/index.mdx | 2 +- .../mobile/mobile-vitals/screen-loads.mdx | 2 +- .../sentry-dashboards/transaction-summary.mdx | 4 +- .../dashboards/widget-builder/index.mdx | 16 ++-- .../discover-queries/img/001.png | Bin .../discover-queries/img/002.png | Bin .../discover-queries/img/003.png | Bin .../discover-queries/img/004.png | Bin .../discover-queries/img/005.png | Bin .../discover-queries/img/006.png | Bin .../discover-queries/img/007.png | Bin .../discover-queries/img/008.png | Bin .../discover-queries/img/009.png | Bin .../discover-queries/img/010.png | Bin .../discover-queries/img/012.png | Bin .../discover-queries/img/013.png | Bin .../discover-queries/img/014.png | Bin .../img/discover-event-details.png | Bin .../img/discover-facet-map.png | Bin .../img/discover-homepage.png | Bin .../discover-queries/img/discover-results.png | Bin .../img/discover-table-cell.png | Bin .../img/trace-details-view.png | Bin .../{explore => }/discover-queries/index.mdx | 7 +- .../discover-queries/query-builder.mdx | 2 +- .../query-builder/img/add_equation.gif | Bin .../query-builder/query-equations.mdx | 0 .../discover-queries/standard-fields.json | 0 .../discover-queries/uncover-trends.mdx | 0 docs/product/drains/index.mdx | 9 ++- docs/product/drains/openrouter.mdx | 2 +- docs/product/drains/vercel.mdx | 2 +- docs/product/explore/index.mdx | 11 --- docs/product/index.mdx | 8 +- docs/product/issues/index.mdx | 3 +- .../issue-details/breadcrumbs/index.mdx | 2 +- docs/product/issues/issue-details/index.mdx | 8 +- .../performance-issues/frame-drop/index.mdx | 2 +- .../function-regressions.mdx | 2 +- .../image-decoding-main-thread/index.mdx | 2 +- .../json-decoding-main-thread/index.mdx | 2 +- .../regex-main-thread/index.mdx | 2 +- .../issue-details/replay-issues/index.mdx | 2 +- .../replay-issues/rage-clicks.mdx | 4 +- .../logs/getting-started/index.mdx | 0 .../{explore => }/logs/img/AutoRefresh.png | Bin .../logs/img/ContinueScanning.png | Bin .../logs/img/ExtrapolatedLogs.png | Bin .../{explore => }/logs/img/LogQueries.png | Bin .../logs/img/LogSearchRawText.png | Bin .../{explore => }/logs/img/LogSearchTags.png | Bin .../{explore => }/logs/img/LogsExpanded.png | Bin .../{explore => }/logs/img/StructuredLogs.png | Bin docs/product/{explore => }/logs/index.mdx | 7 +- .../metrics/getting-started/index.mdx | 0 .../{explore => }/metrics/img/aggregates.png | Bin .../metrics/img/metric-equation-example.png | Bin .../{explore => }/metrics/img/samples.png | Bin docs/product/{explore => }/metrics/index.mdx | 13 +-- docs/product/monitors-and-alerts/index.mdx | 3 +- .../monitors-and-alerts/monitors/index.mdx | 4 +- .../uptime-monitoring/uptime-tracing.mdx | 2 +- docs/product/notifications/index.mdx | 3 +- docs/product/onboarding/index.mdx | 2 +- docs/product/partnership-platform/index.mdx | 3 +- ...ontinuous-ui-profiling-migration-guide.mdx | 2 +- .../profiling/differential-flamegraphs.mdx | 0 .../profiling/flame-charts-graphs.mdx | 0 .../profiling/getting-started.mdx | 4 +- .../img/aggregated-flame-graph-view.png | Bin .../img/differential-flamegraph-inverted.png | Bin .../img/differential-flamegraph-new.png | Bin .../img/differential-flamegraph-regular.png | Bin .../img/differential-flamegraph-table.png | Bin .../profiling/img/differential-flamegraph.png | Bin .../profiling/img/fib-flame-chart.png | Bin .../profiling/img/fib-flame-graph.png | Bin .../profiling/img/flame-chart-hair.png | Bin .../profiling/img/flame-chart-less-hair.png | Bin .../profiling/img/flame-chart.png | Bin .../{explore => }/profiling/img/minimap.png | Bin .../profiling/img/profile-details-trace.png | Bin .../profiling/img/profile-flame-chart.png | Bin .../profiling-page-aggregate-flamegraph.png | Bin .../img/profiling-page-functions.png | Bin .../img/profiling-page-transactions.png | Bin .../profiling/img/search-bar.png | Bin .../profiling/img/thread-selector.png | Bin .../profiling/img/trace-environment-view.png | Bin .../profiling/img/trace-view-profiles.png | Bin .../profiling/img/trace-view-span-profile.png | Bin .../profiling/img/trace-view.png | Bin .../img/transaction-summary-profiles.png | Bin .../{explore => }/profiling/img/tree-view.gif | Bin .../product/{explore => }/profiling/index.mdx | 11 +-- .../img/flamechart-with-gpu-overlay.png | Bin .../profiling/mobile-app-profiling/index.mdx | 0 .../mobile-app-profiling/metrics.mdx | 0 .../profiling/performance-overhead.mdx | 0 .../profiling/profile-details.mdx | 4 +- .../transaction-vs-continuous-profiling.mdx | 10 +-- docs/product/projects/index.mdx | 2 +- docs/product/relay/index.mdx | 3 +- docs/product/releases/health/index.mdx | 2 +- docs/product/releases/index.mdx | 3 +- docs/product/sentry-basics/index.mdx | 4 +- .../integrate-frontend/configure-scms.mdx | 4 +- .../sentry-basics/performance-monitoring.mdx | 4 +- docs/product/sentry-toolbar/index.mdx | 5 +- .../session-replay/access-control.mdx | 0 .../img/replay-details-share.png | Bin .../img/replay-details-tags.png | Bin .../session-replay/img/replay-details.png | Bin .../img/replay-index-delete-all.png | Bin .../img/replay-index-delete-visible.png | Bin .../img/replay-index-filtering.png | Bin .../{explore => }/session-replay/index.mdx | 3 +- .../mobile/img/session-replay-redacted.png | Bin .../mobile/img/session-replay.png | Bin .../session-replay/mobile/index.mdx | 2 +- .../mobile/performance-overhead.mdx | 2 +- .../session-replay/replay-details.mdx | 0 .../replay-page-and-filters.mdx | 6 +- .../img/session-replay-what-is-a-replay.png | Bin .../session-replay/web/img/session-replay.png | Bin .../session-replay/web/index.mdx | 2 +- .../web/performance-overhead.mdx | 2 +- docs/product/size-analysis/index.mdx | 3 +- docs/product/snapshots/index.mdx | 3 +- docs/product/stats/index.mdx | 3 +- .../img/Trace_Explorer_home.png | Bin .../img/Trace_explorer_alerts.png | Bin .../img/Trace_explorer_low_samples.png | Bin .../img/Trace_explorer_low_samples_old.png | Bin .../img/Trace_explorer_search.png | Bin .../img/attribute_comparison.png | Bin .../trace-explorer/img/trace-explorer01.png | Bin .../trace-explorer/img/trace-explorer02.png | Bin .../trace-explorer/img/trace-explorer03.png | Bin .../trace-explorer/img/trace-explorer04.png | Bin .../trace-explorer/img/trace-explorer05.png | Bin .../trace-explorer/img/trace-explorer06.png | Bin .../trace-explorer/img/trace-explorer07.png | Bin .../img/trace_explorer_save.png | Bin .../{explore => }/trace-explorer/index.mdx | 7 +- docs/product/user-feedback/index.mdx | 7 +- .../scrubbing/advanced-datascrubbing.mdx | 4 +- includes/apple-platform-getting-started.mdx | 2 +- includes/docs-changelog.mdx | 4 +- middleware.ts | 76 +++++++----------- platform-includes/metrics/options/godot.mdx | 2 +- platform-includes/metrics/options/unreal.mdx | 2 +- platform-includes/metrics/usage/rust.mdx | 8 +- .../_default.mdx | 2 +- .../browser-profiling/javascript.mdx | 2 +- .../index/why-profiling/_default.mdx | 2 +- .../index/why-profiling/javascript.mdx | 2 +- redirects.js | 47 ++++++----- src/components/featureInfo.tsx | 14 ++-- src/components/home.tsx | 2 +- src/components/sidebar/dynamicNav.tsx | 24 +++++- src/components/sidebar/types.ts | 9 ++- src/types/frontmatter.ts | 17 ++-- 273 files changed, 384 insertions(+), 345 deletions(-) rename docs/product/{explore => }/discover-queries/img/001.png (100%) rename docs/product/{explore => }/discover-queries/img/002.png (100%) rename docs/product/{explore => }/discover-queries/img/003.png (100%) rename docs/product/{explore => }/discover-queries/img/004.png (100%) rename docs/product/{explore => }/discover-queries/img/005.png (100%) rename docs/product/{explore => }/discover-queries/img/006.png (100%) rename docs/product/{explore => }/discover-queries/img/007.png (100%) rename docs/product/{explore => }/discover-queries/img/008.png (100%) rename docs/product/{explore => }/discover-queries/img/009.png (100%) rename docs/product/{explore => }/discover-queries/img/010.png (100%) rename docs/product/{explore => }/discover-queries/img/012.png (100%) rename docs/product/{explore => }/discover-queries/img/013.png (100%) rename docs/product/{explore => }/discover-queries/img/014.png (100%) rename docs/product/{explore => }/discover-queries/img/discover-event-details.png (100%) rename docs/product/{explore => }/discover-queries/img/discover-facet-map.png (100%) rename docs/product/{explore => }/discover-queries/img/discover-homepage.png (100%) rename docs/product/{explore => }/discover-queries/img/discover-results.png (100%) rename docs/product/{explore => }/discover-queries/img/discover-table-cell.png (100%) rename docs/product/{explore => }/discover-queries/img/trace-details-view.png (100%) rename docs/product/{explore => }/discover-queries/index.mdx (98%) rename docs/product/{explore => }/discover-queries/query-builder.mdx (99%) rename docs/product/{explore => }/discover-queries/query-builder/img/add_equation.gif (100%) rename docs/product/{explore => }/discover-queries/query-builder/query-equations.mdx (100%) rename docs/product/{explore => }/discover-queries/standard-fields.json (100%) rename docs/product/{explore => }/discover-queries/uncover-trends.mdx (100%) delete mode 100644 docs/product/explore/index.mdx rename docs/product/{explore => }/logs/getting-started/index.mdx (100%) rename docs/product/{explore => }/logs/img/AutoRefresh.png (100%) rename docs/product/{explore => }/logs/img/ContinueScanning.png (100%) rename docs/product/{explore => }/logs/img/ExtrapolatedLogs.png (100%) rename docs/product/{explore => }/logs/img/LogQueries.png (100%) rename docs/product/{explore => }/logs/img/LogSearchRawText.png (100%) rename docs/product/{explore => }/logs/img/LogSearchTags.png (100%) rename docs/product/{explore => }/logs/img/LogsExpanded.png (100%) rename docs/product/{explore => }/logs/img/StructuredLogs.png (100%) rename docs/product/{explore => }/logs/index.mdx (97%) rename docs/product/{explore => }/metrics/getting-started/index.mdx (100%) rename docs/product/{explore => }/metrics/img/aggregates.png (100%) rename docs/product/{explore => }/metrics/img/metric-equation-example.png (100%) rename docs/product/{explore => }/metrics/img/samples.png (100%) rename docs/product/{explore => }/metrics/index.mdx (94%) rename docs/product/{explore => }/profiling/continuous-ui-profiling-migration-guide.mdx (98%) rename docs/product/{explore => }/profiling/differential-flamegraphs.mdx (100%) rename docs/product/{explore => }/profiling/flame-charts-graphs.mdx (100%) rename docs/product/{explore => }/profiling/getting-started.mdx (95%) rename docs/product/{explore => }/profiling/img/aggregated-flame-graph-view.png (100%) rename docs/product/{explore => }/profiling/img/differential-flamegraph-inverted.png (100%) rename docs/product/{explore => }/profiling/img/differential-flamegraph-new.png (100%) rename docs/product/{explore => }/profiling/img/differential-flamegraph-regular.png (100%) rename docs/product/{explore => }/profiling/img/differential-flamegraph-table.png (100%) rename docs/product/{explore => }/profiling/img/differential-flamegraph.png (100%) rename docs/product/{explore => }/profiling/img/fib-flame-chart.png (100%) rename docs/product/{explore => }/profiling/img/fib-flame-graph.png (100%) rename docs/product/{explore => }/profiling/img/flame-chart-hair.png (100%) rename docs/product/{explore => }/profiling/img/flame-chart-less-hair.png (100%) rename docs/product/{explore => }/profiling/img/flame-chart.png (100%) rename docs/product/{explore => }/profiling/img/minimap.png (100%) rename docs/product/{explore => }/profiling/img/profile-details-trace.png (100%) rename docs/product/{explore => }/profiling/img/profile-flame-chart.png (100%) rename docs/product/{explore => }/profiling/img/profiling-page-aggregate-flamegraph.png (100%) rename docs/product/{explore => }/profiling/img/profiling-page-functions.png (100%) rename docs/product/{explore => }/profiling/img/profiling-page-transactions.png (100%) rename docs/product/{explore => }/profiling/img/search-bar.png (100%) rename docs/product/{explore => }/profiling/img/thread-selector.png (100%) rename docs/product/{explore => }/profiling/img/trace-environment-view.png (100%) rename docs/product/{explore => }/profiling/img/trace-view-profiles.png (100%) rename docs/product/{explore => }/profiling/img/trace-view-span-profile.png (100%) rename docs/product/{explore => }/profiling/img/trace-view.png (100%) rename docs/product/{explore => }/profiling/img/transaction-summary-profiles.png (100%) rename docs/product/{explore => }/profiling/img/tree-view.gif (100%) rename docs/product/{explore => }/profiling/index.mdx (89%) rename docs/product/{explore => }/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png (100%) rename docs/product/{explore => }/profiling/mobile-app-profiling/index.mdx (100%) rename docs/product/{explore => }/profiling/mobile-app-profiling/metrics.mdx (100%) rename docs/product/{explore => }/profiling/performance-overhead.mdx (100%) rename docs/product/{explore => }/profiling/profile-details.mdx (97%) rename docs/product/{explore => }/profiling/transaction-vs-continuous-profiling.mdx (91%) rename docs/product/{explore => }/session-replay/access-control.mdx (100%) rename docs/product/{explore => }/session-replay/img/replay-details-share.png (100%) rename docs/product/{explore => }/session-replay/img/replay-details-tags.png (100%) rename docs/product/{explore => }/session-replay/img/replay-details.png (100%) rename docs/product/{explore => }/session-replay/img/replay-index-delete-all.png (100%) rename docs/product/{explore => }/session-replay/img/replay-index-delete-visible.png (100%) rename docs/product/{explore => }/session-replay/img/replay-index-filtering.png (100%) rename docs/product/{explore => }/session-replay/index.mdx (95%) rename docs/product/{explore => }/session-replay/mobile/img/session-replay-redacted.png (100%) rename docs/product/{explore => }/session-replay/mobile/img/session-replay.png (100%) rename docs/product/{explore => }/session-replay/mobile/index.mdx (98%) rename docs/product/{explore => }/session-replay/mobile/performance-overhead.mdx (93%) rename docs/product/{explore => }/session-replay/replay-details.mdx (100%) rename docs/product/{explore => }/session-replay/replay-page-and-filters.mdx (84%) rename docs/product/{explore => }/session-replay/web/img/session-replay-what-is-a-replay.png (100%) rename docs/product/{explore => }/session-replay/web/img/session-replay.png (100%) rename docs/product/{explore => }/session-replay/web/index.mdx (95%) rename docs/product/{explore => }/session-replay/web/performance-overhead.mdx (95%) rename docs/product/{explore => }/trace-explorer/img/Trace_Explorer_home.png (100%) rename docs/product/{explore => }/trace-explorer/img/Trace_explorer_alerts.png (100%) rename docs/product/{explore => }/trace-explorer/img/Trace_explorer_low_samples.png (100%) rename docs/product/{explore => }/trace-explorer/img/Trace_explorer_low_samples_old.png (100%) rename docs/product/{explore => }/trace-explorer/img/Trace_explorer_search.png (100%) rename docs/product/{explore => }/trace-explorer/img/attribute_comparison.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer01.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer02.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer03.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer04.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer05.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer06.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace-explorer07.png (100%) rename docs/product/{explore => }/trace-explorer/img/trace_explorer_save.png (100%) rename docs/product/{explore => }/trace-explorer/index.mdx (97%) diff --git a/docs/ai/index.mdx b/docs/ai/index.mdx index 2f559efd62508c..bc07ff58716221 100644 --- a/docs/ai/index.mdx +++ b/docs/ai/index.mdx @@ -87,14 +87,14 @@ Looking for Sentry's AI-powered debugging features? Sentry uses AI to help you d className="w-full md:w-[calc(50%-12px)]" /> -Span metrics are great for enriching your existing traces with custom data. If you need metrics that are independent of tracing — such as business event counters, success/failure rates, or aggregates that aren't affected by trace sampling — use [Application Metrics](/product/explore/metrics/) instead. +Span metrics are great for enriching your existing traces with custom data. If you need metrics that are independent of tracing — such as business event counters, success/failure rates, or aggregates that aren't affected by trace sampling — use [Application Metrics](/product/metrics/) instead. diff --git a/docs/concepts/otlp/forwarding/sources/aws-cloudwatch.mdx b/docs/concepts/otlp/forwarding/sources/aws-cloudwatch.mdx index e64d12f2bbc7e8..1168fc4c3382ba 100644 --- a/docs/concepts/otlp/forwarding/sources/aws-cloudwatch.mdx +++ b/docs/concepts/otlp/forwarding/sources/aws-cloudwatch.mdx @@ -197,4 +197,4 @@ service: - [AWS CloudWatch Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscloudwatchreceiver) - [AWS SDK Authentication](https://docs.aws.amazon.com/sdk-for-go/v1/developer-guide/configuring-sdk.html) - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/) -- [Sentry Logs](/product/explore/logs/) +- [Sentry Logs](/product/logs/) diff --git a/docs/concepts/otlp/forwarding/sources/kafka.mdx b/docs/concepts/otlp/forwarding/sources/kafka.mdx index 94e6720c7923b7..4f519d83d5418c 100644 --- a/docs/concepts/otlp/forwarding/sources/kafka.mdx +++ b/docs/concepts/otlp/forwarding/sources/kafka.mdx @@ -193,4 +193,4 @@ The Kafka Receiver supports various encodings for different signal types: - [Kafka Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/kafkareceiver) - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/) -- [Sentry Logs](/product/explore/logs/) +- [Sentry Logs](/product/logs/) diff --git a/docs/concepts/otlp/forwarding/sources/nginx.mdx b/docs/concepts/otlp/forwarding/sources/nginx.mdx index 4de840f9d2c6c8..54b8094291428b 100644 --- a/docs/concepts/otlp/forwarding/sources/nginx.mdx +++ b/docs/concepts/otlp/forwarding/sources/nginx.mdx @@ -288,4 +288,4 @@ To run in the background: - [File Log Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver) - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/) -- [Sentry Logs](/product/explore/logs/) +- [Sentry Logs](/product/logs/) diff --git a/docs/concepts/otlp/forwarding/sources/syslog.mdx b/docs/concepts/otlp/forwarding/sources/syslog.mdx index 75506da2649a01..ea126df8dd736d 100644 --- a/docs/concepts/otlp/forwarding/sources/syslog.mdx +++ b/docs/concepts/otlp/forwarding/sources/syslog.mdx @@ -163,4 +163,4 @@ log { - [Syslog Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/syslogreceiver) - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/) -- [Sentry Logs](/product/explore/logs/) +- [Sentry Logs](/product/logs/) diff --git a/docs/concepts/otlp/forwarding/sources/windows-events.mdx b/docs/concepts/otlp/forwarding/sources/windows-events.mdx index d241b3089d242c..bb821dc4bcdb8e 100644 --- a/docs/concepts/otlp/forwarding/sources/windows-events.mdx +++ b/docs/concepts/otlp/forwarding/sources/windows-events.mdx @@ -237,4 +237,4 @@ C:\otel-collector\otelcol-contrib.exe --config C:\otel-collector\config_debug.ya - [Windows Event Log Receiver Documentation](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/windowseventlogreceiver) - [Sentry OpenTelemetry Collector Configuration](/concepts/otlp/forwarding/pipelines/collector/) -- [Sentry Logs](/product/explore/logs/) +- [Sentry Logs](/product/logs/) diff --git a/docs/concepts/search/index.mdx b/docs/concepts/search/index.mdx index 175520ab0acfbb..151699c2abd3b7 100644 --- a/docs/concepts/search/index.mdx +++ b/docs/concepts/search/index.mdx @@ -60,7 +60,7 @@ Here are some examples of valid comparison operator searches: -`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/). +`OR` and `AND` search conditions are only available for [Discover](/product/discover-queries/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/). diff --git a/docs/concepts/search/searchable-properties/session-replay.mdx b/docs/concepts/search/searchable-properties/session-replay.mdx index a6f07388f4f66c..40694cde412197 100644 --- a/docs/concepts/search/searchable-properties/session-replay.mdx +++ b/docs/concepts/search/searchable-properties/session-replay.mdx @@ -4,7 +4,7 @@ description: "Learn more about searchable session replay properties." sidebar_order: 30 --- -[Session Replay](/product/explore/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI. +[Session Replay](/product/session-replay/) provides a video-like reproduction of user interactions on a site or web app. All user interactions, including page visits, mouse movements, clicks, and scrolls, are captured, helping developers connect the dots between a known issue and how a user experienced it in the UI. You can search by session replay properties on the **Replay** page. @@ -102,7 +102,7 @@ The `title` of an element that was clicked. For example, `Save this comment` wou ### `count_dead_clicks` -The number of [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).) within a replay. +The number of [dead clicks](/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).) within a replay. - **Type:** number @@ -114,7 +114,7 @@ The number of errors within a replay. ### `count_rage_clicks` -The number of [rage clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks) within a replay. +The number of [rage clicks](/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks) within a replay. - **Type:** number @@ -138,7 +138,7 @@ The number of URLs that the user visited during a replay recording. ### `dead.selector` -Similar to the `click.selector` search property, but only queries on [dead clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. +Similar to the `click.selector` search property, but only queries on [dead clicks](/product/session-replay/replay-page-and-filters/#:~:text=Dead%20Clicks%3A%20User%20clicks%20on%20a%20and%20button%20tags%20that%20do%20not%20result%20in%20any%20page%20activity%20after%207%20seconds%20(i.e.%20no%20HTML%20was%20added%2C%20removed%2C%20or%20updated%3B%20no%20visual%20changes%20were%20observed%20in%20the%20page).). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. - **Type:** string @@ -228,7 +228,7 @@ The id of the project. ### `rage.selector` -Similar to the `click.selector` search property, but only queries on [rage clicks](/product/explore/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. +Similar to the `click.selector` search property, but only queries on [rage clicks](/product/session-replay/replay-page-and-filters/#:~:text=Rage%20Clicks%3A%20Five%20or%20more%20clicks%20on%20a%20dead%20element%20(it%20exhibits%20no%20page%20activity%20after%207%20seconds.)%20Rage%20clicks%20are%20a%20subset%20of%20dead%20clicks). An element identified using a subset of CSS selector syntax. For example, `#section-1` or `span.active` or `span[role=button]` or `.active[role=button]` would all match the element ``. Note that, CSS combinators, pseudo selectors, and attr selectors other than `=` are not supported. - **Type:** string diff --git a/docs/concepts/search/searchable-properties/spans.mdx b/docs/concepts/search/searchable-properties/spans.mdx index 5af0aa9565d266..b3c585a7f53692 100644 --- a/docs/concepts/search/searchable-properties/spans.mdx +++ b/docs/concepts/search/searchable-properties/spans.mdx @@ -8,7 +8,7 @@ Spans are the underlying data element captured in Sentry SDKs that together make You can search by span properties in the following [Sentry](https://sentry.io) pages: -- [Traces](/product/explore/traces/) - when searching for a trace containing spans with matching properties +- [Traces](/product/trace-explorer/) - when searching for a trace containing spans with matching properties When you search for span properties within the **Traces** page, the search will return any trace that contains _one or more spans_ that match your span properties filter. diff --git a/docs/guides/custom-spans.mdx b/docs/guides/custom-spans.mdx index 28d2050cb58708..0165c0ba16a1f9 100644 --- a/docs/guides/custom-spans.mdx +++ b/docs/guides/custom-spans.mdx @@ -4,7 +4,7 @@ sidebar_order: 30 description: "Add custom instrumentation for visibility beyond auto-instrumentation and set up alerts." --- -You've got your Sentry SDK [auto-instrumentation](/product/explore/trace-explorer/) running. Now what? +You've got your Sentry SDK [auto-instrumentation](/product/trace-explorer/) running. Now what? Auto-instrumentation captures HTTP, database, and framework operations. But it can't see business logic, third-party APIs without auto-instrumentation, or background jobs. This guide shows you where to add custom spans to fill in those gaps. The custom spans in this guide add business context, logical groupings, and attributes that auto-instrumentation can't provide. In many cases, your custom spans will appear as parents of auto-generated child spans. @@ -763,4 +763,4 @@ transaction.finish() ## Next Steps -Explore the [Trace Explorer product walkthrough guides](/product/explore/trace-explorer/) to learn more about the Sentry interface and discover additional tips. +Explore the [Trace Explorer product walkthrough guides](/product/trace-explorer/) to learn more about the Sentry interface and discover additional tips. diff --git a/docs/guides/issues-errors.mdx b/docs/guides/issues-errors.mdx index 04a06d50c06078..d962c6c9c3810a 100644 --- a/docs/guides/issues-errors.mdx +++ b/docs/guides/issues-errors.mdx @@ -225,7 +225,7 @@ Enable the [User Feedback Widget](/platforms/javascript/user-feedback/) to let u ### Capture Context, Not Just Exceptions -When you catch an error, add tags and context to make debugging instant. Set user info globally so it applies to all events. Enable [Session Replays](/product/explore/session-replay/) and [Logs](/product/explore/logs/) for even more visibility. +When you catch an error, add tags and context to make debugging instant. Set user info globally so it applies to all events. Enable [Session Replays](/product/session-replay/) and [Logs](/product/logs/) for even more visibility. ```javascript {tabTitle: JavaScript} // Set user globally (e.g., after login) diff --git a/docs/guides/logs.mdx b/docs/guides/logs.mdx index 2b8f4318da36f9..eadf4e5f08de6c 100644 --- a/docs/guides/logs.mdx +++ b/docs/guides/logs.mdx @@ -4,7 +4,7 @@ sidebar_order: 10 description: "Practical guidance on what to log, how to search logs, and when to set alerts." --- -You've set up [Sentry Logs](/product/explore/logs/). Now what? +You've set up [Sentry Logs](/product/logs/). Now what? This guide covers the high-value logging patterns that help you debug faster and catch problems before users report them. @@ -1085,4 +1085,4 @@ If you can't install the Sentry SDK or need platform-level logs (CDN, database, ## Next Steps -Explore the [Logs product walkthrough guides](/product/explore/logs/) to learn more about the Sentry interface and discover additional tips. +Explore the [Logs product walkthrough guides](/product/logs/) to learn more about the Sentry interface and discover additional tips. diff --git a/docs/guides/metrics.mdx b/docs/guides/metrics.mdx index 35e9193e224b5f..0b5378e16b43bc 100644 --- a/docs/guides/metrics.mdx +++ b/docs/guides/metrics.mdx @@ -4,7 +4,7 @@ sidebar_order: 15 description: "Practical guidance on what metrics to track, how to explore them, and when to set alerts." --- -You've set up [Sentry Metrics](/product/explore/metrics/). Now what? +You've set up [Sentry Metrics](/product/metrics/). Now what? This guide covers the high-value metric patterns that give you visibility into application health and how to drill into traces when something looks off. @@ -637,4 +637,4 @@ You'll soon be able to: All three are trace-connected. Start wherever makes sense and navigate to the others. -Explore the [Application Metrics product walkthrough](/product/explore/metrics/) to learn more about the Sentry interface and discover additional tips. \ No newline at end of file +Explore the [Application Metrics product walkthrough](/product/metrics/) to learn more about the Sentry interface and discover additional tips. \ No newline at end of file diff --git a/docs/guides/querying-traces.mdx b/docs/guides/querying-traces.mdx index b0740ee1e2fa2b..63368cdbaa2d88 100644 --- a/docs/guides/querying-traces.mdx +++ b/docs/guides/querying-traces.mdx @@ -4,7 +4,7 @@ sidebar_order: 20 description: "Find performance issues using data Sentry captures automatically and set up alerts." --- -You've enabled [Sentry Tracing](/product/explore/trace-explorer/). Now what? +You've enabled [Sentry Tracing](/product/trace-explorer/). Now what? Sentry's auto-instrumentation captures a lot without custom code. This guide shows you how to query that data to find performance issues. @@ -90,4 +90,4 @@ Learn about [creating alerts](/product/monitors-and-alerts/alerts/) and [notific ## Next Steps -Explore the [Trace Explorer product walkthrough guides](/product/explore/trace-explorer/) to learn more about the Sentry interface and discover additional tips. +Explore the [Trace Explorer product walkthrough guides](/product/trace-explorer/) to learn more about the Sentry interface and discover additional tips. diff --git a/docs/guides/session-replay.mdx b/docs/guides/session-replay.mdx index c77ad2286370bd..098b549620aa05 100644 --- a/docs/guides/session-replay.mdx +++ b/docs/guides/session-replay.mdx @@ -4,7 +4,7 @@ sidebar_order: 40 description: "Practical guidance on debugging errors and finding UX issues with Session Replay." --- -You've set up [Sentry Session Replay](/product/explore/session-replay/). Now what? +You've set up [Sentry Session Replay](/product/session-replay/). Now what? Stack traces tell you _what_ broke. Replay shows you _how_ it broke. This guide covers how to use replay to debug errors and spot UX problems before users report them. @@ -132,4 +132,4 @@ Be selective. Never unmask form inputs, and review your [privacy configuration]( ## Next Steps -Explore the [Session Replay product walkthrough guides](/product/explore/session-replay/) to learn more about the Sentry interface and discover additional tips. +Explore the [Session Replay product walkthrough guides](/product/session-replay/) to learn more about the Sentry interface and discover additional tips. diff --git a/docs/integrations/feature-flag/generic/index.mdx b/docs/integrations/feature-flag/generic/index.mdx index 2f9d89009480e8..a41d1c9955fe75 100644 --- a/docs/integrations/feature-flag/generic/index.mdx +++ b/docs/integrations/feature-flag/generic/index.mdx @@ -10,7 +10,7 @@ Sentry can track flag evaluations as they happen within your application. Flag ### Set Up Evaluation Tracking -To set up evaluation tracking, visit the [explore page](/product/explore/feature-flags/) and select the language and SDK of your choice. Not using a supported SDK? That's okay. We support generic solutions for your existing system. +To set up evaluation tracking, visit the [explore page](/product/issues/issue-details/feature-flags/) and select the language and SDK of your choice. Not using a supported SDK? That's okay. We support generic solutions for your existing system. To set up generic evaluation tracking, visit one of our supported languages' pages: * [JavaScript](/platforms/javascript/configuration/integrations/featureflags/) diff --git a/docs/integrations/session-replay/index.mdx b/docs/integrations/session-replay/index.mdx index feb04e808ad41b..4d1ff1feaeadf2 100644 --- a/docs/integrations/session-replay/index.mdx +++ b/docs/integrations/session-replay/index.mdx @@ -6,7 +6,7 @@ description: "Learn more about third-party session replay integrations." -Looking for Sentry's built-in Session Replay product? Click here to learn more. +Looking for Sentry's built-in Session Replay product? Click here to learn more. diff --git a/docs/platforms/android/index.mdx b/docs/platforms/android/index.mdx index 368daf3b21f56d..e747818a6bb42b 100644 --- a/docs/platforms/android/index.mdx +++ b/docs/platforms/android/index.mdx @@ -24,7 +24,7 @@ If you don't already have an account and Sentry project established, head over t ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/android/metrics/index.mdx b/docs/platforms/android/metrics/index.mdx index bac3f67368705c..450a55657b7875 100644 --- a/docs/platforms/android/metrics/index.mdx +++ b/docs/platforms/android/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, distributions, and sets from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, distributions, and sets from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/android/overhead/index.mdx b/docs/platforms/android/overhead/index.mdx index 0f74d51230887a..1438040c3d089a 100644 --- a/docs/platforms/android/overhead/index.mdx +++ b/docs/platforms/android/overhead/index.mdx @@ -41,8 +41,8 @@ As stated in our product docs ## Profiling -As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. +As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. ## Session Replay -As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. +As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. diff --git a/docs/platforms/android/session-replay/index.mdx b/docs/platforms/android/session-replay/index.mdx index 2f0fab42d00111..b86c62054bf55e 100644 --- a/docs/platforms/android/session-replay/index.mdx +++ b/docs/platforms/android/session-replay/index.mdx @@ -7,9 +7,9 @@ notSupported: description: "Learn how to enable Session Replay in your mobile app." --- -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. +[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. -By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/explore/session-replay/). +By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/session-replay/). ## Pre-requisites diff --git a/docs/platforms/android/session-replay/performance-overhead.mdx b/docs/platforms/android/session-replay/performance-overhead.mdx index 176c9a30c57819..e8a8d0bad3a633 100644 --- a/docs/platforms/android/session-replay/performance-overhead.mdx +++ b/docs/platforms/android/session-replay/performance-overhead.mdx @@ -7,7 +7,7 @@ description: "Learn about how enabling Session Replay impacts the performance of If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-android) app. -You can learn more about the various optimizations implemented in the Android Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs. +You can learn more about the various optimizations implemented in the Android Replay SDK in the [Replay Performance Overhead](/product/session-replay/mobile/performance-overhead/) docs. ## Benchmarking the Android Replay SDK diff --git a/docs/platforms/android/session-replay/troubleshooting.mdx b/docs/platforms/android/session-replay/troubleshooting.mdx index fe6838091eab5b..0ae04df5f5c80f 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/explore/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/overhead/index.mdx b/docs/platforms/apple/common/overhead/index.mdx index 5db186af55bd08..591d2cede49c09 100644 --- a/docs/platforms/apple/common/overhead/index.mdx +++ b/docs/platforms/apple/common/overhead/index.mdx @@ -47,7 +47,7 @@ As stated in our product docs ## Profiling -As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. +As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. @@ -55,6 +55,6 @@ As stated in our prod ## Session Replay -As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. +As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. diff --git a/docs/platforms/apple/common/session-replay/index.mdx b/docs/platforms/apple/common/session-replay/index.mdx index c6237eeb14f04b..090717927ef899 100644 --- a/docs/platforms/apple/common/session-replay/index.mdx +++ b/docs/platforms/apple/common/session-replay/index.mdx @@ -22,9 +22,9 @@ Before enabling Session Replay in production, verify your masking configuration -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. +[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. -By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/explore/session-replay/). +By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/session-replay/). ## Pre-requisites diff --git a/docs/platforms/apple/common/session-replay/performance-overhead.mdx b/docs/platforms/apple/common/session-replay/performance-overhead.mdx index f95215135f887f..00fb47a88d1456 100644 --- a/docs/platforms/apple/common/session-replay/performance-overhead.mdx +++ b/docs/platforms/apple/common/session-replay/performance-overhead.mdx @@ -19,7 +19,7 @@ notSupported: If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source [Pocket Casts](https://github.com/Automattic/pocket-casts-ios) app. -You can learn more about the various performance overhead optimizations implemented in the iOS Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs. +You can learn more about the various performance overhead optimizations implemented in the iOS Replay SDK in the [Replay Performance Overhead](/product/session-replay/mobile/performance-overhead/) docs. ## Performance on Older Devices diff --git a/docs/platforms/apple/common/session-replay/troubleshooting.mdx b/docs/platforms/apple/common/session-replay/troubleshooting.mdx index 36a53c2bd6b45a..0d46733d1793e7 100644 --- a/docs/platforms/apple/common/session-replay/troubleshooting.mdx +++ b/docs/platforms/apple/common/session-replay/troubleshooting.mdx @@ -53,7 +53,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/explore/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 197790eb580dfd..f7a46288e99a2a 100644 --- a/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx +++ b/docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx @@ -223,7 +223,7 @@ With this feature, the SDK differentiates between four different app start types - **Prewarmed cold start** - **Prewarmed warm start** -You can filter for different app start types in [Discover](/product/explore/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`. +You can filter for different app start types in [Discover](/product/discover-queries/) with `app_start_type:cold.prewarmed`, `app_start_type:warm.prewarmed`, `app_start_type:cold`, and `app_start_type:warm`. To disable prewarmed app start tracing: diff --git a/docs/platforms/dart/common/metrics/index.mdx b/docs/platforms/dart/common/metrics/index.mdx index 22bbd8ad7494e9..35f1b313f1da8d 100644 --- a/docs/platforms/dart/common/metrics/index.mdx +++ b/docs/platforms/dart/common/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/dart/guides/flutter/index.mdx b/docs/platforms/dart/guides/flutter/index.mdx index d12c2a3c628ef4..4cd1e55ca1eeda 100644 --- a/docs/platforms/dart/guides/flutter/index.mdx +++ b/docs/platforms/dart/guides/flutter/index.mdx @@ -23,7 +23,7 @@ If you don't already have an account and Sentry project established, head over t ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/dart/guides/flutter/overhead/index.mdx b/docs/platforms/dart/guides/flutter/overhead/index.mdx index 266d64b466aa15..8eecdb1395b435 100644 --- a/docs/platforms/dart/guides/flutter/overhead/index.mdx +++ b/docs/platforms/dart/guides/flutter/overhead/index.mdx @@ -41,7 +41,7 @@ As stated in our product docs ## Profiling -As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. +As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. ## SDK Size diff --git a/docs/platforms/dart/guides/flutter/session-replay/index.mdx b/docs/platforms/dart/guides/flutter/session-replay/index.mdx index be6df58494f453..cd06cba1f70653 100644 --- a/docs/platforms/dart/guides/flutter/session-replay/index.mdx +++ b/docs/platforms/dart/guides/flutter/session-replay/index.mdx @@ -13,9 +13,9 @@ Flutter Session Replay is available on **iOS** and **Android**. -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. +[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. -By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/explore/session-replay/). +By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/session-replay/). ## Pre-requisites diff --git a/docs/platforms/dart/guides/flutter/session-replay/performance-overhead.mdx b/docs/platforms/dart/guides/flutter/session-replay/performance-overhead.mdx index 060a68ed9789e2..eddf2038fa4aa0 100644 --- a/docs/platforms/dart/guides/flutter/session-replay/performance-overhead.mdx +++ b/docs/platforms/dart/guides/flutter/session-replay/performance-overhead.mdx @@ -5,7 +5,7 @@ notSupported: description: "Learn about how enabling Session Replay impacts the performance of your Flutter app." --- -If you're considering enabling Session Replay, it's important to understand the potential performance impact to your app. Learn more about Replay SDK optimizations in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs. +If you're considering enabling Session Replay, it's important to understand the potential performance impact to your app. Learn more about Replay SDK optimizations in the [Replay Performance Overhead](/product/session-replay/mobile/performance-overhead/) docs. Meaningful metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics. To provide a baseline, we measure replay overhead using this [Open Food Facts app](https://github.com/openfoodfacts/smooth-app/). We chose Open Food Facts because it's an actively maintained open source app that presents several scrollable, interactable lists of both text and images during onboarding. The app also includes native functionality like a default camera view for barcode scanning, making for a more comprehensive testing scenario. diff --git a/docs/platforms/dotnet/common/profiling/index.mdx b/docs/platforms/dotnet/common/profiling/index.mdx index 75869e10df4672..ecb7a4e32fd0f4 100644 --- a/docs/platforms/dotnet/common/profiling/index.mdx +++ b/docs/platforms/dotnet/common/profiling/index.mdx @@ -16,7 +16,7 @@ notSupported: -With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments. +With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real user devices in production to give you a complete picture of how your application performs in a variety of environments. diff --git a/docs/platforms/dotnet/index.mdx b/docs/platforms/dotnet/index.mdx index b8181ba3ec7ae9..ebe5c6cfea4953 100644 --- a/docs/platforms/dotnet/index.mdx +++ b/docs/platforms/dotnet/index.mdx @@ -26,7 +26,7 @@ If you're using a framework, such as ASP.NET Core or MAUI, please select the fra ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/go/common/metrics/index.mdx b/docs/platforms/go/common/metrics/index.mdx index 44992ed7d452ac..3752c402e4ed47 100644 --- a/docs/platforms/go/common/metrics/index.mdx +++ b/docs/platforms/go/common/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With [Sentry's Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With [Sentry's Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Prerequisites diff --git a/docs/platforms/java/guides/jul/usage/advanced-usage.mdx b/docs/platforms/java/guides/jul/usage/advanced-usage.mdx index 9c0fec1d091661..7661960a978596 100644 --- a/docs/platforms/java/guides/jul/usage/advanced-usage.mdx +++ b/docs/platforms/java/guides/jul/usage/advanced-usage.mdx @@ -161,7 +161,7 @@ class MyClass { Starting with Sentry version 6.0.0 and up, you can define a list of `MDC tags` that will be viewable as `Tags` in the Sentry UI. `MDC Tags` not in this list will be viewable as `Context Data`. -As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/explore/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". +As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". To define a tag that shall be sent with events and logs, add a `context-tags` entry with the tags as comma-separated items to the `sentry.properties` file. diff --git a/docs/platforms/java/guides/log4j2/advanced_usage.mdx b/docs/platforms/java/guides/log4j2/advanced_usage.mdx index 82cee16ea2d508..1585b44e01c181 100644 --- a/docs/platforms/java/guides/log4j2/advanced_usage.mdx +++ b/docs/platforms/java/guides/log4j2/advanced_usage.mdx @@ -144,7 +144,7 @@ class MyClass { Starting with Sentry version 6.0.0 and up, you can define a list of `MDC tags` that will be viewable as `Tags` in the Sentry UI. `MDC Tags` not in this list will be viewable as `Context Data`. -As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/explore/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". +As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". To define a tag that shall be sent with events and logs, add a `contextTags` attribute to the `` tag in your `log4j2.xml` with the tags as comma-separated items. diff --git a/docs/platforms/java/guides/logback/usage/advanced-usage.mdx b/docs/platforms/java/guides/logback/usage/advanced-usage.mdx index c643ce4450e57f..37cc54c446ac03 100644 --- a/docs/platforms/java/guides/logback/usage/advanced-usage.mdx +++ b/docs/platforms/java/guides/logback/usage/advanced-usage.mdx @@ -142,7 +142,7 @@ class MyClass { Starting with Sentry version 6.0.0 and up, you can define a list of `MDC tags` that will be viewable as `Tags` in the Sentry UI. `MDC Tags` not in this list will be viewable as `Context Data`. -As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/explore/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". +As of Sentry Java SDK version 8.24.0, `contextTags` also applies to [structured logs](https://docs.sentry.io/product/logs/). MDC properties matching the configured `contextTags` will be attached to log entries as attributes, prefixed with "mdc.". To define a tag that shall be sent with events and logs, add a `` entry inside the `` of the Sentry appender configuration in `logback.xml`. diff --git a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx index 6a26c6c4361cbe..0e38d2b0b6de08 100644 --- a/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/browserprofiling.mdx @@ -29,7 +29,7 @@ This integration only works inside a browser environment. _Import name: `Sentry.browserProfilingIntegration`_ -[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. +[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. The BrowserProfiling integration sets up automatic performance profiling for your frontend applications. It captures profiles via the [JS Self-Profiling API](https://wicg.github.io/js-self-profiling/) from the browser and sends them to Sentry. To use this integration, you also need to have the [BrowserTracing integration](../browsertracing) enabled. diff --git a/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx b/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx index ad45639778c82e..0d6fcfac95647a 100644 --- a/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/elementtiming.mdx @@ -30,7 +30,7 @@ This integration only works inside a browser environment. Requires SDK version ` _Import name: `Sentry.elementTimingIntegration`_ -The `elementTimingIntegration` collects render and load timing data from the browser's [Element Timing API](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceElementTiming) and emits it as [Sentry Application Metrics](/product/explore/metrics/) (distributions). This lets you track how long key elements (hero images, text blocks, etc.) take to appear on screen. +The `elementTimingIntegration` collects render and load timing data from the browser's [Element Timing API](https://developer.mozilla.org/en-US/docs/Web/API/PerformanceElementTiming) and emits it as [Sentry Application Metrics](/product/metrics/) (distributions). This lets you track how long key elements (hero images, text blocks, etc.) take to appear on screen. diff --git a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx index e1ea52f0ab38de..17f963214f1af8 100644 --- a/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/nodeprofiling.mdx @@ -32,7 +32,7 @@ This integration only works in the Node.js runtime. `nodeProfilingIntegration` must be imported from the `@sentry/profiling-node` package. -[Profiling](/product/explore/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. +[Profiling](/product/profiling/) offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level visibility into your application in a production environment. The NodeProfiling integration sets up automatic performance profiling for your Node.js applications. It captures profiles via v8 and sends them to Sentry. To use this integration, you also need to have the performance monitoring enabled. diff --git a/docs/platforms/javascript/common/configuration/integrations/replay.mdx b/docs/platforms/javascript/common/configuration/integrations/replay.mdx index 4d356e4ed594b3..0eafe8b9edffb6 100644 --- a/docs/platforms/javascript/common/configuration/integrations/replay.mdx +++ b/docs/platforms/javascript/common/configuration/integrations/replay.mdx @@ -29,7 +29,7 @@ This integration only works inside a browser environment. _Import name: `Sentry.replayIntegration`_ -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. +[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. Read more about [setting up Session Replay](./../../../session-replay/). diff --git a/docs/platforms/javascript/common/index.mdx b/docs/platforms/javascript/common/index.mdx index c5dfb08e67a951..7409ce12ea0e3d 100644 --- a/docs/platforms/javascript/common/index.mdx +++ b/docs/platforms/javascript/common/index.mdx @@ -32,7 +32,7 @@ This guide focuses on plain JavaScript. If you're working with React, Next.js, o ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/explore/session-replay/web/getting-started/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/session-replay/web/getting-started/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. @@ -64,7 +64,7 @@ Select which Sentry features you'd like to install in addition to Error Monitori -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/common/logs/index.mdx b/docs/platforms/javascript/common/logs/index.mdx index d84e3f597db6e5..6a398b665bf340 100644 --- a/docs/platforms/javascript/common/logs/index.mdx +++ b/docs/platforms/javascript/common/logs/index.mdx @@ -205,8 +205,8 @@ Sentry.init({ Everything in Sentry is linked by trace. When you're viewing a log, you can jump to the parent trace to see the full request context. When you're viewing a trace, you can see all logs emitted during that operation. This connection makes it easy to move between high-level performance data and detailed diagnostic logs. -- **[Traces](/product/explore/traces/)** — Logs emitted during an active span automatically include `sentry.trace.parent_span_id`. Click through from any log to see the full trace, or filter logs by trace ID to see everything that happened during a specific request. -- **[Session Replay](/product/explore/session-replay/)** — Logs include `sentry.replay_id` when a replay is active. Jump from a log entry directly to the replay to see what the user was doing when the log was emitted. +- **[Traces](/product/trace-explorer/)** — Logs emitted during an active span automatically include `sentry.trace.parent_span_id`. Click through from any log to see the full trace, or filter logs by trace ID to see everything that happened during a specific request. +- **[Session Replay](/product/session-replay/)** — Logs include `sentry.replay_id` when a replay is active. Jump from a log entry directly to the replay to see what the user was doing when the log was emitted. - **[Errors](/product/issues/)** — Logs capture the journey leading up to a failure. When an error occurs, your logs show what data was processed, which code paths executed, and what state the system was in — context that stack traces alone can't provide. ## Best Practices diff --git a/docs/platforms/javascript/common/metrics/index.mdx b/docs/platforms/javascript/common/metrics/index.mdx index fbc92a96bd1687..88e4fa95114f09 100644 --- a/docs/platforms/javascript/common/metrics/index.mdx +++ b/docs/platforms/javascript/common/metrics/index.mdx @@ -12,7 +12,7 @@ notSupported: -With [Sentry's Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With [Sentry's Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Prerequisites diff --git a/docs/platforms/javascript/common/migration/v9-to-v10.mdx b/docs/platforms/javascript/common/migration/v9-to-v10.mdx index f43655acfeedd0..be905dce852bce 100644 --- a/docs/platforms/javascript/common/migration/v9-to-v10.mdx +++ b/docs/platforms/javascript/common/migration/v9-to-v10.mdx @@ -88,7 +88,7 @@ The changes outlined in this section detail deprecated APIs that are now removed - `BaseClient` was removed, use `Client` as a direct replacement. - `hasTracingEnabled` was removed, use `hasSpansEnabled` as a direct replacement. -- The internal `logger` and type `Logger` exports in `@sentry/core` were removed, use `debug` and type `SentryDebugLogger` instead. This does not affect the `logger` export used for [Sentry Logging](/product/explore/logs/getting-started/) +- The internal `logger` and type `Logger` exports in `@sentry/core` were removed, use `debug` and type `SentryDebugLogger` instead. This does not affect the `logger` export used for [Sentry Logging](/product/logs/getting-started/) - The `_experiments.enableLogs` and `_experiments.beforeSendLog` options were removed, use the top-level `enableLogs` and `beforeSendLog` options instead. ```js diff --git a/docs/platforms/javascript/common/session-replay/index.mdx b/docs/platforms/javascript/common/session-replay/index.mdx index 761f70c6bbdcad..f8ff311a547b1c 100644 --- a/docs/platforms/javascript/common/session-replay/index.mdx +++ b/docs/platforms/javascript/common/session-replay/index.mdx @@ -34,7 +34,7 @@ Session Replay is no longer supported in `@sentry/capacitor` as of version 4.0.0 -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a video-like reproduction of what was happening in the user's browser before, during, and after the issue. You can rewind and replay your application's DOM state and see key user interactions, like mouse clicks, scrolls, network requests, and console entries, in a single combined UI inspired by your browser's DevTools. +[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. @@ -310,7 +310,7 @@ Errors that happen on the page while a replay is running will be linked to the r ## Trace Linking -When [tracing](/product/explore/traces/) is enabled, traces are visible in the Replay timeline. This lets you see performance data in the context of what the user was doing — you can watch a user click a button, then see the corresponding network request and how long it took. +When [tracing](/product/trace-explorer/) is enabled, traces are visible in the Replay timeline. This lets you see performance data in the context of what the user was doing — you can watch a user click a button, then see the corresponding network request and how long it took. From the Replay Details page, click on any trace span in the timeline to jump directly to the trace view. From there, you can drill into individual spans, see database queries, API calls, and identify performance bottlenecks that affected the user's experience. diff --git a/docs/platforms/javascript/common/session-replay/troubleshooting.mdx b/docs/platforms/javascript/common/session-replay/troubleshooting.mdx index 1df9c24e9a2f68..2ef2818c186f51 100644 --- a/docs/platforms/javascript/common/session-replay/troubleshooting.mdx +++ b/docs/platforms/javascript/common/session-replay/troubleshooting.mdx @@ -119,7 +119,7 @@ We're always working on ways to reduce the bundle size. Additionally, there are -The Sentry SDK attempts to minimize potential [performance overhead](/product/explore/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change. +The Sentry SDK attempts to minimize potential [performance overhead](/product/session-replay/performance-overhead/#how-is-session-replay-optimized) in a few different ways. For example, by keeping track of the number of DOM mutations that are happening then disabling recording when a large number of changes are detected. Many simultaneous mutations can slow down a web page whether Session Replay is installed or not, but when a large number of mutations happen, the Replay client can incur an additional slowdown because it records each change. If you're seeing the "A large number of mutations was detected" message while watching a replay, it means that your page could be optimized. For example, a dropdown list with thousands of entries could be refactored so that rows are virtualized where only the visible rows are rendered in the DOM. Another potential solution is to paginate the results fetch more data as the user scrolls through it. The SDK has a configuration that allows you to configure the limits before recording stops. diff --git a/docs/platforms/javascript/common/tracing/index.mdx b/docs/platforms/javascript/common/tracing/index.mdx index 9eaa31dd67e3e2..12fd0a59ade4a1 100644 --- a/docs/platforms/javascript/common/tracing/index.mdx +++ b/docs/platforms/javascript/common/tracing/index.mdx @@ -89,7 +89,7 @@ You can also manually start spans to instrument specific parts of your code. Thi ## Replay Linking -When [Session Replay](/product/explore/session-replay/) is enabled, traces appear in the Replay timeline. This lets you correlate performance data with exactly what the user was seeing and doing. +When [Session Replay](/product/session-replay/) is enabled, traces appear in the Replay timeline. This lets you correlate performance data with exactly what the user was seeing and doing. From any trace, click the replay link to jump directly to the replay and see the user's experience during that operation. From a replay, click any trace span in the timeline to drill into performance details. diff --git a/docs/platforms/javascript/guides/angular/angular1.mdx b/docs/platforms/javascript/guides/angular/angular1.mdx index 8f67bdda403935..76e363293c0172 100644 --- a/docs/platforms/javascript/guides/angular/angular1.mdx +++ b/docs/platforms/javascript/guides/angular/angular1.mdx @@ -13,7 +13,7 @@ From version 7 onwards, the Sentry JavaScript SDK will not support AngularJS 1.x ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/explore/session-replay/web/getting-started/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/session-replay/web/getting-started/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx index 45816932d6b28e..575351f5a665bd 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/cjs-npm__v9.x.mdx @@ -22,7 +22,7 @@ Before you begin, make sure you have the following: ## 2. Install -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/guides/aws-lambda/install/esm-npm__v9.x.mdx b/docs/platforms/javascript/guides/aws-lambda/install/esm-npm__v9.x.mdx index fabdbc5de0d60d..f5e0288966fa44 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/esm-npm__v9.x.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/esm-npm__v9.x.mdx @@ -27,7 +27,7 @@ Before you begin, make sure you have the following: ## 2. Install -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx b/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx index 3074ba6534a4e3..299f2cfe35be44 100644 --- a/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx +++ b/docs/platforms/javascript/guides/aws-lambda/install/npm.mdx @@ -22,7 +22,7 @@ Before you begin, make sure you have the following: ## 2. Install -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/guides/react-router/index.mdx b/docs/platforms/javascript/guides/react-router/index.mdx index eaa9b230028fc2..fe68c5bed16184 100644 --- a/docs/platforms/javascript/guides/react-router/index.mdx +++ b/docs/platforms/javascript/guides/react-router/index.mdx @@ -45,7 +45,7 @@ If you're using React Router in data or declarative mode, follow the instruction If you prefer to configure Sentry manually, here are the configuration files the wizard would create: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/explore/session-replay/web/getting-started/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also get to the root of an error or performance issue faster, by watching a video-like reproduction of a user session with [session replay](/product/session-replay/web/getting-started/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/javascript/guides/remix/manual-setup__v8.x.mdx b/docs/platforms/javascript/guides/remix/manual-setup__v8.x.mdx index dac12085efcef0..41f0b9e8005024 100644 --- a/docs/platforms/javascript/guides/remix/manual-setup__v8.x.mdx +++ b/docs/platforms/javascript/guides/remix/manual-setup__v8.x.mdx @@ -9,7 +9,7 @@ If you can't (or prefer not to) run the [automatic setup](/platforms/javascript/ ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also analyze performance profiles from real users with [profiling](/product/explore/profiling/). Lastly, adding [session replay](/product/explore/session-replay/web/getting-started/) lets you get to the root of an error or performance issue faster by watching a video-like reproduction of a user session. +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also analyze performance profiles from real users with [profiling](/product/profiling/). Lastly, adding [session replay](/product/session-replay/web/getting-started/) lets you get to the root of an error or performance issue faster by watching a video-like reproduction of a user session. Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/native/metrics/index.mdx b/docs/platforms/native/metrics/index.mdx index 22bbd8ad7494e9..35f1b313f1da8d 100644 --- a/docs/platforms/native/metrics/index.mdx +++ b/docs/platforms/native/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/php/common/profiling/index.mdx b/docs/platforms/php/common/profiling/index.mdx index ecf6244ae58939..a8cff684e5d209 100644 --- a/docs/platforms/php/common/profiling/index.mdx +++ b/docs/platforms/php/common/profiling/index.mdx @@ -12,7 +12,7 @@ Profiling for PHP is supported with Sentry PHP SDK version `3.15.0` and above. -With [profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/php/guides/laravel/profiling/index.mdx b/docs/platforms/php/guides/laravel/profiling/index.mdx index e0afb1e2b3f75d..81e637b28ed857 100644 --- a/docs/platforms/php/guides/laravel/profiling/index.mdx +++ b/docs/platforms/php/guides/laravel/profiling/index.mdx @@ -12,7 +12,7 @@ Profiling for PHP is supported with Sentry Laravel SDK version `3.3.0` and above -With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/php/guides/symfony/profiling/index.mdx b/docs/platforms/php/guides/symfony/profiling/index.mdx index a4d47af57da9e5..c9c824e1949c13 100644 --- a/docs/platforms/php/guides/symfony/profiling/index.mdx +++ b/docs/platforms/php/guides/symfony/profiling/index.mdx @@ -12,7 +12,7 @@ Profiling for PHP is supported with Sentry Symfony SDK version `4.7.0` and above -With [Profiling](/product/explore/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. +With [Profiling](/product/profiling/), Sentry allows you to collect and analyze performance profiles from real users in production to give you a complete picture of how your application performs in a variety of environments. Under the hood, we're using Wikipedia's sampling profiler [Excimer](https://github.com/wikimedia/mediawiki-php-excimer). The Excimer PHP extension supports PHP 7.2 and up. diff --git a/docs/platforms/python/integrations/asgi/index.mdx b/docs/platforms/python/integrations/asgi/index.mdx index ca947b2014d481..19f08899c45933 100644 --- a/docs/platforms/python/integrations/asgi/index.mdx +++ b/docs/platforms/python/integrations/asgi/index.mdx @@ -23,7 +23,7 @@ uv add "sentry-sdk" ## Configure -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx b/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx index 4771b81624dd36..15d9c02f13c3bc 100644 --- a/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx +++ b/docs/platforms/python/integrations/aws-lambda/manual-instrumentation/index.mdx @@ -32,7 +32,7 @@ pip install --target ./package --upgrade sentry-sdk Here's how to use the AWS Lambda integration for the Python SDK: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/beam/index.mdx b/docs/platforms/python/integrations/beam/index.mdx index a77137a2643aa9..774a0733212b5a 100644 --- a/docs/platforms/python/integrations/beam/index.mdx +++ b/docs/platforms/python/integrations/beam/index.mdx @@ -9,7 +9,7 @@ The Beam integration currently parses the functions in [ParDo](https://github.co A Beam version of 2.12 or later is required. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/celery/crons.mdx b/docs/platforms/python/integrations/celery/crons.mdx index 812a94068576b9..ee8ea911e7cef6 100644 --- a/docs/platforms/python/integrations/celery/crons.mdx +++ b/docs/platforms/python/integrations/celery/crons.mdx @@ -44,7 +44,7 @@ Make sure to also set `monitor_beat_tasks=True` in `CeleryIntegration`. If you have set `monitor_beat_tasks=True` make sure that you do not do manual task monitoring using the `@sentry_sdk.monitor` decorator, because this will lead to double instrumentation. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/celery/index.mdx b/docs/platforms/python/integrations/celery/index.mdx index 91b0e08a70a38e..bd3d3eb9824ff6 100644 --- a/docs/platforms/python/integrations/celery/index.mdx +++ b/docs/platforms/python/integrations/celery/index.mdx @@ -30,7 +30,7 @@ If you have the `celery` package in your dependencies, the Celery integration wi When using Celery without Django, you'll need to initialize the Sentry SDK in both your application and the Celery worker processes spawned by the Celery daemon. -In addition to capturing errors, you can use Sentry for [distributed tracing](/concepts/key-terms/tracing/) and [profiling](/product/explore/profiling/). Select what you'd like to install to get the corresponding installation and configuration instructions below. +In addition to capturing errors, you can use Sentry for [distributed tracing](/concepts/key-terms/tracing/) and [profiling](/product/profiling/). Select what you'd like to install to get the corresponding installation and configuration instructions below. #### Set up Sentry in Celery Daemon or Worker Processes diff --git a/docs/platforms/python/integrations/cloudresourcecontext/index.mdx b/docs/platforms/python/integrations/cloudresourcecontext/index.mdx index d4238ea984cac9..d9025b69d540fd 100644 --- a/docs/platforms/python/integrations/cloudresourcecontext/index.mdx +++ b/docs/platforms/python/integrations/cloudresourcecontext/index.mdx @@ -24,7 +24,7 @@ uv add "sentry-sdk" Add `CloudResourceContextIntegration()` to your `integrations` list: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/gcp-functions/index.mdx b/docs/platforms/python/integrations/gcp-functions/index.mdx index f83b64e1df7fba..3e8e5ba51b2863 100644 --- a/docs/platforms/python/integrations/gcp-functions/index.mdx +++ b/docs/platforms/python/integrations/gcp-functions/index.mdx @@ -23,7 +23,7 @@ Limited Sentry support is available on newer Python runtimes by directly enablin You can use the Google Cloud Functions integration for the Python SDK like this: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/grpc/index.mdx b/docs/platforms/python/integrations/grpc/index.mdx index b8da89595d283c..6e006609666bff 100644 --- a/docs/platforms/python/integrations/grpc/index.mdx +++ b/docs/platforms/python/integrations/grpc/index.mdx @@ -26,7 +26,7 @@ Add `GRPCIntegration()` to your `integrations` list, and enable tracing. This will add appropriate intercepters to your server/client to capture errors and performance data. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/litestar/index.mdx b/docs/platforms/python/integrations/litestar/index.mdx index 90907d4309f3de..adb62dc33dc8a8 100644 --- a/docs/platforms/python/integrations/litestar/index.mdx +++ b/docs/platforms/python/integrations/litestar/index.mdx @@ -20,7 +20,7 @@ uv add sentry-sdk uvicorn If you have the `litestar` package in your dependencies, the Litestar integration will be enabled automatically when you initialize the Sentry SDK. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/ray/index.mdx b/docs/platforms/python/integrations/ray/index.mdx index 0d862e0de9d34f..2f196ddcbe2f8c 100644 --- a/docs/platforms/python/integrations/ray/index.mdx +++ b/docs/platforms/python/integrations/ray/index.mdx @@ -21,7 +21,7 @@ uv add "sentry-sdk" Add `RayIntegration()` to your `integrations` list: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/rq/index.mdx b/docs/platforms/python/integrations/rq/index.mdx index c76308e5c67228..1337e87434b681 100644 --- a/docs/platforms/python/integrations/rq/index.mdx +++ b/docs/platforms/python/integrations/rq/index.mdx @@ -23,7 +23,7 @@ If you have the `rq` package in your dependencies, the RQ integration will be en Create a file called `mysettings.py` with the following content: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/sanic/index.mdx b/docs/platforms/python/integrations/sanic/index.mdx index f8a5eb8f998f2e..1072b5a1cf04e0 100644 --- a/docs/platforms/python/integrations/sanic/index.mdx +++ b/docs/platforms/python/integrations/sanic/index.mdx @@ -34,7 +34,7 @@ To ensure that errors occurring in background tasks get reported to Sentry, we a The example below demonstrates the simplest recommended setup. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/serverless/index.mdx b/docs/platforms/python/integrations/serverless/index.mdx index f8add6cf00f6d0..bfbd3240ea04ab 100644 --- a/docs/platforms/python/integrations/serverless/index.mdx +++ b/docs/platforms/python/integrations/serverless/index.mdx @@ -28,7 +28,7 @@ uv add "sentry-sdk" Apply the `serverless_function` decorator to each function that might throw errors: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/socket/index.mdx b/docs/platforms/python/integrations/socket/index.mdx index 312c94135f8d97..593e43d004fb36 100644 --- a/docs/platforms/python/integrations/socket/index.mdx +++ b/docs/platforms/python/integrations/socket/index.mdx @@ -21,7 +21,7 @@ uv add "sentry-sdk" Add `SocketIntegration()` to your `integrations` list: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/spark/index.mdx b/docs/platforms/python/integrations/spark/index.mdx index 58e0befba0ec55..13c4d8f59403fa 100644 --- a/docs/platforms/python/integrations/spark/index.mdx +++ b/docs/platforms/python/integrations/spark/index.mdx @@ -14,7 +14,7 @@ The Spark driver integration is supported for Spark 2 and above. To configure the SDK, initialize it with the integration before you create a `SparkContext` or `SparkSession`. -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/strawberry/index.mdx b/docs/platforms/python/integrations/strawberry/index.mdx index 973d1fb1ee0fce..be8c6a34e4d585 100644 --- a/docs/platforms/python/integrations/strawberry/index.mdx +++ b/docs/platforms/python/integrations/strawberry/index.mdx @@ -20,7 +20,7 @@ uv add "sentry-sdk" ## Configure -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/tryton/index.mdx b/docs/platforms/python/integrations/tryton/index.mdx index cd88abf79c4f0a..acca6c0f71225b 100644 --- a/docs/platforms/python/integrations/tryton/index.mdx +++ b/docs/platforms/python/integrations/tryton/index.mdx @@ -10,7 +10,7 @@ The Tryton integration adds support for the [Tryton Framework Server](https://ww To configure the SDK, initialize it with the integration in a custom `wsgi.py` script: -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/integrations/wsgi/index.mdx b/docs/platforms/python/integrations/wsgi/index.mdx index e16bdc08418451..0a5fd2ffb7c8b0 100644 --- a/docs/platforms/python/integrations/wsgi/index.mdx +++ b/docs/platforms/python/integrations/wsgi/index.mdx @@ -22,7 +22,7 @@ uv add "sentry-sdk" ## Configure -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/python/profiling/index.mdx b/docs/platforms/python/profiling/index.mdx index d559abee02dcdb..fe8621adb8686e 100644 --- a/docs/platforms/python/profiling/index.mdx +++ b/docs/platforms/python/profiling/index.mdx @@ -8,7 +8,7 @@ sidebar_section: features -With [profiling](/product/explore/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. [Sentry's profiler](https://sentry.io/for/profiling/) captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and increase user satisfaction, as well as drive down costs. Learn how to enable and configure profiling in Python with Sentry's stable [Python SDK](https://sentry.io/for/python/) +With [profiling](/product/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. [Sentry's profiler](https://sentry.io/for/profiling/) captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and increase user satisfaction, as well as drive down costs. Learn how to enable and configure profiling in Python with Sentry's stable [Python SDK](https://sentry.io/for/python/) ## Enabling Continuous Profiling diff --git a/docs/platforms/react-native/index.mdx b/docs/platforms/react-native/index.mdx index d0dbfff207e979..1ca1b0b7a58adc 100644 --- a/docs/platforms/react-native/index.mdx +++ b/docs/platforms/react-native/index.mdx @@ -21,7 +21,7 @@ If you don't already have an account and Sentry project established, head over t ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/react-native/metrics/index.mdx b/docs/platforms/react-native/metrics/index.mdx index 291542844d31df..a8f09a376f3767 100644 --- a/docs/platforms/react-native/metrics/index.mdx +++ b/docs/platforms/react-native/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/react-native/overhead/index.mdx b/docs/platforms/react-native/overhead/index.mdx index d8a21fe5ea01cf..75bba9c43d4af7 100644 --- a/docs/platforms/react-native/overhead/index.mdx +++ b/docs/platforms/react-native/overhead/index.mdx @@ -41,8 +41,8 @@ As stated in our product docs ## Profiling -As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. +As stated in our product docs on the topic, Profiling adds some overhead, but should have minimal impact on the performance of your application. In typical scenarios, the expected overhead is less than 5% of the app's resource utilization. ## Session Replay -As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. +As stated in our product docs on the topic, Session Replay adds some overhead, but should have minimal impact on the performance of your application. For more details on the measured overhead, read the performance overhead docs for this SDK. diff --git a/docs/platforms/react-native/profiling/troubleshooting/index.mdx b/docs/platforms/react-native/profiling/troubleshooting/index.mdx index 3a5fc1e1cc1840..7359faebf0698c 100644 --- a/docs/platforms/react-native/profiling/troubleshooting/index.mdx +++ b/docs/platforms/react-native/profiling/troubleshooting/index.mdx @@ -13,7 +13,7 @@ If you don't see any profiling data in [sentry.io](https://sentry.io), you can t ### Limitations -Because profile samples are collected at a fixed sampling frequency, we recommend checking if profiling's [Performance Overhead](/product/explore/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/session-replay/index.mdx b/docs/platforms/react-native/session-replay/index.mdx index 53b2f3be637dfa..a50118e380b90d 100644 --- a/docs/platforms/react-native/session-replay/index.mdx +++ b/docs/platforms/react-native/session-replay/index.mdx @@ -7,9 +7,9 @@ notSupported: description: "Learn how to enable Session Replay in your mobile app." --- -[Session Replay](/product/explore/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. +[Session Replay](/product/session-replay/) helps you get to the root cause of an error or latency issue faster by providing you with a reproduction of what was happening in the user's device before, during, and after the issue. You can rewind and replay your application's state and see key user interactions, like taps, swipes, network requests, and console entries, in a single UI. -By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/explore/session-replay/). +By default, our Session Replay SDK masks all text content, images, and user input, giving you heightened confidence that no sensitive data will leave the device. To learn more, see [product docs](/product/session-replay/). ## Pre-requisites diff --git a/docs/platforms/react-native/session-replay/performance-overhead.mdx b/docs/platforms/react-native/session-replay/performance-overhead.mdx index 70d270883e585b..f2b7498cce7c45 100644 --- a/docs/platforms/react-native/session-replay/performance-overhead.mdx +++ b/docs/platforms/react-native/session-replay/performance-overhead.mdx @@ -7,7 +7,7 @@ description: "Learn about how enabling Session Replay impacts the performance of If you're considering enabling Session Replay, it's important to first understand the potential performance impact to your app. While accurate metrics require realistic testing where you apply typical access patterns and correlate the results with your business metrics, to provide a baseline, we measured the overhead using the open-source Pocket Casts app. -You can learn more about the various optimizations implemented in the React Native Replay SDK in the [Replay Performance Overhead](/product/explore/session-replay/mobile/performance-overhead/) docs. +You can learn more about the various optimizations implemented in the React Native Replay SDK in the [Replay Performance Overhead](/product/session-replay/mobile/performance-overhead/) docs. The React Native Replay SDK is a lightweight wrapper for the native iOS and Android SDKs, so its overhead is minimal and doesn't require separate measurement. Below are the benchmark results for each platform. diff --git a/docs/platforms/ruby/common/index.mdx b/docs/platforms/ruby/common/index.mdx index 2414afd753b503..9494ba95ce22e5 100644 --- a/docs/platforms/ruby/common/index.mdx +++ b/docs/platforms/ruby/common/index.mdx @@ -9,7 +9,7 @@ ## Features -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). Select which Sentry features you'd like to install in addition to Error Monitoring to get the corresponding installation and configuration instructions below. diff --git a/docs/platforms/rust/common/metrics/index.mdx b/docs/platforms/rust/common/metrics/index.mdx index f14d4356f51a27..b165fa663102ab 100644 --- a/docs/platforms/rust/common/metrics/index.mdx +++ b/docs/platforms/rust/common/metrics/index.mdx @@ -7,7 +7,7 @@ new: true sidebar_order: 5700 --- -With [Sentry's Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your Rust applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors and searched using their individual attributes. +With [Sentry's Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your Rust applications to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/rust/guides/tracing/index.mdx b/docs/platforms/rust/guides/tracing/index.mdx index c779c3058551a1..22198761213b67 100644 --- a/docs/platforms/rust/guides/tracing/index.mdx +++ b/docs/platforms/rust/guides/tracing/index.mdx @@ -90,7 +90,7 @@ async fn fail() { By default, error-level events from `tracing` are captured as Sentry events, while events at or above info level are added to the current scope as breadcrumbs. -Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/explore/logs/). +Additionally, if the `logs` feature flag of the `sentry` crate is enabled and the SDK is initialized with `enable_logs: true`, then events from `tracing` at info level or above are also captured as [structured logs](https://docs.sentry.io/product/logs/). This behavior can be customized by applying a custom `event_filter` when creating the layer. The following snippet shows the default `event_filter` that's applied when using the `sentry` crate with the `logs` feature flag. diff --git a/docs/platforms/unity/metrics/index.mdx b/docs/platforms/unity/metrics/index.mdx index d61b71eeac2596..2d7413d8daa05a 100644 --- a/docs/platforms/unity/metrics/index.mdx +++ b/docs/platforms/unity/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your Unity game to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your Unity game to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/platforms/unreal/metrics/index.mdx b/docs/platforms/unreal/metrics/index.mdx index 06d1b0eddc41f2..e11eb31e064043 100644 --- a/docs/platforms/unreal/metrics/index.mdx +++ b/docs/platforms/unreal/metrics/index.mdx @@ -7,7 +7,7 @@ sidebar_section: features new: true --- -With Sentry's [Application Metrics](/product/explore/metrics/), you can send counters, gauges, and distributions from your Unreal Engine game to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. +With Sentry's [Application Metrics](/product/metrics/), you can send counters, gauges, and distributions from your Unreal Engine game to Sentry. Once in Sentry, these metrics can be viewed alongside relevant errors, and searched using their individual attributes. ## Requirements diff --git a/docs/pricing/index.mdx b/docs/pricing/index.mdx index d5eb32da623ecc..6379d191a4a9f6 100644 --- a/docs/pricing/index.mdx +++ b/docs/pricing/index.mdx @@ -109,7 +109,7 @@ Tracing is enabled by and will be billed for in spans. Profile Hours are determined by the length of the profile in milliseconds and are billed in hours. Partial hours are prorated and rounded down to the nearest cent. Profile Hours can only be purchased with your PAYG budget. - [Transaction-Based profiling](/product/explore/profiling/transaction-vs-continuous-profiling/) is billed under either UI or Continuous Profile Hours, by extracting the duration from the samples that make up the profile. + [Transaction-Based profiling](/product/profiling/transaction-vs-continuous-profiling/) is billed under either UI or Continuous Profile Hours, by extracting the duration from the samples that make up the profile. **Continuous Profile Hours** diff --git a/docs/pricing/quotas/manage-application-metrics-quota.mdx b/docs/pricing/quotas/manage-application-metrics-quota.mdx index 09c01697054bbf..5d364067a42e5d 100644 --- a/docs/pricing/quotas/manage-application-metrics-quota.mdx +++ b/docs/pricing/quotas/manage-application-metrics-quota.mdx @@ -9,7 +9,7 @@ og_image: /og-images/pricing-quotas-manage-application-metrics-quota.png --- -[Application Metrics](/product/explore/metrics/) is currently available on Team, Business, and Developer plans. These plans include a certain amount of Application Metrics data to be processed and stored. Once you exceed your included quota, you'll be charged based on your pay-as-you-go (PAYG) budget. +[Application Metrics](/product/metrics/) is currently available on Team, Business, and Developer plans. These plans include a certain amount of Application Metrics data to be processed and stored. Once you exceed your included quota, you'll be charged based on your pay-as-you-go (PAYG) budget. ## Key Terms @@ -92,7 +92,7 @@ sentry_sdk.init( ### Disabling Metrics -If you want to stop sending Application Metrics from a specific SDK entirely, most SDKs expose an option to disable metrics without removing the rest of your Sentry configuration (for example, `enableMetrics: false` in JavaScript SDKs or `experimental.enableMetrics = false` on Apple platforms). See the [platform-specific metrics docs](/product/explore/metrics/getting-started/) for the option name on your SDK. +If you want to stop sending Application Metrics from a specific SDK entirely, most SDKs expose an option to disable metrics without removing the rest of your Sentry configuration (for example, `enableMetrics: false` in JavaScript SDKs or `experimental.enableMetrics = false` on Apple platforms). See the [platform-specific metrics docs](/product/metrics/getting-started/) for the option name on your SDK. ### Application Metrics Filtering diff --git a/docs/pricing/quotas/manage-continuous-profile-hours.mdx b/docs/pricing/quotas/manage-continuous-profile-hours.mdx index 36b9fd9d558039..61f82497e78317 100644 --- a/docs/pricing/quotas/manage-continuous-profile-hours.mdx +++ b/docs/pricing/quotas/manage-continuous-profile-hours.mdx @@ -56,6 +56,6 @@ Continuous profiling provides two "lifecycle" modes that can be used to control - If you're using the `manual` profile lifecycle mode, add calls to `start_profile_session` and `stop_profile_session` - If you're using the `trace` profile lifecycle mode, ensure that `traces_sample_rate` or `traces_sampler` are configured appropriately in addition to `profile_session_sample_rate` -See the detailed [migration guide](/product/explore/profiling/continuous-ui-profiling-migration-guide/) for more information. +See the detailed [migration guide](/product/profiling/continuous-ui-profiling-migration-guide/) for more information. diff --git a/docs/pricing/quotas/manage-logs-quota.mdx b/docs/pricing/quotas/manage-logs-quota.mdx index cee4152d09f7f6..e5522fbb6c281d 100644 --- a/docs/pricing/quotas/manage-logs-quota.mdx +++ b/docs/pricing/quotas/manage-logs-quota.mdx @@ -8,7 +8,7 @@ og_image: /og-images/pricing-quotas-manage-logs-quota.png --- -[Logs](/product/explore/logs/) is currently available on Team, Business, and Developer plans. These plans include a certain amount of Logs data to be processed and stored. Once you exceed your included quota, you'll be charged based on your pay-as-you-go (PAYG) budget. +[Logs](/product/logs/) is currently available on Team, Business, and Developer plans. These plans include a certain amount of Logs data to be processed and stored. Once you exceed your included quota, you'll be charged based on your pay-as-you-go (PAYG) budget. ## Key Terms diff --git a/docs/pricing/quotas/manage-ui-profile-hours.mdx b/docs/pricing/quotas/manage-ui-profile-hours.mdx index fd83c9714b1699..f5a754702c80f4 100644 --- a/docs/pricing/quotas/manage-ui-profile-hours.mdx +++ b/docs/pricing/quotas/manage-ui-profile-hours.mdx @@ -62,5 +62,5 @@ To estimate monthly usage for UI Profiling in the browser, the calculation is ** - If you're using the `manual` profile lifecycle mode, add calls to `start_profile_session` and `stop_profile_session` - If you're using the `trace` profile lifecycle mode, ensure that `traces_sample_rate` or `traces_sampler` are configured appropriately in addition to `profile_session_sample_rate` -See the detailed [migration guide](/product/explore/profiling/continuous-ui-profiling-migration-guide/) for more information. +See the detailed [migration guide](/product/profiling/continuous-ui-profiling-migration-guide/) for more information. diff --git a/docs/product/ai-in-sentry/index.mdx b/docs/product/ai-in-sentry/index.mdx index d9bfcffba48a0c..8442d9354570a4 100644 --- a/docs/product/ai-in-sentry/index.mdx +++ b/docs/product/ai-in-sentry/index.mdx @@ -1,6 +1,7 @@ --- title: AI in Sentry -sidebar_order: 25 +sidebar_order: 400 +sidebar_section: automate description: "Learn about Sentry's AI-powered features that help you analyze and debug your code faster." keywords: - Seer @@ -40,7 +41,7 @@ that traditional detectors can't catch. ### AI Summaries -See a summary of [User Feedback](/product/user-feedback/) and [Session Replays](/product/explore/session-replay/) to identify common issues and patterns. +See a summary of [User Feedback](/product/user-feedback/) and [Session Replays](/product/session-replay/) to identify common issues and patterns. ## Privacy and security diff --git a/docs/product/ai-in-sentry/seer/autofix/index.mdx b/docs/product/ai-in-sentry/seer/autofix/index.mdx index 479254e914f6d9..910f65848387f5 100644 --- a/docs/product/ai-in-sentry/seer/autofix/index.mdx +++ b/docs/product/ai-in-sentry/seer/autofix/index.mdx @@ -143,7 +143,7 @@ Seer handles access to a wide variety of data sources and tools. While debugging - **Issue details**: Error messages, stack traces, and event metadata from your [Issues](/product/issues/) - **Tracing data**: Distributed [traces](/concepts/key-terms/tracing/#whats-a-trace) and span information -- **Logs**: Structured [Logs](/product/explore/logs/) from your application (beta) +- **Logs**: Structured [Logs](/product/logs/) from your application (beta) - **Your codebases**: Relevant code from linked GitHub or GitLab repositories, with support for multiple repos for distributed services - **Performance data**: Profiles and performance metrics - **Interactive feedback**: Your input and guidance during the process diff --git a/docs/product/ai-in-sentry/seer/index.mdx b/docs/product/ai-in-sentry/seer/index.mdx index 1c1fd42c347def..861ebdb8bc9d30 100644 --- a/docs/product/ai-in-sentry/seer/index.mdx +++ b/docs/product/ai-in-sentry/seer/index.mdx @@ -99,7 +99,7 @@ Seer is a powerful debugging agent, with access to a wide variety of data source - **Issue Context**: Error messages, stack traces, and event metadata from your [Issues](/product/issues/) - **Tracing Data**: Distributed [traces](/concepts/key-terms/tracing/#whats-a-trace) and span information -- **Logs**: Structured [Logs](/product/explore/logs/) from your application (beta) +- **Logs**: Structured [Logs](/product/logs/) from your application (beta) - **Your Codebase**: Relevant code from linked GitHub or GitLab repositories, with support for multiple repos for distributed services - **Performance Data**: Profiles and performance metrics - **Interactive Feedback**: Your input and guidance during the process diff --git a/docs/product/build-distribution/index.mdx b/docs/product/build-distribution/index.mdx index 9a19df45489b4b..73671f7fd51cf9 100644 --- a/docs/product/build-distribution/index.mdx +++ b/docs/product/build-distribution/index.mdx @@ -1,6 +1,7 @@ --- title: Build Distribution -sidebar_order: 137 +sidebar_order: 320 +sidebar_section: measure description: Distribute app builds to internal teams and beta testers. beta: true --- diff --git a/docs/product/dashboards/index.mdx b/docs/product/dashboards/index.mdx index 3578436137c636..d979f919b0c1f3 100644 --- a/docs/product/dashboards/index.mdx +++ b/docs/product/dashboards/index.mdx @@ -1,6 +1,7 @@ --- title: Dashboards -sidebar_order: 45 +sidebar_order: 300 +sidebar_section: measure description: >- Learn how Sentry’s Dashboards give you a focused view of your application’s health, across multiple projects. @@ -38,7 +39,7 @@ You can make [custom dashboards](/product/dashboards/custom-dashboards/) by dupl ## Open Dashboard Widgets in Discover and Issues -Each dashboard [widget](/product/dashboards/widget-builder/) has an ellipsis that opens a context menu. From here, depending on the type of data the widget shows, you can open the widget in [Discover](/product/explore/discover-queries/) or [Issues](/product/issues/) to get more information. +Each dashboard [widget](/product/dashboards/widget-builder/) has an ellipsis that opens a context menu. From here, depending on the type of data the widget shows, you can open the widget in [Discover](/product/discover-queries/) or [Issues](/product/issues/) to get more information. ## Widget Viewer diff --git a/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/index.mdx b/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/index.mdx index e3d6b405e5f31f..a5c4c74fa4ad3f 100644 --- a/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/index.mdx +++ b/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/index.mdx @@ -28,7 +28,7 @@ The **Web Vitals** page only displays data from your application's initial page ## Page Summary -From the table in **Web Vitals** or a Web Vital Summary panel, click on a page to open its **Page Summary**. Here, you can see a summary of that single page's Web Vitals. In **Page Summary**, you can further drill down to a specific page load sample [Trace](/concepts/key-terms/tracing/#whats-a-trace), [LCP Element](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp), [Replay](/product/explore/session-replay/), or [Profile](/product/explore/profiling/). The page's Performance Score is represented in a circular graph broken down by metric, as well as a "Page Loads" chart. +From the table in **Web Vitals** or a Web Vital Summary panel, click on a page to open its **Page Summary**. Here, you can see a summary of that single page's Web Vitals. In **Page Summary**, you can further drill down to a specific page load sample [Trace](/concepts/key-terms/tracing/#whats-a-trace), [LCP Element](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp), [Replay](/product/session-replay/), or [Profile](/product/profiling/). The page's Performance Score is represented in a circular graph broken down by metric, as well as a "Page Loads" chart. ### Samples List diff --git a/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts.mdx b/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts.mdx index 11cb6f570ea7ea..c894cf0f9a6bc9 100644 --- a/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts.mdx +++ b/docs/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts.mdx @@ -62,7 +62,7 @@ First Paint (FP) measures the amount of time the first pixel takes to appear in ### First Input Delay (FID) -As of March 12, 2024, First Input Delay (FID) was replaced as a Core Web Vital by INP. While Sentry no longer includes FID in our performance score calculations nor on the **Web Vitals** performance page, we continue to collect FID metrics. You can query FID measurements in [Discover](/product/explore/discover-queries/). +As of March 12, 2024, First Input Delay (FID) was replaced as a Core Web Vital by INP. While Sentry no longer includes FID in our performance score calculations nor on the **Web Vitals** performance page, we continue to collect FID metrics. You can query FID measurements in [Discover](/product/discover-queries/). [First Input Delay (FID)](https://web.dev/fid/) measures response time when a user tries to interact with the viewport by clicking a button, link, or any other custom JavaScript controller. FID data is critical for understanding whether interactions on an application page are successful or not. diff --git a/docs/product/dashboards/sentry-dashboards/index.mdx b/docs/product/dashboards/sentry-dashboards/index.mdx index 8b9d638613c687..245bdc464e83f4 100644 --- a/docs/product/dashboards/sentry-dashboards/index.mdx +++ b/docs/product/dashboards/sentry-dashboards/index.mdx @@ -8,7 +8,7 @@ og_image: /og-images/product-insights-overview.png Spot trends, fix issues, and boost application performance with Sentry's frontend, backend, mobile, and AI performance dashboards in [**Sentry Dashboards**](https://sentry.io/orgredirect/organizations/:orgslug/dashboards/). Get a summary of the telemetry and events impacting the performance of your application, like web vitals, crash rate, session health, and outbound API requests. You can also use it to drill deeper into specific workflows and review traces, errors, and releases. -Sentry Dashboards use [tracing data](/concepts/key-terms/tracing/). By enabling tracing, Sentry tracks application performance, measuring metrics like throughput and latency, displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of multiple [spans](/product/explore/trace-explorer/#spans) to measure individual services and operations within those services. +Sentry Dashboards use [tracing data](/concepts/key-terms/tracing/). By enabling tracing, Sentry tracks application performance, measuring metrics like throughput and latency, displaying the impact of errors across multiple services. Sentry captures [distributed traces](/product/sentry-basics/tracing/distributed-tracing/) consisting of multiple [spans](/product/trace-explorer/#spans) to measure individual services and operations within those services. Haven't set it up yet? Use the SDK to [set up tracing for your platform](/platform-redirect/?next=%2Ftracing%2F). diff --git a/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/screen-loads.mdx b/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/screen-loads.mdx index a5259bf9a396bb..2acba365cf650d 100644 --- a/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/screen-loads.mdx +++ b/docs/product/dashboards/sentry-dashboards/mobile/mobile-vitals/screen-loads.mdx @@ -80,4 +80,4 @@ If spans end before TTID or TTFD, there's a chance they could be affecting their Clicking on a span description takes you to the Traces page, where you can see a list of related sampled spans. -Once on a trace view, you can click over to **Profiles** to investigate [flamegraphs](/product/explore/profiling/flame-charts-graphs/) for the span to see where the most time is being spent. \ No newline at end of file +Once on a trace view, you can click over to **Profiles** to investigate [flamegraphs](/product/profiling/flame-charts-graphs/) for the span to see where the most time is being spent. \ No newline at end of file diff --git a/docs/product/dashboards/sentry-dashboards/transaction-summary.mdx b/docs/product/dashboards/sentry-dashboards/transaction-summary.mdx index 4f00e8c42651ce..e12c7442134be3 100644 --- a/docs/product/dashboards/sentry-dashboards/transaction-summary.mdx +++ b/docs/product/dashboards/sentry-dashboards/transaction-summary.mdx @@ -57,7 +57,7 @@ On initial load, the table displays slow occurrences of the transaction along wi The table also updates dynamically if you change any of the project, environment, or date range filters or when you drill in on a latency segment (applicable when viewing the Latency Histogram). -When viewing transactions, you may want to create more curated views. Click "Open in Discover" above the table to create a custom query to investigate further. For more details, see the full documentation for the Discover [Query Builder](/product/explore/discover-queries/query-builder/). +When viewing transactions, you may want to create more curated views. Click "Open in Discover" above the table to create a custom query to investigate further. For more details, see the full documentation for the Discover [Query Builder](/product/discover-queries/query-builder/). @@ -147,7 +147,7 @@ Spans with the same operation and description are grouped together into a single ### Replays -The Replays tab displays a list of replays where the transaction you're viewing had occurred. Go directly to [Replay Details](/product/explore/session-replay/web/replay-details/) for any replay and see how a slow transaction impacted the user experience. Note: you must have [Session Replay](/product/explore/session-replay/) enabled to see this tab. +The Replays tab displays a list of replays where the transaction you're viewing had occurred. Go directly to [Replay Details](/product/session-replay/web/replay-details/) for any replay and see how a slow transaction impacted the user experience. Note: you must have [Session Replay](/product/session-replay/) enabled to see this tab. ## Additional Actions diff --git a/docs/product/dashboards/widget-builder/index.mdx b/docs/product/dashboards/widget-builder/index.mdx index 6346bfa2323743..7c326403980720 100644 --- a/docs/product/dashboards/widget-builder/index.mdx +++ b/docs/product/dashboards/widget-builder/index.mdx @@ -18,7 +18,7 @@ Some of these options are standard and displayed for all widgets, but others are In the dataset selection step, choose which type of data you would like to use in your widget. Available datasets include: [errors](#errors), [spans](#spans), [transactions](#transactions), [logs](#logs), [issues](#issues), and [releases](#releases). ### Errors -Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example: +Choosing "Errors" allows you to query and aggregate error events in the same way you would for a [Discover Query](/product/discover-queries/). This data is comprised of errors that occur in your application, which Sentry will use to group into issues, for example: - Users most affected by errors @@ -30,11 +30,11 @@ Choosing "Spans" allows you to query and aggregate individual operations within - Average duration of API calls grouped by endpoint - P90 latency of specific operations in your application -You can create span-based widgets directly from [Trace Explorer](/product/explore/trace-explorer/) queries using the "Save As" button. +You can create span-based widgets directly from [Trace Explorer](/product/trace-explorer/) queries using the "Save As" button. ### Transactions -Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/explore/discover-queries/). This data is comprised of events that track the performance of operations in your application. Some widget examples include: +Choosing "Transactions" allows you to query and aggregate transaction events in the same way you would for a [Discover Query](/product/discover-queries/). This data is comprised of events that track the performance of operations in your application. Some widget examples include: - Tracking performance of an endpoint - Throughput by country @@ -47,7 +47,7 @@ Choosing "Logs" allows you to query and aggregate structured log data from your - Logs filtered by severity level or custom attributes - Trends in application state or business events -You can create log-based widgets from [Logs Explorer](/product/explore/logs/) queries. +You can create log-based widgets from [Logs Explorer](/product/logs/) queries. ### Issues @@ -96,11 +96,11 @@ This visualization is useful when you want to compare values across different ca ### Table -Table charts display the results of a [Discover Query](/product/explore/discover-queries/). This visualization is well suited to showing key fields and related aggregates. For example “duration percentiles for the most frequently visited transaction names”. You can also choose to display [issues](/product/issues/) data in a table visualization using the [dataset selector](/product/dashboards/widget-builder/#choose-your-dataset). +Table charts display the results of a [Discover Query](/product/discover-queries/). This visualization is well suited to showing key fields and related aggregates. For example “duration percentiles for the most frequently visited transaction names”. You can also choose to display [issues](/product/issues/) data in a table visualization using the [dataset selector](/product/dashboards/widget-builder/#choose-your-dataset). ### Big Number -A big number visualization displays the current value of a single function or [equation](/product/explore/discover-queries/query-builder/query-equations/). This visualization is well suited for high-level aggregates. An example scenario would be “p95 of all transactions”. +A big number visualization displays the current value of a single function or [equation](/product/discover-queries/query-builder/query-equations/). This visualization is well suited for high-level aggregates. An example scenario would be “p95 of all transactions”. ### Markdown @@ -120,9 +120,9 @@ For example, if you filter for a specific database query using `span.op:db`, the The option to set columns is only available for [table visualizations](/product/dashboards/widget-builder/#table). -By default, the first column is already configured for you, but you can update it. To add more columns, which stacks events, add [functions](/product/explore/discover-queries/query-builder/#stacking-functions) (`f(x)`) that can take in parameters. [Field and tag columns](/concepts/search/searchable-properties/#event-properties) will help you view more details about the events (for example, `title` to see the description of an issue or `users` to see how many users it's affecting). +By default, the first column is already configured for you, but you can update it. To add more columns, which stacks events, add [functions](/product/discover-queries/query-builder/#stacking-functions) (`f(x)`) that can take in parameters. [Field and tag columns](/concepts/search/searchable-properties/#event-properties) will help you view more details about the events (for example, `title` to see the description of an issue or `users` to see how many users it's affecting). -You can also add equations to your query using the table columns as equation variables, and the results will be displayed in the query results table. Learn more in [Adding Query Equations](/product/explore/discover-queries/query-builder/query-equations/). +You can also add equations to your query using the table columns as equation variables, and the results will be displayed in the query results table. Learn more in [Adding Query Equations](/product/discover-queries/query-builder/query-equations/). Next to each column and equation, you have the option to set an alias that will replace the column name in the table header. diff --git a/docs/product/explore/discover-queries/img/001.png b/docs/product/discover-queries/img/001.png similarity index 100% rename from docs/product/explore/discover-queries/img/001.png rename to docs/product/discover-queries/img/001.png diff --git a/docs/product/explore/discover-queries/img/002.png b/docs/product/discover-queries/img/002.png similarity index 100% rename from docs/product/explore/discover-queries/img/002.png rename to docs/product/discover-queries/img/002.png diff --git a/docs/product/explore/discover-queries/img/003.png b/docs/product/discover-queries/img/003.png similarity index 100% rename from docs/product/explore/discover-queries/img/003.png rename to docs/product/discover-queries/img/003.png diff --git a/docs/product/explore/discover-queries/img/004.png b/docs/product/discover-queries/img/004.png similarity index 100% rename from docs/product/explore/discover-queries/img/004.png rename to docs/product/discover-queries/img/004.png diff --git a/docs/product/explore/discover-queries/img/005.png b/docs/product/discover-queries/img/005.png similarity index 100% rename from docs/product/explore/discover-queries/img/005.png rename to docs/product/discover-queries/img/005.png diff --git a/docs/product/explore/discover-queries/img/006.png b/docs/product/discover-queries/img/006.png similarity index 100% rename from docs/product/explore/discover-queries/img/006.png rename to docs/product/discover-queries/img/006.png diff --git a/docs/product/explore/discover-queries/img/007.png b/docs/product/discover-queries/img/007.png similarity index 100% rename from docs/product/explore/discover-queries/img/007.png rename to docs/product/discover-queries/img/007.png diff --git a/docs/product/explore/discover-queries/img/008.png b/docs/product/discover-queries/img/008.png similarity index 100% rename from docs/product/explore/discover-queries/img/008.png rename to docs/product/discover-queries/img/008.png diff --git a/docs/product/explore/discover-queries/img/009.png b/docs/product/discover-queries/img/009.png similarity index 100% rename from docs/product/explore/discover-queries/img/009.png rename to docs/product/discover-queries/img/009.png diff --git a/docs/product/explore/discover-queries/img/010.png b/docs/product/discover-queries/img/010.png similarity index 100% rename from docs/product/explore/discover-queries/img/010.png rename to docs/product/discover-queries/img/010.png diff --git a/docs/product/explore/discover-queries/img/012.png b/docs/product/discover-queries/img/012.png similarity index 100% rename from docs/product/explore/discover-queries/img/012.png rename to docs/product/discover-queries/img/012.png diff --git a/docs/product/explore/discover-queries/img/013.png b/docs/product/discover-queries/img/013.png similarity index 100% rename from docs/product/explore/discover-queries/img/013.png rename to docs/product/discover-queries/img/013.png diff --git a/docs/product/explore/discover-queries/img/014.png b/docs/product/discover-queries/img/014.png similarity index 100% rename from docs/product/explore/discover-queries/img/014.png rename to docs/product/discover-queries/img/014.png diff --git a/docs/product/explore/discover-queries/img/discover-event-details.png b/docs/product/discover-queries/img/discover-event-details.png similarity index 100% rename from docs/product/explore/discover-queries/img/discover-event-details.png rename to docs/product/discover-queries/img/discover-event-details.png diff --git a/docs/product/explore/discover-queries/img/discover-facet-map.png b/docs/product/discover-queries/img/discover-facet-map.png similarity index 100% rename from docs/product/explore/discover-queries/img/discover-facet-map.png rename to docs/product/discover-queries/img/discover-facet-map.png diff --git a/docs/product/explore/discover-queries/img/discover-homepage.png b/docs/product/discover-queries/img/discover-homepage.png similarity index 100% rename from docs/product/explore/discover-queries/img/discover-homepage.png rename to docs/product/discover-queries/img/discover-homepage.png diff --git a/docs/product/explore/discover-queries/img/discover-results.png b/docs/product/discover-queries/img/discover-results.png similarity index 100% rename from docs/product/explore/discover-queries/img/discover-results.png rename to docs/product/discover-queries/img/discover-results.png diff --git a/docs/product/explore/discover-queries/img/discover-table-cell.png b/docs/product/discover-queries/img/discover-table-cell.png similarity index 100% rename from docs/product/explore/discover-queries/img/discover-table-cell.png rename to docs/product/discover-queries/img/discover-table-cell.png diff --git a/docs/product/explore/discover-queries/img/trace-details-view.png b/docs/product/discover-queries/img/trace-details-view.png similarity index 100% rename from docs/product/explore/discover-queries/img/trace-details-view.png rename to docs/product/discover-queries/img/trace-details-view.png diff --git a/docs/product/explore/discover-queries/index.mdx b/docs/product/discover-queries/index.mdx similarity index 98% rename from docs/product/explore/discover-queries/index.mdx rename to docs/product/discover-queries/index.mdx index 53e29ee8f3d0a7..6894d272a6a90c 100644 --- a/docs/product/explore/discover-queries/index.mdx +++ b/docs/product/discover-queries/index.mdx @@ -1,6 +1,7 @@ --- title: Discover -sidebar_order: 90 +sidebar_order: 260 +sidebar_section: debug description: >- Discover is a powerful query engine that allows you to query all your metadata across projects and environments to unlock insights. @@ -41,7 +42,7 @@ From the **Discover** page, you can build a " | sha1sum -c - On the **Discover** page, each saved query card has an ellipsis that will open a context menu. Delete the query from here. You can also delete the query within Query Results view by clicking the trash can in the upper right. -For more details on how to view saved queries, see the [full documentation on Discover](/product/explore/discover-queries/) +For more details on how to view saved queries, see the [full documentation on Discover](/product/discover-queries/) diff --git a/docs/product/explore/discover-queries/query-builder/img/add_equation.gif b/docs/product/discover-queries/query-builder/img/add_equation.gif similarity index 100% rename from docs/product/explore/discover-queries/query-builder/img/add_equation.gif rename to docs/product/discover-queries/query-builder/img/add_equation.gif diff --git a/docs/product/explore/discover-queries/query-builder/query-equations.mdx b/docs/product/discover-queries/query-builder/query-equations.mdx similarity index 100% rename from docs/product/explore/discover-queries/query-builder/query-equations.mdx rename to docs/product/discover-queries/query-builder/query-equations.mdx diff --git a/docs/product/explore/discover-queries/standard-fields.json b/docs/product/discover-queries/standard-fields.json similarity index 100% rename from docs/product/explore/discover-queries/standard-fields.json rename to docs/product/discover-queries/standard-fields.json diff --git a/docs/product/explore/discover-queries/uncover-trends.mdx b/docs/product/discover-queries/uncover-trends.mdx similarity index 100% rename from docs/product/explore/discover-queries/uncover-trends.mdx rename to docs/product/discover-queries/uncover-trends.mdx diff --git a/docs/product/drains/index.mdx b/docs/product/drains/index.mdx index 6c11002c657deb..a837acc31606f4 100644 --- a/docs/product/drains/index.mdx +++ b/docs/product/drains/index.mdx @@ -1,10 +1,11 @@ --- title: Log and Trace Drains -sidebar_order: 75 +sidebar_order: 250 +sidebar_section: debug description: Learn how to set up log and trace drains to send logs and traces to Sentry from managed hosting platforms. --- -Log and trace drains connect your hosting platform's native telemetry system directly to Sentry, letting you send [logs](/product/explore/logs/) and [traces](/product/explore/trace-explorer/) without modifying your application code. +Log and trace drains connect your hosting platform's native telemetry system directly to Sentry, letting you send [logs](/product/logs/) and [traces](/product/trace-explorer/) without modifying your application code. @@ -33,5 +34,5 @@ Log and trace drains support logs and traces only: ## Learn More - [OpenTelemetry Protocol (OTLP)](/concepts/otlp/): Send OTLP data to Sentry via SDK, OpenTelemetry Collector, Vector, or Fluent Bit -- [Logs](/product/explore/logs/): View, search, and analyze logs in Sentry -- [Trace Explorer](/product/explore/trace-explorer/): View, search, and analyze traces in Sentry +- [Logs](/product/logs/): View, search, and analyze logs in Sentry +- [Trace Explorer](/product/trace-explorer/): View, search, and analyze traces in Sentry diff --git a/docs/product/drains/openrouter.mdx b/docs/product/drains/openrouter.mdx index 916ae717154140..f99ffa0a812862 100644 --- a/docs/product/drains/openrouter.mdx +++ b/docs/product/drains/openrouter.mdx @@ -55,4 +55,4 @@ ___DSN___ ## Step 5: Verify traces in Sentry -Make an API request through OpenRouter and view the trace in Sentry's [Trace Explorer](/product/explore/trace-explorer/). It may take a few minutes for traces to appear. +Make an API request through OpenRouter and view the trace in Sentry's [Trace Explorer](/product/trace-explorer/). It may take a few minutes for traces to appear. diff --git a/docs/product/drains/vercel.mdx b/docs/product/drains/vercel.mdx index 78d24bf99c1565..5d7d6e84a81782 100644 --- a/docs/product/drains/vercel.mdx +++ b/docs/product/drains/vercel.mdx @@ -92,7 +92,7 @@ x-sentry-auth: sentry sentry_key=___PUBLIC_KEY___ -Sending [Application Metrics](/product/explore/metrics/) via Vercel Metric Drains (Speed Insights, Web Analytics) isn't currently supported. If you're interested in this support please reach out on [GitHub](https://github.com/getsentry/sentry/issues/103488). +Sending [Application Metrics](/product/metrics/) via Vercel Metric Drains (Speed Insights, Web Analytics) isn't currently supported. If you're interested in this support please reach out on [GitHub](https://github.com/getsentry/sentry/issues/103488). diff --git a/docs/product/explore/index.mdx b/docs/product/explore/index.mdx deleted file mode 100644 index 19f8e3eb87dac7..00000000000000 --- a/docs/product/explore/index.mdx +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: Explore -sidebar_order: 40 -description: Learn about the different ways you can explore your data in Sentry. ---- - -The Explore tab in Sentry offers multiple ways to search and investigate your application's data. You can look at your app's traces, application metrics, profiles, logs, and replays to get the information you need to debug issues more quickly and easily. - -## Learn More - - diff --git a/docs/product/index.mdx b/docs/product/index.mdx index 31b8c796aea049..b1cc8e4bc94d0d 100644 --- a/docs/product/index.mdx +++ b/docs/product/index.mdx @@ -18,7 +18,7 @@ Sentry's error monitoring capabilities make it possible to quickly get to the ro Sentry automatically captures unhandled exceptions (errors). It then groups similar errors into [issues](/product/issues/), making it possible to triage and manage them more efficiently. -- If you're monitoring a web project, you can [**replay**](/product/explore/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/integrate-frontend/upload-source-maps/). +- If you're monitoring a web project, you can [**replay**](/product/session-replay/) what the user experienced on your app and connect that error to the problematic line of code with [**source maps**](/product/sentry-basics/integrate-frontend/upload-source-maps/). - If you set up Sentry for both your frontend and backend, you'll be able to use [**distributed tracing**](/product/sentry-basics/concepts/tracing/distributed-tracing/) to see the sequence of events (both frontend and backend) that led up to the event of interest. - Additionally, you can set up [**integrations**](/integrations/source-code-mgmt/) to link your source code so that Sentry can surface [**suspect commits**](/product/issues/suspect-commits/) and [**stack traces**](/integrations/source-code-mgmt/github/#stack-trace-linking) to show the problematic line of code, as well as [**suggest assignees**](/integrations/source-code-mgmt/github/#suspect-commits-and-suggested-assignees) for issues based on commit authors. @@ -26,7 +26,7 @@ Sentry automatically captures unhandled exceptions (errors). It then groups simi Tracing gives you a full view of what's happening in your application from the frontend to the backend and between systems, by looking at interactions between various components of your stack. This is especially useful if you rely on microservices or are trying to find the root cause of a difficult user complaint. With [distributed tracing](/concepts/key-terms/tracing/distributed-tracing/), you can quickly identify performance bottlenecks. -You can also get full context about what was happening when an error or performance issue occurred by looking at the [Trace View](/concepts/key-terms/tracing/trace-view/) page. This will allow you to among other things, trace slow-loading pages all the way back to poor-performing API calls. Lastly, you can use the [Trace Explorer](/product/explore/traces/) page to search span data, including conditions relating to the structure of the trace itself. +You can also get full context about what was happening when an error or performance issue occurred by looking at the [Trace View](/concepts/key-terms/tracing/trace-view/) page. This will allow you to among other things, trace slow-loading pages all the way back to poor-performing API calls. Lastly, you can use the [Trace Explorer](/product/trace-explorer/) page to search span data, including conditions relating to the structure of the trace itself. ### Profiling @@ -40,7 +40,7 @@ Our performance monitoring feature helps you track application performance, meas ### Application Metrics -Sentry's [**Application Metrics**](/product/explore/metrics/) let you send counters, gauges, and distributions from your code to track application health signals like `email.sent`, `checkout.failed`, or `queue.depth`. Every metric event is trace-connected, so when something looks off you can click from an aggregate straight into the related traces, spans, logs, and errors that produced it — turning "metric spike → guesswork" into a single debugging flow. You can also turn any metric query into a [Monitor](/product/monitors-and-alerts/monitors/) or add it to a [Dashboard](/product/dashboards/). +Sentry's [**Application Metrics**](/product/metrics/) let you send counters, gauges, and distributions from your code to track application health signals like `email.sent`, `checkout.failed`, or `queue.depth`. Every metric event is trace-connected, so when something looks off you can click from an aggregate straight into the related traces, spans, logs, and errors that produced it — turning "metric spike → guesswork" into a single debugging flow. You can also turn any metric query into a [Monitor](/product/monitors-and-alerts/monitors/) or add it to a [Dashboard](/product/dashboards/). ### Release Health Monitoring @@ -62,7 +62,7 @@ Sentry's [**Uptime Monitoring**](/product/monitors-and-alerts/monitors/uptime-mo ### Visibility Into Your Data Across Environments -[**Discover**](/product/explore/discover-queries/) provides visibility into your data across environments by building upon and enriching your error data. You can [**query**](/product/explore/discover-queries/query-builder/) and unlock insights into the health of your entire system and get answers to critical business questions — all in one place. You can also build your own [**dashboards**](/product/dashboards/) to help you monitor what's most important for your app. +[**Discover**](/product/discover-queries/) provides visibility into your data across environments by building upon and enriching your error data. You can [**query**](/product/discover-queries/query-builder/) and unlock insights into the health of your entire system and get answers to critical business questions — all in one place. You can also build your own [**dashboards**](/product/dashboards/) to help you monitor what's most important for your app. ### Seamless Developer Workflow diff --git a/docs/product/issues/index.mdx b/docs/product/issues/index.mdx index edc620d033a126..a59c0c8f1b1299 100644 --- a/docs/product/issues/index.mdx +++ b/docs/product/issues/index.mdx @@ -1,6 +1,7 @@ --- title: Issues -sidebar_order: 20 +sidebar_order: 100 +sidebar_section: detect description: >- Learn how to use Sentry’s Issues page, where you can see and start to debug errors and performance problems that are affecting your application. diff --git a/docs/product/issues/issue-details/breadcrumbs/index.mdx b/docs/product/issues/issue-details/breadcrumbs/index.mdx index 446945a2194be5..b9330b16f5406b 100644 --- a/docs/product/issues/issue-details/breadcrumbs/index.mdx +++ b/docs/product/issues/issue-details/breadcrumbs/index.mdx @@ -7,7 +7,7 @@ og_image: /og-images/product-issues-issue-details-breadcrumbs.png -Manual breadcrumbs had a good run, but [Sentry's got logs](/product/explore/logs/). Structured, searchable, and way easier to alert or query on. Check them out! +Manual breadcrumbs had a good run, but [Sentry's got logs](/product/logs/). Structured, searchable, and way easier to alert or query on. Check them out! diff --git a/docs/product/issues/issue-details/index.mdx b/docs/product/issues/issue-details/index.mdx index af13b9a15b1aa1..cd75896edec2db 100644 --- a/docs/product/issues/issue-details/index.mdx +++ b/docs/product/issues/issue-details/index.mdx @@ -57,7 +57,7 @@ Similar and merged issues allow you to learn more about and control [grouped iss In addition to events, information about replays, attachments, and feedback can be found from the page. -- **Replays** – A list of [replays](/product/explore/session-replay/) tied to error events included in the issue. +- **Replays** – A list of [replays](/product/session-replay/) tied to error events included in the issue. - **User Feedback** - Any feedback collected from users through the SDK's user feedback. - **Attachments** - Any additional files stored, such as config, log, or screenshot files that are related to the error event. @@ -125,7 +125,7 @@ Sometimes the trace will be supplemented by a Trace-related Issue. A Trace-relat ### Session Replay -If you’ve enabled [Session Replay](/product/explore/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/explore/session-replay/getting-started#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/explore/session-replay/web/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/getting-started#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/web/replay-details/) page. ### HTTP Request @@ -187,13 +187,13 @@ Feature flag change tracking and feature flag evaluation tracking is currently i -Enabling one or more of our [evaluation tracking integrations](/product/explore/feature-flags/#evaluation-tracking) will reveal the feature flag evaluation table. Here you can see an ordered list (in order of evaluation) of all the flags evaluated and their evaluation results prior to the error event. +Enabling one or more of our [evaluation tracking integrations](/product/issues/issue-details/feature-flags/#evaluation-tracking) will reveal the feature flag evaluation table. Here you can see an ordered list (in order of evaluation) of all the flags evaluated and their evaluation results prior to the error event. ![Feature Flag Table](./img/ff-table.png) Setting up evaluation tracking also allows you to use Issues Search in conjunction with feature flags. On Issues Search, using the `flags` keyword will allow you to filter for issues containing errors where the feature flag evaluated value is true or false. This allows you to quickly find all errors where a specific flag evaluation and its value of interest are present. See [searchable properties](/concepts/search/searchable-properties/issues/#flags) for more details about the search syntax. -Enabling both [change tracking](/product/explore/feature-flags/#change-tracking) and evaluation tracking integrations adds feature flag change annotations to the event volume chart and unlocks suspect feature flag detection. Feature flag change annotations help you identify regressions caused by updates to a feature flag’s definition. An annotation will only appear for flags that were evaluated before the error event occurred. +Enabling both [change tracking](/product/issues/issue-details/feature-flags/#change-tracking) and evaluation tracking integrations adds feature flag change annotations to the event volume chart and unlocks suspect feature flag detection. Feature flag change annotations help you identify regressions caused by updates to a feature flag’s definition. An annotation will only appear for flags that were evaluated before the error event occurred. ![Feature Flag Release Chart](./img/ff-release.png) diff --git a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx index 7fddabc7a69399..0570cb7fd541b4 100644 --- a/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/frame-drop/index.mdx @@ -13,7 +13,7 @@ We can detect some specific causes for a main thread stall, like decoding [image ## Detection Criteria -[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Frame Drop issues. Once set up, Sentry will look for profiles that record a frozen UI frame and then search for the most time-consuming application function call delaying the display link's next vsync. In a run of functions calling through without any self-time, the deepest call will be chosen. +[Profiling](/product/profiling/) must be enabled for Sentry to detect Frame Drop issues. Once set up, Sentry will look for profiles that record a frozen UI frame and then search for the most time-consuming application function call delaying the display link's next vsync. In a run of functions calling through without any self-time, the deepest call will be chosen. 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 e27998d8ec7ba8..3c694afbbb2c85 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/explore/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/image-decoding-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx index 7bf0f853c3f793..0d778f9f6d04c5 100644 --- a/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/image-decoding-main-thread/index.mdx @@ -14,7 +14,7 @@ The process of decoding a compressed JPEG or PNG image into a bitmap (especially ## Detection Criteria -[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Decoding on Main Thread issues. Sentry looks for functions related to image-decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/profiling/) must be enabled for Sentry to detect Decoding on Main Thread issues. Sentry looks for functions related to image-decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx index 858fe95c2b69da..67ef71b1c97cb3 100644 --- a/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/json-decoding-main-thread/index.mdx @@ -16,7 +16,7 @@ Decoding a JSON blob into a data structure can be a long running operation, espe ## Detection Criteria -[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect JSON Decoding on Main Thread issues. Sentry looks for functions related to JSON decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/profiling/) must be enabled for Sentry to detect JSON Decoding on Main Thread issues. Sentry looks for functions related to JSON decoding that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx b/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx index 815b1583fd9f8f..0f3bc3964ffcaa 100644 --- a/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx +++ b/docs/product/issues/issue-details/performance-issues/regex-main-thread/index.mdx @@ -12,7 +12,7 @@ Evaluating matches between strings and regular expressions (regex) can be long-r ## Detection Criteria -[Profiling](/product/explore/profiling/) must be enabled for Sentry to detect Regex on Main Thread issues. Sentry looks for functions related to regular expressions that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. +[Profiling](/product/profiling/) must be enabled for Sentry to detect Regex on Main Thread issues. Sentry looks for functions related to regular expressions that have been running on the main thread for at least 40ms. This threshold ensures the function appears in a sufficient number of samples collected by the profile (~10ms per sample x 4 = ~40ms total) before it gets detected as an issue. ## Function Evidence diff --git a/docs/product/issues/issue-details/replay-issues/index.mdx b/docs/product/issues/issue-details/replay-issues/index.mdx index 6edd302dd8ef96..3daf1f2d48e290 100644 --- a/docs/product/issues/issue-details/replay-issues/index.mdx +++ b/docs/product/issues/issue-details/replay-issues/index.mdx @@ -4,7 +4,7 @@ sidebar_order: 30 description: "Learn more about which replay issues Sentry detects." --- -If you've enabled [Session Replay](/product/explore/session-replay/), you'll be able to see new issue types on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. +If you've enabled [Session Replay](/product/session-replay/), you'll be able to see new issue types on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. ## Quota Consumption diff --git a/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx b/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx index a7c61ed5746fdd..d071a4dc14f14d 100644 --- a/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx +++ b/docs/product/issues/issue-details/replay-issues/rage-clicks.mdx @@ -5,7 +5,7 @@ description: Learn about Session Replay rage click issues. og_image: /og-images/product-issues-issue-details-replay-issues-rage-clicks.png --- -If you've enabled [Session Replay](/product/explore/session-replay/), you'll be able to see rage click issues on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive page element. They are a strong signal of user frustration and most likely deserve your attention. +If you've enabled [Session Replay](/product/session-replay/), you'll be able to see rage click issues on the [**Issues**](https://sentry.io/orgredirect/organizations/:orgslug/issues/) page in Sentry. Rage clicks are a series of consecutive clicks on the same unresponsive page element. They are a strong signal of user frustration and most likely deserve your attention. ![Rage click issue](./img/rage-click-issue-details.png) @@ -13,7 +13,7 @@ If you've enabled [Session Replay](/product/explore/session-replay/), you'll be In order to see rage clicks in your issue stream on the **Issues** page, your organization needs to: -- Be sending [Session Replay events](/product/explore/session-replay/getting-started/) +- Be sending [Session Replay events](/product/session-replay/getting-started/) - Enable the JavaScript SDK (or framework-specific bundle), version 7.60.1 or higher diff --git a/docs/product/explore/logs/getting-started/index.mdx b/docs/product/logs/getting-started/index.mdx similarity index 100% rename from docs/product/explore/logs/getting-started/index.mdx rename to docs/product/logs/getting-started/index.mdx diff --git a/docs/product/explore/logs/img/AutoRefresh.png b/docs/product/logs/img/AutoRefresh.png similarity index 100% rename from docs/product/explore/logs/img/AutoRefresh.png rename to docs/product/logs/img/AutoRefresh.png diff --git a/docs/product/explore/logs/img/ContinueScanning.png b/docs/product/logs/img/ContinueScanning.png similarity index 100% rename from docs/product/explore/logs/img/ContinueScanning.png rename to docs/product/logs/img/ContinueScanning.png diff --git a/docs/product/explore/logs/img/ExtrapolatedLogs.png b/docs/product/logs/img/ExtrapolatedLogs.png similarity index 100% rename from docs/product/explore/logs/img/ExtrapolatedLogs.png rename to docs/product/logs/img/ExtrapolatedLogs.png diff --git a/docs/product/explore/logs/img/LogQueries.png b/docs/product/logs/img/LogQueries.png similarity index 100% rename from docs/product/explore/logs/img/LogQueries.png rename to docs/product/logs/img/LogQueries.png diff --git a/docs/product/explore/logs/img/LogSearchRawText.png b/docs/product/logs/img/LogSearchRawText.png similarity index 100% rename from docs/product/explore/logs/img/LogSearchRawText.png rename to docs/product/logs/img/LogSearchRawText.png diff --git a/docs/product/explore/logs/img/LogSearchTags.png b/docs/product/logs/img/LogSearchTags.png similarity index 100% rename from docs/product/explore/logs/img/LogSearchTags.png rename to docs/product/logs/img/LogSearchTags.png diff --git a/docs/product/explore/logs/img/LogsExpanded.png b/docs/product/logs/img/LogsExpanded.png similarity index 100% rename from docs/product/explore/logs/img/LogsExpanded.png rename to docs/product/logs/img/LogsExpanded.png diff --git a/docs/product/explore/logs/img/StructuredLogs.png b/docs/product/logs/img/StructuredLogs.png similarity index 100% rename from docs/product/explore/logs/img/StructuredLogs.png rename to docs/product/logs/img/StructuredLogs.png diff --git a/docs/product/explore/logs/index.mdx b/docs/product/logs/index.mdx similarity index 97% rename from docs/product/explore/logs/index.mdx rename to docs/product/logs/index.mdx index dca48291558431..118b92ef8bdc36 100644 --- a/docs/product/explore/logs/index.mdx +++ b/docs/product/logs/index.mdx @@ -1,6 +1,7 @@ --- title: Logs -sidebar_order: 70 +sidebar_order: 210 +sidebar_section: debug description: >- Structured logs allow you to send, view and query logs and parameters sent from your applications within Sentry. @@ -27,11 +28,11 @@ Not everything in your application generates an error or requires full tracing. - **Application state**: Configuration loading, service initialization, and connection status - **Business events**: Order placements, payment processing, and notification delivery -Learn how to [send structured logs](/product/explore/logs/getting-started/) with custom attributes that you can search and filter in Sentry. +Learn how to [send structured logs](/product/logs/getting-started/) with custom attributes that you can search and filter in Sentry. ## Set up Logs -To get started with Logs, navigate to the [Getting Started](/product/explore/logs/getting-started/) page and select your SDK from the list. +To get started with Logs, navigate to the [Getting Started](/product/logs/getting-started/) page and select your SDK from the list. If you're using a platform where you can't install the Sentry SDK directly, or if you want to forward logs from platform-native logging systems, you can use [log drains](/product/drains/) to send logs to Sentry. diff --git a/docs/product/explore/metrics/getting-started/index.mdx b/docs/product/metrics/getting-started/index.mdx similarity index 100% rename from docs/product/explore/metrics/getting-started/index.mdx rename to docs/product/metrics/getting-started/index.mdx diff --git a/docs/product/explore/metrics/img/aggregates.png b/docs/product/metrics/img/aggregates.png similarity index 100% rename from docs/product/explore/metrics/img/aggregates.png rename to docs/product/metrics/img/aggregates.png diff --git a/docs/product/explore/metrics/img/metric-equation-example.png b/docs/product/metrics/img/metric-equation-example.png similarity index 100% rename from docs/product/explore/metrics/img/metric-equation-example.png rename to docs/product/metrics/img/metric-equation-example.png diff --git a/docs/product/explore/metrics/img/samples.png b/docs/product/metrics/img/samples.png similarity index 100% rename from docs/product/explore/metrics/img/samples.png rename to docs/product/metrics/img/samples.png diff --git a/docs/product/explore/metrics/index.mdx b/docs/product/metrics/index.mdx similarity index 94% rename from docs/product/explore/metrics/index.mdx rename to docs/product/metrics/index.mdx index 06a8f32b4f838b..744bfd7e219600 100644 --- a/docs/product/explore/metrics/index.mdx +++ b/docs/product/metrics/index.mdx @@ -1,6 +1,7 @@ --- title: Application Metrics -sidebar_order: 75 +sidebar_order: 240 +sidebar_section: debug description: >- Send counters, gauges, and distributions from your code to track application health and drill down into related traces, logs, and errors. @@ -24,7 +25,7 @@ Not everything in your application generates an error or requires full tracing. ## Set Up Application Metrics -To get started, navigate to the [Getting Started](/product/explore/metrics/getting-started/) page and select your SDK from the list. +To get started, navigate to the [Getting Started](/product/metrics/getting-started/) page and select your SDK from the list. ## Metric Types @@ -158,9 +159,9 @@ Instead of "metric alert → guesswork," debugging becomes a **single flow**: Me ### When a Sample Doesn't Have a Trace -Application Metrics are typically sampled at 100% while traces are usually sampled at a much lower rate, so some metric events won't have a trace attached to them. When that happens, use the metric's attributes (such as release, environment, or route) to find a comparable trace in [Trace Explorer](/product/explore/trace-explorer/). +Application Metrics are typically sampled at 100% while traces are usually sampled at a much lower rate, so some metric events won't have a trace attached to them. When that happens, use the metric's attributes (such as release, environment, or route) to find a comparable trace in [Trace Explorer](/product/trace-explorer/). -[Cross-Event Querying](/product/explore/trace-explorer/#cross-event-querying) makes this easier by letting you filter traces based on related spans, logs, and application metrics. The comparable trace gives you the same debugging context as a directly attached one. +[Cross-Event Querying](/product/trace-explorer/#cross-event-querying) makes this easier by letting you filter traces based on related spans, logs, and application metrics. The comparable trace gives you the same debugging context as a directly attached one. ## Metric Attributes @@ -191,8 +192,8 @@ Application Metrics are best for **application and code-based health signals**, - Success/failure rates **Other Sentry features that may be a better fit:** -- Log aggregation - use [Logs](/product/explore/logs/) -- Full request tracing - use [Traces](/product/explore/trace-explorer/) +- Log aggregation - use [Logs](/product/logs/) +- Full request tracing - use [Traces](/product/trace-explorer/) ## AI-Powered Metric Analysis diff --git a/docs/product/monitors-and-alerts/index.mdx b/docs/product/monitors-and-alerts/index.mdx index e4562058a09500..67e5e2d767f3a5 100644 --- a/docs/product/monitors-and-alerts/index.mdx +++ b/docs/product/monitors-and-alerts/index.mdx @@ -3,7 +3,8 @@ title: Monitors and Alerts description: >- Use Monitors to decide when problems become issues, and Alerts to notify, ticket, and automate next steps when those issues match your rules. -sidebar_order: 8000 +sidebar_order: 410 +sidebar_section: automate --- Sentry separates **what you detect** from **what you do about it**: diff --git a/docs/product/monitors-and-alerts/monitors/index.mdx b/docs/product/monitors-and-alerts/monitors/index.mdx index ce5cadc7476807..389fd78bc23e60 100644 --- a/docs/product/monitors-and-alerts/monitors/index.mdx +++ b/docs/product/monitors-and-alerts/monitors/index.mdx @@ -32,8 +32,8 @@ To create a Monitor, navigate to the [Monitors](https://sentry.io/monitors/new/) You can also create a Metric Monitor directly from a query: -- From the [Application Metrics](/product/explore/metrics/) Explorer, open the **Save As** menu and choose **Monitor for** to create a Monitor with the current metric and filters pre-selected. -- From [Discover](/product/explore/discover-queries/), use the **Create Monitor** button to turn the current query into a Monitor. +- From the [Application Metrics](/product/metrics/) Explorer, open the **Save As** menu and choose **Monitor for** to create a Monitor with the current metric and filters pre-selected. +- From [Discover](/product/discover-queries/), use the **Create Monitor** button to turn the current query into a Monitor. ### General Settings diff --git a/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx b/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx index b23e50a37e12d2..890b4753465e1c 100644 --- a/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx +++ b/docs/product/monitors-and-alerts/monitors/uptime-monitoring/uptime-tracing.mdx @@ -32,7 +32,7 @@ Sentry-Trace: 32d4011600324838afcd666edadc1d09-8d5ca7419a02ca36 ## Tracing Errors -Error tracing is enabled by default for uptime checks. When downtime is detected, an [Uptime Issue](/product/issues/issue-details/uptime-issues/) is created. You can then go to Sentry's [**Trace Explorer**](/product/explore/traces/) page to view any related errors. +Error tracing is enabled by default for uptime checks. When downtime is detected, an [Uptime Issue](/product/issues/issue-details/uptime-issues/) is created. You can then go to Sentry's [**Trace Explorer**](/product/trace-explorer/) page to view any related errors. Because uptime requests won't override your SDK’s error sampling rate, some errors may not appear in traces if that rate is set to below 1. diff --git a/docs/product/notifications/index.mdx b/docs/product/notifications/index.mdx index 593e3eb94d4a42..316638bccad67f 100644 --- a/docs/product/notifications/index.mdx +++ b/docs/product/notifications/index.mdx @@ -1,6 +1,7 @@ --- title: Sentry Notifications -sidebar_order: 40 +sidebar_order: 500 +sidebar_section: platform description: >- Learn about the types of notifications that Sentry sends you, and how to manage them. diff --git a/docs/product/onboarding/index.mdx b/docs/product/onboarding/index.mdx index 03c9582b405bd3..24f036385bb478 100644 --- a/docs/product/onboarding/index.mdx +++ b/docs/product/onboarding/index.mdx @@ -1,7 +1,7 @@ --- title: Quick-Start Guide description: An easy onboarding guide for Sentry. -sidebar_order: 4000 +sidebar_order: 6 og_image: /og-images/product-onboarding.png --- diff --git a/docs/product/partnership-platform/index.mdx b/docs/product/partnership-platform/index.mdx index 35a67e2490a4d4..e75ec27e4439cd 100644 --- a/docs/product/partnership-platform/index.mdx +++ b/docs/product/partnership-platform/index.mdx @@ -1,7 +1,8 @@ --- title: "Partnership Platform" description: "Learn how to integrate Sentry into your platform and provide error monitoring and performance insights to your customers." -sidebar_order: 35 +sidebar_order: 530 +sidebar_section: platform --- # Partnership Platform diff --git a/docs/product/explore/profiling/continuous-ui-profiling-migration-guide.mdx b/docs/product/profiling/continuous-ui-profiling-migration-guide.mdx similarity index 98% rename from docs/product/explore/profiling/continuous-ui-profiling-migration-guide.mdx rename to docs/product/profiling/continuous-ui-profiling-migration-guide.mdx index cb059ab6ae7df7..71b6616c9bf3f1 100644 --- a/docs/product/explore/profiling/continuous-ui-profiling-migration-guide.mdx +++ b/docs/product/profiling/continuous-ui-profiling-migration-guide.mdx @@ -4,7 +4,7 @@ sidebar_order: 150 description: "Learn how to migrate from the older transaction-based Profiling API to the new Continuous and UI Profiling APIs." --- -To learn more about the conceptual difference between the previous transaction-based and the new Continuous Profiling and UI Profiling products, please see [the Transaction vs Continuous Profiling docs](/product/explore/profiling/transaction-vs-continuous-profiling/). To summarize, the key differences are: +To learn more about the conceptual difference between the previous transaction-based and the new Continuous Profiling and UI Profiling products, please see [the Transaction vs Continuous Profiling docs](/product/profiling/transaction-vs-continuous-profiling/). To summarize, the key differences are: - Transaction-based profiling was bound to the lifecycle of a trace. Profiling only occurred during a transaction or root span and could not be started independently. **Continuous and UI Profiling support both a trace-bound lifecycle mode, and a manual lifecycle mode that allows you to directly control the profiler using start/stop APIs**. - Transaction-based profiles were limited at 30 seconds in length. **Continuous and UI Profiling support arbitrarily long profiles.** diff --git a/docs/product/explore/profiling/differential-flamegraphs.mdx b/docs/product/profiling/differential-flamegraphs.mdx similarity index 100% rename from docs/product/explore/profiling/differential-flamegraphs.mdx rename to docs/product/profiling/differential-flamegraphs.mdx diff --git a/docs/product/explore/profiling/flame-charts-graphs.mdx b/docs/product/profiling/flame-charts-graphs.mdx similarity index 100% rename from docs/product/explore/profiling/flame-charts-graphs.mdx rename to docs/product/profiling/flame-charts-graphs.mdx diff --git a/docs/product/explore/profiling/getting-started.mdx b/docs/product/profiling/getting-started.mdx similarity index 95% rename from docs/product/explore/profiling/getting-started.mdx rename to docs/product/profiling/getting-started.mdx index 847f18be738bf4..72a1ac47130422 100644 --- a/docs/product/explore/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/explore/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/explore/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/explore/profiling/img/aggregated-flame-graph-view.png b/docs/product/profiling/img/aggregated-flame-graph-view.png similarity index 100% rename from docs/product/explore/profiling/img/aggregated-flame-graph-view.png rename to docs/product/profiling/img/aggregated-flame-graph-view.png diff --git a/docs/product/explore/profiling/img/differential-flamegraph-inverted.png b/docs/product/profiling/img/differential-flamegraph-inverted.png similarity index 100% rename from docs/product/explore/profiling/img/differential-flamegraph-inverted.png rename to docs/product/profiling/img/differential-flamegraph-inverted.png diff --git a/docs/product/explore/profiling/img/differential-flamegraph-new.png b/docs/product/profiling/img/differential-flamegraph-new.png similarity index 100% rename from docs/product/explore/profiling/img/differential-flamegraph-new.png rename to docs/product/profiling/img/differential-flamegraph-new.png diff --git a/docs/product/explore/profiling/img/differential-flamegraph-regular.png b/docs/product/profiling/img/differential-flamegraph-regular.png similarity index 100% rename from docs/product/explore/profiling/img/differential-flamegraph-regular.png rename to docs/product/profiling/img/differential-flamegraph-regular.png diff --git a/docs/product/explore/profiling/img/differential-flamegraph-table.png b/docs/product/profiling/img/differential-flamegraph-table.png similarity index 100% rename from docs/product/explore/profiling/img/differential-flamegraph-table.png rename to docs/product/profiling/img/differential-flamegraph-table.png diff --git a/docs/product/explore/profiling/img/differential-flamegraph.png b/docs/product/profiling/img/differential-flamegraph.png similarity index 100% rename from docs/product/explore/profiling/img/differential-flamegraph.png rename to docs/product/profiling/img/differential-flamegraph.png diff --git a/docs/product/explore/profiling/img/fib-flame-chart.png b/docs/product/profiling/img/fib-flame-chart.png similarity index 100% rename from docs/product/explore/profiling/img/fib-flame-chart.png rename to docs/product/profiling/img/fib-flame-chart.png diff --git a/docs/product/explore/profiling/img/fib-flame-graph.png b/docs/product/profiling/img/fib-flame-graph.png similarity index 100% rename from docs/product/explore/profiling/img/fib-flame-graph.png rename to docs/product/profiling/img/fib-flame-graph.png diff --git a/docs/product/explore/profiling/img/flame-chart-hair.png b/docs/product/profiling/img/flame-chart-hair.png similarity index 100% rename from docs/product/explore/profiling/img/flame-chart-hair.png rename to docs/product/profiling/img/flame-chart-hair.png diff --git a/docs/product/explore/profiling/img/flame-chart-less-hair.png b/docs/product/profiling/img/flame-chart-less-hair.png similarity index 100% rename from docs/product/explore/profiling/img/flame-chart-less-hair.png rename to docs/product/profiling/img/flame-chart-less-hair.png diff --git a/docs/product/explore/profiling/img/flame-chart.png b/docs/product/profiling/img/flame-chart.png similarity index 100% rename from docs/product/explore/profiling/img/flame-chart.png rename to docs/product/profiling/img/flame-chart.png diff --git a/docs/product/explore/profiling/img/minimap.png b/docs/product/profiling/img/minimap.png similarity index 100% rename from docs/product/explore/profiling/img/minimap.png rename to docs/product/profiling/img/minimap.png diff --git a/docs/product/explore/profiling/img/profile-details-trace.png b/docs/product/profiling/img/profile-details-trace.png similarity index 100% rename from docs/product/explore/profiling/img/profile-details-trace.png rename to docs/product/profiling/img/profile-details-trace.png diff --git a/docs/product/explore/profiling/img/profile-flame-chart.png b/docs/product/profiling/img/profile-flame-chart.png similarity index 100% rename from docs/product/explore/profiling/img/profile-flame-chart.png rename to docs/product/profiling/img/profile-flame-chart.png diff --git a/docs/product/explore/profiling/img/profiling-page-aggregate-flamegraph.png b/docs/product/profiling/img/profiling-page-aggregate-flamegraph.png similarity index 100% rename from docs/product/explore/profiling/img/profiling-page-aggregate-flamegraph.png rename to docs/product/profiling/img/profiling-page-aggregate-flamegraph.png diff --git a/docs/product/explore/profiling/img/profiling-page-functions.png b/docs/product/profiling/img/profiling-page-functions.png similarity index 100% rename from docs/product/explore/profiling/img/profiling-page-functions.png rename to docs/product/profiling/img/profiling-page-functions.png diff --git a/docs/product/explore/profiling/img/profiling-page-transactions.png b/docs/product/profiling/img/profiling-page-transactions.png similarity index 100% rename from docs/product/explore/profiling/img/profiling-page-transactions.png rename to docs/product/profiling/img/profiling-page-transactions.png diff --git a/docs/product/explore/profiling/img/search-bar.png b/docs/product/profiling/img/search-bar.png similarity index 100% rename from docs/product/explore/profiling/img/search-bar.png rename to docs/product/profiling/img/search-bar.png diff --git a/docs/product/explore/profiling/img/thread-selector.png b/docs/product/profiling/img/thread-selector.png similarity index 100% rename from docs/product/explore/profiling/img/thread-selector.png rename to docs/product/profiling/img/thread-selector.png diff --git a/docs/product/explore/profiling/img/trace-environment-view.png b/docs/product/profiling/img/trace-environment-view.png similarity index 100% rename from docs/product/explore/profiling/img/trace-environment-view.png rename to docs/product/profiling/img/trace-environment-view.png diff --git a/docs/product/explore/profiling/img/trace-view-profiles.png b/docs/product/profiling/img/trace-view-profiles.png similarity index 100% rename from docs/product/explore/profiling/img/trace-view-profiles.png rename to docs/product/profiling/img/trace-view-profiles.png diff --git a/docs/product/explore/profiling/img/trace-view-span-profile.png b/docs/product/profiling/img/trace-view-span-profile.png similarity index 100% rename from docs/product/explore/profiling/img/trace-view-span-profile.png rename to docs/product/profiling/img/trace-view-span-profile.png diff --git a/docs/product/explore/profiling/img/trace-view.png b/docs/product/profiling/img/trace-view.png similarity index 100% rename from docs/product/explore/profiling/img/trace-view.png rename to docs/product/profiling/img/trace-view.png diff --git a/docs/product/explore/profiling/img/transaction-summary-profiles.png b/docs/product/profiling/img/transaction-summary-profiles.png similarity index 100% rename from docs/product/explore/profiling/img/transaction-summary-profiles.png rename to docs/product/profiling/img/transaction-summary-profiles.png diff --git a/docs/product/explore/profiling/img/tree-view.gif b/docs/product/profiling/img/tree-view.gif similarity index 100% rename from docs/product/explore/profiling/img/tree-view.gif rename to docs/product/profiling/img/tree-view.gif diff --git a/docs/product/explore/profiling/index.mdx b/docs/product/profiling/index.mdx similarity index 89% rename from docs/product/explore/profiling/index.mdx rename to docs/product/profiling/index.mdx index 2d3c54fd89f78a..3282124b0a8c44 100644 --- a/docs/product/explore/profiling/index.mdx +++ b/docs/product/profiling/index.mdx @@ -1,6 +1,7 @@ --- title: Profiling -sidebar_order: 50 +sidebar_order: 230 +sidebar_section: debug description: >- Profiling offers a deeper level of visibility on top of traditional tracing, removing the need for custom instrumentation and enabling precise code-level @@ -40,7 +41,7 @@ Profiling helps you quickly identify performance bottlenecks, enabling you to bu Sentry supports profiling for both backend and frontend use cases with two products: * **Continuous Profiling** enables *continuously* profiling backend services to find code paths that are causing excessive resource usage and high infrastructure cost. -* **UI Profiling** enables profiling critical user flows (or entire user sessions) in browser and [mobile](/product/explore/profiling/mobile-app-profiling/) apps to find code paths that are causing janky scrolling and animations, high interaction latency, and slow load times that contribute to a poor user experience. +* **UI Profiling** enables profiling critical user flows (or entire user sessions) in browser and [mobile](/product/profiling/mobile-app-profiling/) apps to find code paths that are causing janky scrolling and animations, high interaction latency, and slow load times that contribute to a poor user experience. ## Profiling Page @@ -66,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/explore/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/explore/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) @@ -95,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/explore/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/explore/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png b/docs/product/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png similarity index 100% rename from docs/product/explore/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png rename to docs/product/profiling/mobile-app-profiling/img/flamechart-with-gpu-overlay.png diff --git a/docs/product/explore/profiling/mobile-app-profiling/index.mdx b/docs/product/profiling/mobile-app-profiling/index.mdx similarity index 100% rename from docs/product/explore/profiling/mobile-app-profiling/index.mdx rename to docs/product/profiling/mobile-app-profiling/index.mdx diff --git a/docs/product/explore/profiling/mobile-app-profiling/metrics.mdx b/docs/product/profiling/mobile-app-profiling/metrics.mdx similarity index 100% rename from docs/product/explore/profiling/mobile-app-profiling/metrics.mdx rename to docs/product/profiling/mobile-app-profiling/metrics.mdx diff --git a/docs/product/explore/profiling/performance-overhead.mdx b/docs/product/profiling/performance-overhead.mdx similarity index 100% rename from docs/product/explore/profiling/performance-overhead.mdx rename to docs/product/profiling/performance-overhead.mdx diff --git a/docs/product/explore/profiling/profile-details.mdx b/docs/product/profiling/profile-details.mdx similarity index 97% rename from docs/product/explore/profiling/profile-details.mdx rename to docs/product/profiling/profile-details.mdx index 3f5e007d08b764..a8570fade72755 100644 --- a/docs/product/explore/profiling/profile-details.mdx +++ b/docs/product/profiling/profile-details.mdx @@ -5,9 +5,9 @@ description: Learn how to explore your profile data using the Profile Details pa 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/explore/profiling/) documentation. +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/explore/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/explore/profiling/transaction-vs-continuous-profiling.mdx b/docs/product/profiling/transaction-vs-continuous-profiling.mdx similarity index 91% rename from docs/product/explore/profiling/transaction-vs-continuous-profiling.mdx rename to docs/product/profiling/transaction-vs-continuous-profiling.mdx index db8611216e2291..db498b81c0673e 100644 --- a/docs/product/explore/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/explore/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/explore/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 @@ -44,10 +44,10 @@ One of the benefits of transaction-based profiling was the simplicity of being a ## Sampling -As with transaction-based profiling, Continuous Profiling & UI Profiling support client-side sampling controls. However, sampling now occurs at a **session** scope rather than at an individual profile scope. For more information on how sampling works, read the [migration guide](/product/explore/profiling/continuous-ui-profiling-migration-guide/). +As with transaction-based profiling, Continuous Profiling & UI Profiling support client-side sampling controls. However, sampling now occurs at a **session** scope rather than at an individual profile scope. For more information on how sampling works, read the [migration guide](/product/profiling/continuous-ui-profiling-migration-guide/). ## Next Steps -If you are an existing user of transaction-based profiling, read the [migration guide](/product/explore/profiling/continuous-ui-profiling-migration-guide/) for instructions on how to migrate to the new APIs. +If you are an existing user of transaction-based profiling, read the [migration guide](/product/profiling/continuous-ui-profiling-migration-guide/) for instructions on how to migrate to the new APIs. -If you are a new user, read the [getting started](/product/explore/profiling/getting-started/) guide for the SDK that you’re using. +If you are a new user, read the [getting started](/product/profiling/getting-started/) guide for the SDK that you’re using. diff --git a/docs/product/projects/index.mdx b/docs/product/projects/index.mdx index 79f7288de21941..1704dc15571744 100644 --- a/docs/product/projects/index.mdx +++ b/docs/product/projects/index.mdx @@ -1,6 +1,6 @@ --- title: Projects -sidebar_order: 30 +sidebar_order: 7 description: "View all the projects associated with teams that you're a member of, then dive into their details quickly." --- diff --git a/docs/product/relay/index.mdx b/docs/product/relay/index.mdx index 5dc0e8dc4d4d2d..8da3cf2f02dcda 100644 --- a/docs/product/relay/index.mdx +++ b/docs/product/relay/index.mdx @@ -1,7 +1,8 @@ --- title: Relay description: "Learn more about Relay, Sentry's data security solution." -sidebar_order: 3000 +sidebar_order: 520 +sidebar_section: platform --- Sentry Relay offers enterprise-grade data security by providing a standalone service that acts as a middle layer between your application and sentry.io. diff --git a/docs/product/releases/health/index.mdx b/docs/product/releases/health/index.mdx index b0ae9e1b228ec0..517964dbae21c7 100644 --- a/docs/product/releases/health/index.mdx +++ b/docs/product/releases/health/index.mdx @@ -9,7 +9,7 @@ og_image: /og-images/product-releases-health.png -Note, that Sessions (as described below) are not the same as a [Session Replay](/product/explore/session-replay/), (a video-like reproduction of the user's session). We don't bill for release health sessions. +Note, that Sessions (as described below) are not the same as a [Session Replay](/product/session-replay/), (a video-like reproduction of the user's session). We don't bill for release health sessions. diff --git a/docs/product/releases/index.mdx b/docs/product/releases/index.mdx index a5b9f194e8ff8b..b7a9c70ce2e462 100644 --- a/docs/product/releases/index.mdx +++ b/docs/product/releases/index.mdx @@ -1,6 +1,7 @@ --- title: Releases -sidebar_order: 110 +sidebar_order: 310 +sidebar_section: measure description: >- Learn how to provide Sentry with important information about your releases, such as release health and release details, to determine regressions and diff --git a/docs/product/sentry-basics/index.mdx b/docs/product/sentry-basics/index.mdx index 05b9ecacb18a72..756b734de8ab3d 100644 --- a/docs/product/sentry-basics/index.mdx +++ b/docs/product/sentry-basics/index.mdx @@ -1,6 +1,6 @@ --- title: Getting Started With Sentry -sidebar_order: 10 +sidebar_order: 5 description: "Learn about our recommendations for getting the most out of Sentry." --- @@ -14,7 +14,7 @@ There are three things we recommend you do to get the most out of Sentry: - **Connect your codebase**, making sure you've also set up [source code management integrations](/integrations/source-code-mgmt/) and [source maps](/product/sentry-basics/integrate-frontend/upload-source-maps/) (if applicable). This will allow Sentry to link errors and performance issues directly to the problematic line of code via readable stack traces and suspect commits. - **Set up [alerts](/product/monitors-and-alerts/alerts/)** to make sure you know when things you care about are going wrong. You can choose to be alerted via one of our chat integrations like [Slack](/integrations/notification-incidents/slack/) or [Discord](/integrations/notification-incidents/discord/). Check out our [alert best practices](/product/monitors-and-alerts/alerts/#alerts-best-practices) to learn how to only get relevant notifications. -- **Customize [Discover](/product/explore/discover-queries/), [Dashboards](/product/dashboards/), and [queries](/product/explore/discover-queries/query-builder/)** to better control the kinds of insights you get when things are going wrong in your app. Lastly, create [custom tags](/concepts/search/searchable-properties/#custom-tags) tailored to your use case for more granular searching and querying. +- **Customize [Discover](/product/discover-queries/), [Dashboards](/product/dashboards/), and [queries](/product/discover-queries/query-builder/)** to better control the kinds of insights you get when things are going wrong in your app. Lastly, create [custom tags](/concepts/search/searchable-properties/#custom-tags) tailored to your use case for more granular searching and querying. **Want a TL;DR for getting started? Download our ["Developer Quick Reference Guide"](/pdfs/developer-quick-reference-guide.pdf)** diff --git a/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx b/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx index 9b0425a5885ca5..3f45292ac685ea 100644 --- a/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx +++ b/docs/product/sentry-basics/integrate-frontend/configure-scms.mdx @@ -181,6 +181,6 @@ You should now have Sentry's error monitoring set up with source maps and suspec On top of error monitoring, Sentry offers other features to help you detect and fix problems with your apps, like: -- [Session Replay](/product/explore/session-replay/) to view a a video-like reproduction of your user sessions when errors occur. +- [Session Replay](/product/session-replay/) to view a a video-like reproduction of your user sessions when errors occur. - [pre-built Sentry Dashboards](/product/dashboards/sentry-dashboards/) to track application performance and errors across services. -- [Profiling](/product/explore/profiling/) to get deeper level of visibility on top of traditional tracing. +- [Profiling](/product/profiling/) to get deeper level of visibility on top of traditional tracing. diff --git a/docs/product/sentry-basics/performance-monitoring.mdx b/docs/product/sentry-basics/performance-monitoring.mdx index 1e6e56fedaa213..baed496a1f813f 100644 --- a/docs/product/sentry-basics/performance-monitoring.mdx +++ b/docs/product/sentry-basics/performance-monitoring.mdx @@ -41,7 +41,7 @@ Alongside typical [error issues](/product/issues/issue-details/error-issues/), S ### 3: Trace Explorer: Find root causes & common patterns for performance issues -While Performance Issues and Sentry Dashboards give you a high-level view of performance data, the [Trace Explorer](/product/explore/trace-explorer/) lets you slice and dice all your performance data by any attribute. This is an extremely powerful tool for finding root causes and common patterns for performance regressions or potential optimizations. For instance, you can find the p95 duration of all spans on the `GET /users/:id` endpoint, or find all pages slowing down because of a particular middleware routing. +While Performance Issues and Sentry Dashboards give you a high-level view of performance data, the [Trace Explorer](/product/trace-explorer/) lets you slice and dice all your performance data by any attribute. This is an extremely powerful tool for finding root causes and common patterns for performance regressions or potential optimizations. For instance, you can find the p95 duration of all spans on the `GET /users/:id` endpoint, or find all pages slowing down because of a particular middleware routing. Trace Explorer also lets you quickly calculate metrics based on your span data, like p50, p95, and p99 durations, and then group them by any attribute. This lets you quickly see if there are specific endpoints, versions, user groups, etc. that are performing poorly. You can also compare attributes from a zoomed in time span against your app's baseline data in order to more efficiently find the root cause. For a deeper dive into how you can use Trace Explorer and Span Metrics, take a look at our most recent [blog post](https://blog.sentry.io/find-and-fix-performance-bottlenecks-with-sentrys-trace-explorer/). @@ -52,7 +52,7 @@ Trace Explorer also lets you quickly calculate metrics based on your span data, By default, Sentry automatically tracks a set of [performance metrics](/platforms/javascript/tracing/span-metrics/) for every trace. These are used to populate the Sentry Dashboards, but you can also use them to build custom [dashboards](/product/dashboards/) and [alerts](/product/monitors-and-alerts/alerts/). -Opting into the [Early Adopter](https://sentry.io/orgredirect/settings/:orgslug/) program for the Trace Explorer also gives you access to the new [Span Metrics](/product/explore/new-trace-explorer/#span-metrics/) feature, which lets you calculate custom metrics based on your span data. This is extremely useful for building dashboards and alerts that are underpinned by real performance tracing data, so you can quickly debug performance issues. +Opting into the [Early Adopter](https://sentry.io/orgredirect/settings/:orgslug/) program for the Trace Explorer also gives you access to the new [Span Metrics](/product/trace-explorer/#span-metrics/) feature, which lets you calculate custom metrics based on your span data. This is extremely useful for building dashboards and alerts that are underpinned by real performance tracing data, so you can quickly debug performance issues. ## How to set up Performance Monitoring diff --git a/docs/product/sentry-toolbar/index.mdx b/docs/product/sentry-toolbar/index.mdx index d10c58736b7fe0..43d92f08d2ccfe 100644 --- a/docs/product/sentry-toolbar/index.mdx +++ b/docs/product/sentry-toolbar/index.mdx @@ -1,6 +1,7 @@ --- title: Sentry Toolbar -sidebar_order: 110 +sidebar_order: 510 +sidebar_section: platform description: >- Bring critical Sentry insights and tools directly into your web app for easier troubleshooting with the Sentry Toolbar. @@ -30,7 +31,7 @@ The feedback panel shows you the most recent user feedback messages for the page ## Feature Flags Panel -Feature flags are a powerful tool that allow you to control the visibility of features in your app, enabling you to ship, test, and experiment with confidence. The feature flag panel allows you to quickly view and override feature flags locally. You can override any feature flag to be `true` or `false` for your browser session, so you can verify its behavior and observe the impact it might have on errors. Learn more about how to [configure the feature flag panel](/product/sentry-toolbar/setup/#implement-feature-flag-adapter) and [what data Sentry can track](/product/explore/feature-flags/) related to your feature flagging system. +Feature flags are a powerful tool that allow you to control the visibility of features in your app, enabling you to ship, test, and experiment with confidence. The feature flag panel allows you to quickly view and override feature flags locally. You can override any feature flag to be `true` or `false` for your browser session, so you can verify its behavior and observe the impact it might have on errors. Learn more about how to [configure the feature flag panel](/product/sentry-toolbar/setup/#implement-feature-flag-adapter) and [what data Sentry can track](/product/issues/issue-details/feature-flags/) related to your feature flagging system. ![Toolbar with the Feature Flags Panel open](./img/feature-flags-panel.png) diff --git a/docs/product/explore/session-replay/access-control.mdx b/docs/product/session-replay/access-control.mdx similarity index 100% rename from docs/product/explore/session-replay/access-control.mdx rename to docs/product/session-replay/access-control.mdx diff --git a/docs/product/explore/session-replay/img/replay-details-share.png b/docs/product/session-replay/img/replay-details-share.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-details-share.png rename to docs/product/session-replay/img/replay-details-share.png diff --git a/docs/product/explore/session-replay/img/replay-details-tags.png b/docs/product/session-replay/img/replay-details-tags.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-details-tags.png rename to docs/product/session-replay/img/replay-details-tags.png diff --git a/docs/product/explore/session-replay/img/replay-details.png b/docs/product/session-replay/img/replay-details.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-details.png rename to docs/product/session-replay/img/replay-details.png diff --git a/docs/product/explore/session-replay/img/replay-index-delete-all.png b/docs/product/session-replay/img/replay-index-delete-all.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-index-delete-all.png rename to docs/product/session-replay/img/replay-index-delete-all.png diff --git a/docs/product/explore/session-replay/img/replay-index-delete-visible.png b/docs/product/session-replay/img/replay-index-delete-visible.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-index-delete-visible.png rename to docs/product/session-replay/img/replay-index-delete-visible.png diff --git a/docs/product/explore/session-replay/img/replay-index-filtering.png b/docs/product/session-replay/img/replay-index-filtering.png similarity index 100% rename from docs/product/explore/session-replay/img/replay-index-filtering.png rename to docs/product/session-replay/img/replay-index-filtering.png diff --git a/docs/product/explore/session-replay/index.mdx b/docs/product/session-replay/index.mdx similarity index 95% rename from docs/product/explore/session-replay/index.mdx rename to docs/product/session-replay/index.mdx index 09fc742cabef55..b6062b1e837a36 100644 --- a/docs/product/explore/session-replay/index.mdx +++ b/docs/product/session-replay/index.mdx @@ -1,6 +1,7 @@ --- title: "Session Replay" -sidebar_order: 70 +sidebar_order: 220 +sidebar_section: debug description: "Use Session Replay to get reproductions of user sessions to improve your app experience." --- diff --git a/docs/product/explore/session-replay/mobile/img/session-replay-redacted.png b/docs/product/session-replay/mobile/img/session-replay-redacted.png similarity index 100% rename from docs/product/explore/session-replay/mobile/img/session-replay-redacted.png rename to docs/product/session-replay/mobile/img/session-replay-redacted.png diff --git a/docs/product/explore/session-replay/mobile/img/session-replay.png b/docs/product/session-replay/mobile/img/session-replay.png similarity index 100% rename from docs/product/explore/session-replay/mobile/img/session-replay.png rename to docs/product/session-replay/mobile/img/session-replay.png diff --git a/docs/product/explore/session-replay/mobile/index.mdx b/docs/product/session-replay/mobile/index.mdx similarity index 98% rename from docs/product/explore/session-replay/mobile/index.mdx rename to docs/product/session-replay/mobile/index.mdx index b2ce6a1917e754..6cc173e21111a1 100644 --- a/docs/product/explore/session-replay/mobile/index.mdx +++ b/docs/product/session-replay/mobile/index.mdx @@ -9,7 +9,7 @@ og_image: /og-images/product-explore-session-replay-mobile.png Session Replay allows you to see reproductions of user sessions, which can help you understand what happened before, during, and after an error or performance issue occurred. As you play back each session, you'll be able to see every user interaction in relation to network requests, frontend and backend errors, backend spans, and more. -Replays help you see exactly how the user experience is impacted by errors. Because they're integrated with our Issues product, you'll be able to see session replays connected to error events on the [Issue Details](/product/issues/issue-details/) page in Sentry. To make sure backend errors are also included in the replay, see our [backend set up instructions](/product/explore/session-replay/web/getting-started/#replays-for-backend-errors). +Replays help you see exactly how the user experience is impacted by errors. Because they're integrated with our Issues product, you'll be able to see session replays connected to error events on the [Issue Details](/product/issues/issue-details/) page in Sentry. To make sure backend errors are also included in the replay, see our [backend set up instructions](/product/session-replay/web/getting-started/#replays-for-backend-errors). ![Session Replay User Interface](./img/session-replay.png) diff --git a/docs/product/explore/session-replay/mobile/performance-overhead.mdx b/docs/product/session-replay/mobile/performance-overhead.mdx similarity index 93% rename from docs/product/explore/session-replay/mobile/performance-overhead.mdx rename to docs/product/session-replay/mobile/performance-overhead.mdx index a04feb99b04247..e197c7c3953241 100644 --- a/docs/product/explore/session-replay/mobile/performance-overhead.mdx +++ b/docs/product/session-replay/mobile/performance-overhead.mdx @@ -20,7 +20,7 @@ Sentry's Session Replay SDK takes several measures to avoid negatively impacting - When sending a replay segment, the screenshots are further compressed into an `mp4` video file using `h.264` compression with a 75 kbps bitrate (the default behavior). This ensures a small payload size while preserving video quality. We observed nearly 5x reduction in size when compressing five screenshots into a video segment. - The video segment, along with other debugging information (such as breadcrumbs), is gzip-compressed on the client before transmission over HTTP. This compression is performed on a background thread, ensuring the application's main thread remains unaffected. - To minimize disk space usage, screenshots and video segment files are deleted from the disk upon successful upload. -- Sentry’s event ingestion infrastructure uses [distributed Points-of-Presence (PoPs)](https://blog.sentry.io/2022/03/31/sentry-points-of-presence-how-we-built-a-distributed-ingestion/) which place ingestion servers around the world and close to your users. When a Session Replay event is transmitted, the user’s device connects and transmits the event payload to the closest PoP available for their region. This greatly reduces end-to-end latency and minimizes the amount of networking overhead placed on the device. +- Sentry’s event ingestion infrastructure uses [distributed Points-of-Presence (PoPs)](https://blog.sentry.io/sentry-points-of-presence-how-we-built-a-distributed-ingestion/) which place ingestion servers around the world and close to your users. When a Session Replay event is transmitted, the user’s device connects and transmits the event payload to the closest PoP available for their region. This greatly reduces end-to-end latency and minimizes the amount of networking overhead placed on the device. - The SDK is built to gracefully downgrade when needed. In the event of sending too many replay events and hitting Sentry's rate limit, the SDK will disable recording to make sure the rate limit is respected. Once the rate limit is lifted, the SDK will continue recording. ## Factors in Performance Overhead diff --git a/docs/product/explore/session-replay/replay-details.mdx b/docs/product/session-replay/replay-details.mdx similarity index 100% rename from docs/product/explore/session-replay/replay-details.mdx rename to docs/product/session-replay/replay-details.mdx diff --git a/docs/product/explore/session-replay/replay-page-and-filters.mdx b/docs/product/session-replay/replay-page-and-filters.mdx similarity index 84% rename from docs/product/explore/session-replay/replay-page-and-filters.mdx rename to docs/product/session-replay/replay-page-and-filters.mdx index 73c17b1943dc9b..db3d2ccf227530 100644 --- a/docs/product/explore/session-replay/replay-page-and-filters.mdx +++ b/docs/product/session-replay/replay-page-and-filters.mdx @@ -26,11 +26,11 @@ By default, the IP address is used to identify each replay on this page. This ca Replays can appear on this page while they’re still in progress. You will see a LIVE indicator for replays that are still in progress. You can’t delete in-progress replays. -Each replay will bring users to the [**Replay Details**](/product/explore/session-replay/web/replay-details/) page. +Each replay will bring users to the [**Replay Details**](/product/session-replay/web/replay-details/) page. ## Filtering Replays -All replays have built-in key fields, and may have [custom tags](/platform-redirect/?next=/enriching-events/tags/) if you have them set up. The search bar operates similarly to the one in the Discover [Query Builder](/product/explore/discover-queries/query-builder/#filter-by-search-conditions). Use it to search for keys and specific values. This will filter down your list of replays so you can quickly find the ones with the criteria you care about. For example, you can refine your replays search to a specific browser by using `browser.version:` as a key field and assigning the version as a value. For a list of all the built-in key fields and replay properties, check out our [Searchable Properties](/concepts/search/searchable-properties/session-replay/) documentation. +All replays have built-in key fields, and may have [custom tags](/platform-redirect/?next=/enriching-events/tags/) if you have them set up. The search bar operates similarly to the one in the Discover [Query Builder](/product/discover-queries/query-builder/#filter-by-search-conditions). Use it to search for keys and specific values. This will filter down your list of replays so you can quickly find the ones with the criteria you care about. For example, you can refine your replays search to a specific browser by using `browser.version:` as a key field and assigning the version as a value. For a list of all the built-in key fields and replay properties, check out our [Searchable Properties](/concepts/search/searchable-properties/session-replay/) documentation. ![Highlight the Search Filters input on the Session Replay Index Page](./img/replay-index-filtering.png) @@ -40,7 +40,7 @@ Replays can be deleted either individually or in bulk. Deleting replays in bulk When a replay is deleted, it is permanently removed from Sentry's servers, with the exception of its metadata. The metadata rows are archived and remain inaccessible to users. They are retained only until they are removed according to your organization's [data retention policy](https://sentry.io/security/#data-retention). These metadata rows may also be eagerly deleted, but doing so requires manual intervention. To request this, please file a support ticket by emailing support@sentry.io. -To delete a [single replay](/product/explore/session-replay/web/replay-details/#delete-replays), go to the Replay Details page and click the "Delete" link, which is located under the "..." (more options) button. +To delete a [single replay](/product/session-replay/web/replay-details/#delete-replays), go to the Replay Details page and click the "Delete" link, which is located under the "..." (more options) button. To delete multiple replays at once, go to the **Replay** page and use the checkboxes next to each replay row to select the ones you want to delete. Then, click the "Delete" button to remove the selected replays. Deleting a large number of replays takes some time to complete. If a job is running you will see a banner at the top of the Replay list and a link to 'Track Progress'. You can also visit Settings > Project > MyProject > Replays to see the history of previous deletion jobs. diff --git a/docs/product/explore/session-replay/web/img/session-replay-what-is-a-replay.png b/docs/product/session-replay/web/img/session-replay-what-is-a-replay.png similarity index 100% rename from docs/product/explore/session-replay/web/img/session-replay-what-is-a-replay.png rename to docs/product/session-replay/web/img/session-replay-what-is-a-replay.png diff --git a/docs/product/explore/session-replay/web/img/session-replay.png b/docs/product/session-replay/web/img/session-replay.png similarity index 100% rename from docs/product/explore/session-replay/web/img/session-replay.png rename to docs/product/session-replay/web/img/session-replay.png diff --git a/docs/product/explore/session-replay/web/index.mdx b/docs/product/session-replay/web/index.mdx similarity index 95% rename from docs/product/explore/session-replay/web/index.mdx rename to docs/product/session-replay/web/index.mdx index a3381ea6d46728..ed4360525f1600 100644 --- a/docs/product/explore/session-replay/web/index.mdx +++ b/docs/product/session-replay/web/index.mdx @@ -12,7 +12,7 @@ Session Replay allows you to see video-like reproductions of user sessions which Session Replay for web now includes an AI-powered replay summary that automatically analyzes what happened during a user session, and gives a short play-by-play to help debug issues faster. Rather than watch an entire replay, you can now get a quick overview of what happened and focus on the specific interactions that led to the issue. This feature requires the **Show Generative AI Features** setting to be enabled in **Settings > General**. -Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/dashboards/sentry-dashboards/transaction-summary/) page. For [backend error replays](/product/explore/session-replay/web/getting-started/#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](/product/issues/issue-details/breadcrumbs/), and errors. +Replays are integrated with other parts of the Sentry product so you can see how the user experience is impacted by errors and slow transactions. You'll see session replays associated with error events on the [Issue Details](/product/issues/issue-details/) page, and those associated with slow transactions on the [Transaction Summary](/product/dashboards/sentry-dashboards/transaction-summary/) page. For [backend error replays](/product/session-replay/web/getting-started/#replays-for-backend-errors), any contributing backend errors will be included in the replay's timeline, [breadcrumbs](/product/issues/issue-details/breadcrumbs/), and errors. ![Session Replay User Interface](./img/session-replay.png) diff --git a/docs/product/explore/session-replay/web/performance-overhead.mdx b/docs/product/session-replay/web/performance-overhead.mdx similarity index 95% rename from docs/product/explore/session-replay/web/performance-overhead.mdx rename to docs/product/session-replay/web/performance-overhead.mdx index 61aea41d514a4d..0dea55e3850bf4 100644 --- a/docs/product/explore/session-replay/web/performance-overhead.mdx +++ b/docs/product/session-replay/web/performance-overhead.mdx @@ -21,7 +21,7 @@ Sentry's Session Replay SDK takes several measures to avoid negatively impacting - Once the initial DOM tree is snapshotted, the SDK records and transmits _changes_ (deltas) to the DOM rather than snapshotting the entire tree again. This ensures the smallest amount of state is transmitted to facilitate playback. Additionally, the SDK doesn't spend CPU cycles scanning for changes itself; instead it listens for changes emitted by [`MutationObserver`](https://developer.mozilla.org/en-US/docs/Web/API/MutationObserver), an internal browser API. - DOM content itself is gzip compressed client-side before transmission over HTTP. The compression operation is executed in a background thread using a [Web Worker](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Using_web_workers), which means the browser’s UI thread is unaffected. - The SDK doesn't cause the browser to download and transmit other static assets, like images, video, etc. Instead during playback, those assets are fetched directly from the original host server. -- Sentry’s event ingestion infrastructure uses [distributed Points-of-Presence (PoPs)](https://blog.sentry.io/2022/03/31/sentry-points-of-presence-how-we-built-a-distributed-ingestion/) which place ingestion servers around the world and close to your users. When a Session Replay event is transmitted, the user’s browser connects and transmits the event payload to the closest PoP available for their region. This greatly reduces end-to-end latency and minimizes the amount of networking overhead placed on the browser. +- Sentry’s event ingestion infrastructure uses [distributed Points-of-Presence (PoPs)](https://blog.sentry.io/sentry-points-of-presence-how-we-built-a-distributed-ingestion/) which place ingestion servers around the world and close to your users. When a Session Replay event is transmitted, the user’s browser connects and transmits the event payload to the closest PoP available for their region. This greatly reduces end-to-end latency and minimizes the amount of networking overhead placed on the browser. - The SDK is built to gracefully downgrade when needed. In the event several thousand DOM mutations happen at once, the SDK will disable recording to make sure recording the website doesn't further degrade user experience. The [mutation limit values are configurable](/platforms/javascript/session-replay/configuration/#mutation-limits). ## Factors in Performance Overhead diff --git a/docs/product/size-analysis/index.mdx b/docs/product/size-analysis/index.mdx index 28dab83c520c26..96835ae9b42e6f 100644 --- a/docs/product/size-analysis/index.mdx +++ b/docs/product/size-analysis/index.mdx @@ -1,6 +1,7 @@ --- title: Size Analysis -sidebar_order: 136 +sidebar_order: 340 +sidebar_section: measure description: Monitor mobile builds for size changes before they reach users. og_image: /og-images/product-size-analysis.png new: true diff --git a/docs/product/snapshots/index.mdx b/docs/product/snapshots/index.mdx index 953b833a376448..2f0df740ed49c4 100644 --- a/docs/product/snapshots/index.mdx +++ b/docs/product/snapshots/index.mdx @@ -1,6 +1,7 @@ --- title: Snapshots -sidebar_order: 138 +sidebar_order: 120 +sidebar_section: detect description: Catch visual changes on every pull request with snapshots. beta: true --- diff --git a/docs/product/stats/index.mdx b/docs/product/stats/index.mdx index 083f8efdc7b9e7..c789bc4cdae3b2 100644 --- a/docs/product/stats/index.mdx +++ b/docs/product/stats/index.mdx @@ -3,7 +3,8 @@ title: Stats description: >- The Sentry Stats page displays important metrics such as Usage, and Issues that help teams track project health. Learn how to get started here. -sidebar_order: 130 +sidebar_order: 330 +sidebar_section: measure og_image: /og-images/product-stats.png --- diff --git a/docs/product/explore/trace-explorer/img/Trace_Explorer_home.png b/docs/product/trace-explorer/img/Trace_Explorer_home.png similarity index 100% rename from docs/product/explore/trace-explorer/img/Trace_Explorer_home.png rename to docs/product/trace-explorer/img/Trace_Explorer_home.png diff --git a/docs/product/explore/trace-explorer/img/Trace_explorer_alerts.png b/docs/product/trace-explorer/img/Trace_explorer_alerts.png similarity index 100% rename from docs/product/explore/trace-explorer/img/Trace_explorer_alerts.png rename to docs/product/trace-explorer/img/Trace_explorer_alerts.png diff --git a/docs/product/explore/trace-explorer/img/Trace_explorer_low_samples.png b/docs/product/trace-explorer/img/Trace_explorer_low_samples.png similarity index 100% rename from docs/product/explore/trace-explorer/img/Trace_explorer_low_samples.png rename to docs/product/trace-explorer/img/Trace_explorer_low_samples.png diff --git a/docs/product/explore/trace-explorer/img/Trace_explorer_low_samples_old.png b/docs/product/trace-explorer/img/Trace_explorer_low_samples_old.png similarity index 100% rename from docs/product/explore/trace-explorer/img/Trace_explorer_low_samples_old.png rename to docs/product/trace-explorer/img/Trace_explorer_low_samples_old.png diff --git a/docs/product/explore/trace-explorer/img/Trace_explorer_search.png b/docs/product/trace-explorer/img/Trace_explorer_search.png similarity index 100% rename from docs/product/explore/trace-explorer/img/Trace_explorer_search.png rename to docs/product/trace-explorer/img/Trace_explorer_search.png diff --git a/docs/product/explore/trace-explorer/img/attribute_comparison.png b/docs/product/trace-explorer/img/attribute_comparison.png similarity index 100% rename from docs/product/explore/trace-explorer/img/attribute_comparison.png rename to docs/product/trace-explorer/img/attribute_comparison.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer01.png b/docs/product/trace-explorer/img/trace-explorer01.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer01.png rename to docs/product/trace-explorer/img/trace-explorer01.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer02.png b/docs/product/trace-explorer/img/trace-explorer02.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer02.png rename to docs/product/trace-explorer/img/trace-explorer02.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer03.png b/docs/product/trace-explorer/img/trace-explorer03.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer03.png rename to docs/product/trace-explorer/img/trace-explorer03.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer04.png b/docs/product/trace-explorer/img/trace-explorer04.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer04.png rename to docs/product/trace-explorer/img/trace-explorer04.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer05.png b/docs/product/trace-explorer/img/trace-explorer05.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer05.png rename to docs/product/trace-explorer/img/trace-explorer05.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer06.png b/docs/product/trace-explorer/img/trace-explorer06.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer06.png rename to docs/product/trace-explorer/img/trace-explorer06.png diff --git a/docs/product/explore/trace-explorer/img/trace-explorer07.png b/docs/product/trace-explorer/img/trace-explorer07.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace-explorer07.png rename to docs/product/trace-explorer/img/trace-explorer07.png diff --git a/docs/product/explore/trace-explorer/img/trace_explorer_save.png b/docs/product/trace-explorer/img/trace_explorer_save.png similarity index 100% rename from docs/product/explore/trace-explorer/img/trace_explorer_save.png rename to docs/product/trace-explorer/img/trace_explorer_save.png diff --git a/docs/product/explore/trace-explorer/index.mdx b/docs/product/trace-explorer/index.mdx similarity index 97% rename from docs/product/explore/trace-explorer/index.mdx rename to docs/product/trace-explorer/index.mdx index eee36ee77f9c5a..7342758ea27311 100644 --- a/docs/product/explore/trace-explorer/index.mdx +++ b/docs/product/trace-explorer/index.mdx @@ -1,6 +1,7 @@ --- title: Traces and Spans -sidebar_order: 31 +sidebar_order: 200 +sidebar_section: debug description: >- Learn how to use Sentry's Trace Explorer to search span data, find distributed traces, and debug performance issues across your entire application stack. @@ -156,7 +157,7 @@ If, for example, you see that 80% of spans in your selection come from a specifi ## Cross-Event Querying -Cross-Event Querying lets you refine your span search by joining on additional Sentry event types connected by the same trace. This is useful when the data you need to filter on lives in a related event. For example, finding backend services that logged errors, or locating a representative trace based on attributes from an [Application Metrics](/product/explore/metrics/) sample, where the data is not in the span itself. +Cross-Event Querying lets you refine your span search by joining on additional Sentry event types connected by the same trace. This is useful when the data you need to filter on lives in a related event. For example, finding backend services that logged errors, or locating a representative trace based on attributes from an [Application Metrics](/product/metrics/) sample, where the data is not in the span itself. Spans, logs, and application metrics are supported as join targets. @@ -181,7 +182,7 @@ The span results now include only traces that also contain at least one error lo ### Example: Finding a Comparable Trace for a Metric -[Application Metrics](/product/explore/metrics/) are typically sampled at 100%, while traces are sampled at a much lower rate, so a specific metric sample often won't have a trace attached to it. Joining on **Application Metrics** lets you search directly for traces that contain a matching metric event, giving you a comparable trace for the pattern you're investigating: +[Application Metrics](/product/metrics/) are typically sampled at 100%, while traces are sampled at a much lower rate, so a specific metric sample often won't have a trace attached to it. Joining on **Application Metrics** lets you search directly for traces that contain a matching metric event, giving you a comparable trace for the pattern you're investigating: 1. In Trace Explorer, click the **Plus (+)** next to the search bar and choose **Application Metrics**. 2. Pick the metric you want to trace back (for example, `checkout.duration`). diff --git a/docs/product/user-feedback/index.mdx b/docs/product/user-feedback/index.mdx index 15124fabe473f1..6fa7cc3995de5e 100644 --- a/docs/product/user-feedback/index.mdx +++ b/docs/product/user-feedback/index.mdx @@ -1,6 +1,7 @@ --- title: User Feedback -sidebar_order: 65 +sidebar_order: 110 +sidebar_section: detect description: Learn how you can view and triage user feedback submissions. og_image: /og-images/product-user-feedback.png --- @@ -9,7 +10,7 @@ Sentry automatically detects errors thrown by your application, such as performa That's where Sentry's User Feedback Widget and Crash-Report Modal features come in. Setting up one or both lets you collect feedback from your end-users when they run into bugs in your application. Sentry then links that feedback to available rich debugging context, including errors, replays, and tags such as URL, allowing you to get to the root of the problem faster. -For example, using [Session Replay](/product/explore/session-replay/) with the User Feedback Widget could save you time, helping you quickly understand the context of the user problem by seeing exactly what they experienced before submitting their feedback. +For example, using [Session Replay](/product/session-replay/) with the User Feedback Widget could save you time, helping you quickly understand the context of the user problem by seeing exactly what they experienced before submitting their feedback. ## User Feedback Widget @@ -23,7 +24,7 @@ Feedback collected via the Feedback Widget may have some or all of the following - Screenshot from the user - User email - Associated replay event (with up to 60 seconds of replay recording before the user submitted the feedback) - - Learn more about how to set up Session Replay [here](/product/explore/session-replay/getting-started/). + - Learn more about how to set up Session Replay [here](/product/session-replay/getting-started/). - URL of the page the user was on when they submitted the feedback - Tags diff --git a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx index cf1edb319a8bb4..d4366a345b3737 100644 --- a/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx +++ b/docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx @@ -35,7 +35,7 @@ Navigate to your project- or organization-settings, click _Security and Privacy_ As soon as you press _Save_, Sentry will attempt to find all credit card numbers in your events going forward, and replace them with a series of `******`. -For a more verbose tutorial check out [this blogpost](https://blog.sentry.io/2020/07/02/sentry-data-wash-now-offering-advanced-scrubbing/). +For a more verbose tutorial check out [this blogpost](https://blog.sentry.io/sentry-data-wash-now-offering-advanced-scrubbing/). Rules generally consist of three parts: @@ -244,7 +244,7 @@ The following limitations generally apply to all server-side data scrubbing, be ## Data Scrubbing for Logs -[Logs](/product/explore/logs/) will honor the default [Server-Side Data Scrubbing rules](/security-legal-pii/scrubbing/server-side-scrubbing/#geographic-information) applied to your projects. To add advanced data scrubbing rules for Logs, start by choosing the dataset. +[Logs](/product/logs/) will honor the default [Server-Side Data Scrubbing rules](/security-legal-pii/scrubbing/server-side-scrubbing/#geographic-information) applied to your projects. To add advanced data scrubbing rules for Logs, start by choosing the dataset. ![Add an advanced data scrubbing rule dialog showing dataset selection, method, data type, and source fields](img/data_scrub_rule.png) diff --git a/includes/apple-platform-getting-started.mdx b/includes/apple-platform-getting-started.mdx index 46f809eab5a2f0..f409f96856fbe1 100644 --- a/includes/apple-platform-getting-started.mdx +++ b/includes/apple-platform-getting-started.mdx @@ -22,7 +22,7 @@ The support for [visionOS](https://developer.apple.com/visionos/) is currently e -In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/explore/profiling/). +In addition to capturing errors, you can monitor interactions between multiple services or applications by [enabling tracing](/concepts/key-terms/tracing/). You can also collect and analyze performance profiles from real users with [profiling](/product/profiling/). diff --git a/includes/docs-changelog.mdx b/includes/docs-changelog.mdx index 834e5fa49ec1a1..b95d44f4e89b87 100644 --- a/includes/docs-changelog.mdx +++ b/includes/docs-changelog.mdx @@ -230,8 +230,8 @@ - [Dashboards](/product/dashboards/) - [Widget Builder](/product/dashboards/widget-builder/) - [Widget Library](/product/dashboards/widget-library/) -- [Query Builder](/product/explore/discover-queries/query-builder/) -- [Adding Query Equations](/product/explore/discover-queries/query-builder/query-equations/) +- [Query Builder](/product/discover-queries/query-builder/) +- [Adding Query Equations](/product/discover-queries/query-builder/query-equations/) - [Queries](/product/dashboards/sentry-dashboards/backend/queries/) - [Sentry Dashboards](/product/dashboards/sentry-dashboards/) - [Transaction Summary](/product/dashboards/sentry-dashboards/transaction-summary/) diff --git a/middleware.ts b/middleware.ts index e6bf71e8648315..e2bf6e1c51d310 100644 --- a/middleware.ts +++ b/middleware.ts @@ -2578,27 +2578,27 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ }, { from: '/profiling/', - to: '/product/explore/profiling/', + to: '/product/profiling/', }, { from: '/profiling/performance-overhead/', - to: '/product/explore/profiling/performance-overhead/', + to: '/product/profiling/performance-overhead/', }, { from: '/profiling/setup/', - to: '/product/explore/profiling/getting-started/', + to: '/product/profiling/getting-started/', }, { from: '/profiling/getting-started/', - to: '/product/explore/profiling/getting-started/', + to: '/product/profiling/getting-started/', }, { from: '/profiling/mobile-app-profiling/', - to: '/product/explore/profiling/mobile-app-profiling/', + to: '/product/profiling/mobile-app-profiling/', }, { from: '/profiling/mobile-app-profiling/metrics/', - to: '/product/explore/profiling/mobile-app-profiling/metrics/', + to: '/product/profiling/mobile-app-profiling/metrics/', }, { @@ -2663,39 +2663,39 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ }, { from: '/product/discover/', - to: '/product/explore/discover-queries/', + to: '/product/discover-queries/', }, { from: '/workflow/discover/', - to: '/product/explore/discover-queries/', + to: '/product/discover-queries/', }, { from: '/workflow/discover2/', - to: '/product/explore/discover-queries/', + to: '/product/discover-queries/', }, { from: '/performance-monitoring/discover/', - to: '/product/explore/discover-queries/', + to: '/product/discover-queries/', }, { from: '/performance/discover/', - to: '/product/explore/discover-queries/', + to: '/product/discover-queries/', }, { from: '/guides/discover/', - to: '/product/explore/discover-queries/uncover-trends/', + to: '/product/discover-queries/uncover-trends/', }, { from: '/product/sentry-basics/guides/discover/', - to: '/product/explore/discover-queries/uncover-trends/', + to: '/product/discover-queries/uncover-trends/', }, { from: '/workflow/discover2/query-builder/', - to: '/product/explore/discover-queries/query-builder/', + to: '/product/discover-queries/query-builder/', }, { from: '/performance-monitoring/discover-queries/query-builder/', - to: '/product/explore/discover-queries/query-builder/', + to: '/product/discover-queries/query-builder/', }, { from: '/product/crons/alerts/', @@ -3474,22 +3474,8 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ from: '/product/sentry-mcp/', to: 'https://mcp.sentry.dev', }, - { - from: '/product/metrics/', - to: '/product/explore/metrics/', - }, - { - from: '/product/profiling/', - to: '/product/explore/profiling/', - }, - { - from: '/product/discover-queries/', - to: '/product/explore/discover-queries/', - }, - { - from: '/product/session-replay/', - to: '/product/explore/session-replay/', - }, + // Removed: /product/metrics/, /product/profiling/, /product/discover-queries/, + // /product/session-replay/ are now canonical paths (previously redirected to /product/explore/*) { from: '/enriching-error-data/advanced-datascrubbing/', to: '/concepts/data-management/advanced-datascrubbing/', @@ -3583,7 +3569,7 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ to: '/product/dashboards/sentry-dashboards/backend/queues/', }, { - from: '/product/explore/session-replay/protecting-user-privacy/', + from: '/product/session-replay/protecting-user-privacy/', to: '/security-legal-pii/scrubbing/protecting-user-privacy/', }, { @@ -3627,8 +3613,8 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ to: '/concepts/data-management/event-grouping/', }, { - from: '/product/explore/session-replay/performance-overhead/', - to: '/product/explore/session-replay/web/performance-overhead/', + from: '/product/session-replay/performance-overhead/', + to: '/product/session-replay/web/performance-overhead/', }, { from: '/organization/integrations/project-mgmt/jira/', @@ -3639,31 +3625,31 @@ const USER_DOCS_REDIRECTS: Redirect[] = [ to: '/integrations/source-code-mgmt/', }, { - from: '/product/explore/session-replay/getting-started/', - to: '/product/explore/session-replay/', + from: '/product/session-replay/getting-started/', + to: '/product/session-replay/', }, { - from: '/product/explore/session-replay/web/getting-started/', - to: '/product/explore/session-replay/web/', + from: '/product/session-replay/web/getting-started/', + to: '/product/session-replay/web/', }, { - from: '/product/explore/session-replay/web/replay-page-and-filters/', - to: '/product/explore/session-replay/replay-page-and-filters/', + from: '/product/session-replay/web/replay-page-and-filters/', + to: '/product/session-replay/replay-page-and-filters/', }, { - from: '/product/explore/session-replay/web/replay-details/', - to: '/product/explore/session-replay/replay-details/', + from: '/product/session-replay/web/replay-details/', + to: '/product/session-replay/replay-details/', }, { - from: '/product/explore/session-replay/hydration-errors/', + from: '/product/session-replay/hydration-errors/', to: '/product/issues/issue-details/replay-issues/hydration-error/', }, { - from: '/product/explore/session-replay/rage-dead-clicks/', + from: '/product/session-replay/rage-dead-clicks/', to: '/product/issues/issue-details/replay-issues/rage-clicks/', }, { - from: '/product/explore/session-replay/privacy/', + from: '/product/session-replay/privacy/', to: '/security-legal-pii/scrubbing/protecting-user-privacy/', }, { diff --git a/platform-includes/metrics/options/godot.mdx b/platform-includes/metrics/options/godot.mdx index ff4b9fdadfdf11..0690eb72af4c1e 100644 --- a/platform-includes/metrics/options/godot.mdx +++ b/platform-includes/metrics/options/godot.mdx @@ -1,4 +1,4 @@ -The following configuration options are available for Sentry's [Application Metrics](/product/explore/metrics/) in Godot Engine: +The following configuration options are available for Sentry's [Application Metrics](/product/metrics/) in Godot Engine: | Option | Description | Default | | ---------------------- | ------------------------------------------------------------------ | ------- | diff --git a/platform-includes/metrics/options/unreal.mdx b/platform-includes/metrics/options/unreal.mdx index dbacb87adeb822..fc0252dac3c532 100644 --- a/platform-includes/metrics/options/unreal.mdx +++ b/platform-includes/metrics/options/unreal.mdx @@ -1,4 +1,4 @@ -The following configuration options are available for Sentry's [Application Metrics](/product/explore/metrics/) in Unreal Engine: +The following configuration options are available for Sentry's [Application Metrics](/product/metrics/) in Unreal Engine: | Option | Description | Default | |--------|-------------|---------| diff --git a/platform-includes/metrics/usage/rust.mdx b/platform-includes/metrics/usage/rust.mdx index 0c8622402d6b4c..ac21ddcecd4eb1 100644 --- a/platform-includes/metrics/usage/rust.mdx +++ b/platform-includes/metrics/usage/rust.mdx @@ -1,10 +1,10 @@ -The SDK's [`sentry::metrics` module](https://docs.rs/sentry/latest/sentry/metrics/index.html) contains functions for capturing each of the [three metric types](/product/explore/metrics/#metric-types) that Sentry supports. +The SDK's [`sentry::metrics` module](https://docs.rs/sentry/latest/sentry/metrics/index.html) contains functions for capturing each of the [three metric types](/product/metrics/#metric-types) that Sentry supports. Metrics are automatically associated with the trace and, if applicable, the span they are captured within. ### Capture a Counter -Capture [counter metrics](/product/explore/metrics/#counters) using [`metrics::counter`](https://docs.rs/sentry/latest/sentry/metrics/fn.counter.html). +Capture [counter metrics](/product/metrics/#counters) using [`metrics::counter`](https://docs.rs/sentry/latest/sentry/metrics/fn.counter.html). Counters track occurrences, such as handled HTTP requests, and are always unitless. @@ -16,7 +16,7 @@ metrics::counter("http.requests", 1).capture(); ### Capture a Gauge -Capture [gauge metrics](/product/explore/metrics/#gauges) using [`metrics::gauge`](https://docs.rs/sentry/latest/sentry/metrics/fn.gauge.html). +Capture [gauge metrics](/product/metrics/#gauges) using [`metrics::gauge`](https://docs.rs/sentry/latest/sentry/metrics/fn.gauge.html). Gauges track current state or level, such as queue depth or active connections, and support [units](https://docs.rs/sentry/latest/sentry/metrics/struct.GaugeMetric.html#method.unit). @@ -28,7 +28,7 @@ metrics::gauge("queue.depth", 42).capture(); ### Distribution -Capture [distribution metrics](/product/explore/metrics/#distributions) using [`metrics::distribution`](https://docs.rs/sentry/latest/sentry/metrics/fn.distribution.html). +Capture [distribution metrics](/product/metrics/#distributions) using [`metrics::distribution`](https://docs.rs/sentry/latest/sentry/metrics/fn.distribution.html). Distributions track values that vary and need statistical analysis, such as response times or payload sizes, and they support [units](https://docs.rs/sentry/latest/sentry/metrics/struct.DistributionMetric.html#method.unit). diff --git a/platform-includes/profiling/automatic-instrumentation-headers/_default.mdx b/platform-includes/profiling/automatic-instrumentation-headers/_default.mdx index 1233b9c896c633..965bd9c618539f 100644 --- a/platform-includes/profiling/automatic-instrumentation-headers/_default.mdx +++ b/platform-includes/profiling/automatic-instrumentation-headers/_default.mdx @@ -123,6 +123,6 @@ app.Use(async (context, next) => { -If you're using a hosting provider that doesn't allow custom response headers (some static hosting services, corporate proxies, etc.), browser profiling won't be available for your application. Consider using Sentry's [backend profiling](/product/explore/profiling/) for your server-side code instead. +If you're using a hosting provider that doesn't allow custom response headers (some static hosting services, corporate proxies, etc.), browser profiling won't be available for your application. Consider using Sentry's [backend profiling](/product/profiling/) for your server-side code instead. diff --git a/platform-includes/profiling/browser-profiling/javascript.mdx b/platform-includes/profiling/browser-profiling/javascript.mdx index 8ca7c1bd17d77d..0ea00c15b57afe 100644 --- a/platform-includes/profiling/browser-profiling/javascript.mdx +++ b/platform-includes/profiling/browser-profiling/javascript.mdx @@ -4,7 +4,7 @@ Browser Profiling is currently in beta. Beta features are still in progress and -[Profiling](/product/explore/profiling/) captures function-level data from your production code to enable you to fine-tune your app's performance. It tracks what's being called, how often, and where. In the browser, this helps you pinpoint causes of UI jank, understand why metrics like [Interaction to Next Paint (INP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) are slow, or identify long tasks blocking repaints and causing frame drops. +[Profiling](/product/profiling/) captures function-level data from your production code to enable you to fine-tune your app's performance. It tracks what's being called, how often, and where. In the browser, this helps you pinpoint causes of UI jank, understand why metrics like [Interaction to Next Paint (INP)](/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/#interaction-to-next-paint-inp) are slow, or identify long tasks blocking repaints and causing frame drops. diff --git a/platform-includes/profiling/index/why-profiling/_default.mdx b/platform-includes/profiling/index/why-profiling/_default.mdx index d1f32a144cce47..f57b8f7c3b2746 100644 --- a/platform-includes/profiling/index/why-profiling/_default.mdx +++ b/platform-includes/profiling/index/why-profiling/_default.mdx @@ -1 +1 @@ -With [profiling](/product/explore/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. [Sentry's profiler](https://sentry.io/for/profiling/) captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and increase user satisfaction, as well as drive down costs. +With [profiling](/product/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. [Sentry's profiler](https://sentry.io/for/profiling/) captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and increase user satisfaction, as well as drive down costs. diff --git a/platform-includes/profiling/index/why-profiling/javascript.mdx b/platform-includes/profiling/index/why-profiling/javascript.mdx index 0eb76e0f6f57d9..8d270cd10e0ac8 100644 --- a/platform-includes/profiling/index/why-profiling/javascript.mdx +++ b/platform-includes/profiling/index/why-profiling/javascript.mdx @@ -1,3 +1,3 @@ -With [profiling](/product/explore/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. Sentry's profiler captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and user satisfaction. +With [profiling](/product/profiling/), Sentry tracks your software's performance by sampling your program's call stack in a variety of environments. This feature collects function-level information about your code and enables you to fine-tune your program's performance. Sentry's profiler captures function calls and their exact locations, aggregates them, and shows you the most common code paths of your program. This highlights areas you could optimize to help increase both the performance of your code and user satisfaction. In a browser environment, profiling can help you pinpoint causes of UI jank, surface why values like interaction to next paint (INP) are performing poorly, or why a long task was keeping the browser from repainting the screen and causing frame drops. All of this information enables you to fix real world performance issues and deliver a snappier user experience to your users. diff --git a/redirects.js b/redirects.js index dc45e24574aa83..ed8dfc4e15e987 100644 --- a/redirects.js +++ b/redirects.js @@ -1646,21 +1646,34 @@ const userDocsRedirects = [ destination: '/platforms/javascript/guides/cloudflare/frameworks/hydrogen-react-router/', }, + // Flatten Explore: redirect old /product/explore/* paths to new /product/* paths { - source: '/product/metrics/:path*', - destination: '/product/explore/metrics/:path*', + source: '/product/explore/metrics/:path*', + destination: '/product/metrics/:path*', }, { - source: '/product/profiling/:path*', - destination: '/product/explore/profiling/:path*', + source: '/product/explore/profiling/:path*', + destination: '/product/profiling/:path*', }, { - source: '/product/discover-queries/:path*', - destination: '/product/explore/discover-queries/:path*', + source: '/product/explore/discover-queries/:path*', + destination: '/product/discover-queries/:path*', }, { - source: '/product/session-replay/:path*', - destination: '/product/explore/session-replay/:path*', + source: '/product/explore/session-replay/:path*', + destination: '/product/session-replay/:path*', + }, + { + source: '/product/explore/trace-explorer/:path*', + destination: '/product/trace-explorer/:path*', + }, + { + source: '/product/explore/logs/:path*', + destination: '/product/logs/:path*', + }, + { + source: '/product/explore', + destination: '/product/trace-explorer/', }, { source: '/platforms/javascript/best-practices/browser-extensions/', @@ -2133,11 +2146,15 @@ const userDocsRedirects = [ // Redirects for Trace Explorer { source: '/product/explore/traces', - destination: '/product/explore/trace-explorer/', + destination: '/product/trace-explorer/', }, { source: '/product/explore/new-trace-explorer', - destination: '/product/explore/trace-explorer/', + destination: '/product/trace-explorer/', + }, + { + source: '/product/traces', + destination: '/product/trace-explorer/', }, { source: '/organization/integrations/expo/', @@ -2252,15 +2269,7 @@ const userDocsRedirects = [ source: '/product/monitors-and-alerts/alerts/best-practices/', destination: '/product/monitors-and-alerts/alerts/', }, - // DOCS-2550: /product/logs/ moved under /product/explore/ - { - source: '/product/logs/', - destination: '/product/explore/logs/', - }, - { - source: '/product/logs/:path*', - destination: '/product/explore/logs/:path*', - }, + // DOCS-2550: /product/logs/ redirects now handled in the flatten-explore block above // DOCS-2227: retention-priorities page removed; dynamic-sampling is the closest equivalent { source: '/product/performance/retention-priorities/', diff --git a/src/components/featureInfo.tsx b/src/components/featureInfo.tsx index 1aee98e6af0d4b..f451575def3369 100644 --- a/src/components/featureInfo.tsx +++ b/src/components/featureInfo.tsx @@ -63,7 +63,7 @@ const FEATURE_DATA: Record< }, sessionReplay: { title: 'Session Replay', - link: '/product/explore/session-replay/web', + link: '/product/session-replay/web', learnMore: "Get to the root cause of an issue faster by viewing a video-like reproduction of what was happening in the user's browser before, during, and after the problem.", findInSentry: ( @@ -79,7 +79,7 @@ const FEATURE_DATA: Record< }, logs: { title: 'Logs', - link: '/product/explore/logs', + link: '/product/logs', learnMore: "Centralize and analyze your application logs to correlate them with errors and performance issues. Search, filter, and visualize log data to understand what's happening in your applications.", findInSentry: ( @@ -90,13 +90,13 @@ const FEATURE_DATA: Record< {' '} page and filter by service, environment, or search keywords to view log entries from your application. For an interactive UI walkthrough, click{' '} - here. + here. ), }, profiling: { title: 'Profiling', - link: '/product/explore/profiling/', + link: '/product/profiling/', learnMore: 'Gain deeper insight than traditional tracing without custom instrumentation, letting you discover slow-to-execute or resource-intensive functions in your app.', findInSentry: ( @@ -107,7 +107,7 @@ const FEATURE_DATA: Record< {' '} page, select a transaction, and then a profile ID to view its flame graph. For more information, click{' '} - here. + here. ), }, @@ -129,7 +129,7 @@ const FEATURE_DATA: Record< }, metrics: { title: 'Application Metrics', - link: '/product/explore/metrics', + link: '/product/metrics', learnMore: "Track and analyze custom application metrics, such as response times and database query durations, to understand trends and patterns in your application's performance and behavior over time.", findInSentry: ( @@ -139,7 +139,7 @@ const FEATURE_DATA: Record< Application Metrics {' '} page to view and analyze your metrics. For more details, see this{' '} - interactive walkthrough. + interactive walkthrough. ), }, diff --git a/src/components/home.tsx b/src/components/home.tsx index 9020124ecd2ac8..3569d4e16ea6ae 100644 --- a/src/components/home.tsx +++ b/src/components/home.tsx @@ -219,7 +219,7 @@ export async function Home() { ,{' '} Tracing diff --git a/src/components/sidebar/dynamicNav.tsx b/src/components/sidebar/dynamicNav.tsx index c966b5a69079c9..c20f06c882990d 100644 --- a/src/components/sidebar/dynamicNav.tsx +++ b/src/components/sidebar/dynamicNav.tsx @@ -12,6 +12,11 @@ import type {ExternalSidebarLink} from './types'; const SECTION_LABELS: Record = { features: 'Features', configuration: 'Configuration', + detect: 'Detect', + debug: 'Debug', + measure: 'Measure', + automate: 'Automate', + platform: 'Platform', }; // Section links configuration - sections that should be clickable headers @@ -19,7 +24,15 @@ const SECTION_LINKS: Record = { features: 'features', }; -const SECTION_ORDER = ['features', 'configuration'] as const; +const SECTION_ORDER = [ + 'features', + 'configuration', + 'detect', + 'debug', + 'measure', + 'automate', + 'platform', +] as const; type Node = { [key: string]: any; @@ -31,7 +44,14 @@ type Node = { section_end_divider?: boolean; sidebar_hidden?: boolean; sidebar_order?: number; - sidebar_section?: 'features' | 'configuration'; + sidebar_section?: + | 'features' + | 'configuration' + | 'detect' + | 'debug' + | 'measure' + | 'automate' + | 'platform'; sidebar_title?: string; title?: string; }; diff --git a/src/components/sidebar/types.ts b/src/components/sidebar/types.ts index c383b918046802..0a4ca4328d79d8 100644 --- a/src/components/sidebar/types.ts +++ b/src/components/sidebar/types.ts @@ -45,7 +45,14 @@ export type NavNode = { section_end_divider?: boolean; sidebar_hidden?: boolean; sidebar_order?: number; - sidebar_section?: 'features' | 'configuration'; + sidebar_section?: + | 'features' + | 'configuration' + | 'detect' + | 'debug' + | 'measure' + | 'automate' + | 'platform'; sidebar_title?: string; }; path: string; diff --git a/src/types/frontmatter.ts b/src/types/frontmatter.ts index 0a80ca6c0265bf..2178b8de09a9e4 100644 --- a/src/types/frontmatter.ts +++ b/src/types/frontmatter.ts @@ -104,11 +104,18 @@ export interface FrontMatter { sidebar_order?: number; /** - * Which sidebar section this page belongs to (for platform docs). - * Options: 'features' | 'configuration' - * Defaults to 'features' if not specified. - */ - sidebar_section?: 'features' | 'configuration'; + * Which sidebar section this page belongs to. + * Platform docs use 'features' | 'configuration'. + * Product docs use 'detect' | 'debug' | 'measure' | 'automate' | 'platform'. + */ + sidebar_section?: + | 'features' + | 'configuration' + | 'detect' + | 'debug' + | 'measure' + | 'automate' + | 'platform'; /** * optional sidebar title From 887400f1de742aa81bf6d77b3fcffc8a166845d5 Mon Sep 17 00:00:00 2001 From: "getsantry[bot]" <66042841+getsantry[bot]@users.noreply.github.com> Date: Thu, 25 Jun 2026 18:49:35 +0000 Subject: [PATCH 2/2] [getsentry/action-github-commit] Auto commit --- src/components/featureInfo.tsx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/components/featureInfo.tsx b/src/components/featureInfo.tsx index f451575def3369..c2dbc869d4f70b 100644 --- a/src/components/featureInfo.tsx +++ b/src/components/featureInfo.tsx @@ -106,8 +106,7 @@ const FEATURE_DATA: Record< Profiles {' '} page, select a transaction, and then a profile ID to view its flame graph. For - more information, click{' '} - here. + more information, click here. ), },