Skip to content

feat(Insights): Insights to dashboards EA#16693

Open
sfanahata wants to merge 9 commits intomasterfrom
insights-to-dashboards-EA
Open

feat(Insights): Insights to dashboards EA#16693
sfanahata wants to merge 9 commits intomasterfrom
insights-to-dashboards-EA

Conversation

@sfanahata
Copy link
Contributor

@sfanahata sfanahata commented Mar 5, 2026

DESCRIBE YOUR PR

Massive update:

  1. Move /product/insights/ content into /product/dashboards/
  2. Clean up the content to be relevant to the new version of those pages as dashboards
  3. Update images/arcades

https://sentry-docs-git-insights-to-dashboards-ea.sentry.dev/product/dashboards/
https://sentry-docs-git-insights-to-dashboards-ea.sentry.dev/product/dashboards/sentry-dashboards/

IS YOUR CHANGE URGENT?

Help us prioritize incoming PRs by letting us know when the change needs to go live.

  • Urgent deadline (GA date, etc.):
  • Other deadline: Whenever Insights -> Dashboards goes EA
  • None: Not urgent, can wait up to 1 week+

SLA

  • Teamwork makes the dream work, so please add a reviewer to your PRs.
  • Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.
    Thanks in advance for your help!

PRE-MERGE CHECKLIST

Make sure you've checked the following before merging your changes:

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs (subject matter experts)
  • PR was reviewed and approved by a member of the Sentry docs team

Shannon Anahata added 2 commits March 3, 2026 15:28
…updated dashboards root, custom dashboards, widget builder, widget library for top level dashboard updates. - updated transaction summary and page filters for insights migration updates.
…d redistributed the information in that page to relevant pages still using those metrics. Built out includes to easily distribute and update that information in relevant places.
@vercel
Copy link

vercel bot commented Mar 5, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment Mar 6, 2026 9:46pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview Mar 6, 2026 9:46pm

Request Review

@codeowner-assignment codeowner-assignment bot requested review from a team March 5, 2026 00:05
Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Autofix Details

Bugbot Autofix prepared a fix for the issue found in the latest run.

  • ✅ Fixed: Internal migration tracking document accidentally committed
    • Deleted the internal migration tracking document from the published docs directory.

Create PR

Or push these changes by commenting:

@cursor push 07a339068c
Preview (07a339068c)
diff --git a/docs/product/dashboards/sentry-dashboards/INSIGHTS-TO-SENTRY-DASHBOARDS-MIGRATION.md b/docs/product/dashboards/sentry-dashboards/INSIGHTS-TO-SENTRY-DASHBOARDS-MIGRATION.md
deleted file mode 100644
--- a/docs/product/dashboards/sentry-dashboards/INSIGHTS-TO-SENTRY-DASHBOARDS-MIGRATION.md
+++ /dev/null
@@ -1,194 +1,0 @@
-# Insights → Sentry Dashboards migration
-
-This document tracks link updates, product naming changes, and redirects when migrating from **Insights** to **Sentry dashboards** (`/product/dashboards/sentry-dashboards/`).
-
-## Decisions
-
-- **Path:** Use `sentry-dashboards` (plural). Base path: `/product/dashboards/sentry-dashboards/`.
-- **Images:** Migrate the associated `img` folder with each moved doc as needed.
-- **Performance Overhead:** Page is deleted; merge useful content into Sentry dashboards index or a short note. Add redirect so `/product/insights/performance-overhead/` → `/product/dashboards/sentry-dashboards/`. Update all links that point to it.
-- **Product naming:** Where the product is called "Insights," change to "Sentry dashboards" (or "Sentry Dashboards" as appropriate). Update both links and prose.
-
----
-
-## Path mapping (old → new)
-
-Use this when updating links and when adding redirects (e.g. in `redirects.js` and `src/middleware.ts`).
-
-| Old path | New path |
-|---------|----------|
-| `/product/insights/` | `/product/dashboards/sentry-dashboards/` |
-| `/product/insights/overview/` | `/product/dashboards/sentry-dashboards/` (merged into index) |
-| `/product/insights/overview/transaction-summary/` | `/product/dashboards/sentry-dashboards/transaction-summary/` |
-| `/product/insights/overview/metrics/` | `/product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view` (performance-metrics page retired; content in Transaction Summary) |
-| `/product/insights/overview/filters-display/` | `/product/dashboards/sentry-dashboards/` (page deleted; redirect to index) |
-| `/product/insights/overview/filters-display/widgets/` | `/product/dashboards/sentry-dashboards/` (page deleted; redirect to index) |
-| `/product/insights/getting-started/` | `/product/dashboards/sentry-dashboards/` (Set Up section merged into index; no separate getting-started page) |
-| `/product/insights/performance-overhead/` | `/product/dashboards/sentry-dashboards/` (page deleted; redirect) |
-| `/product/insights/frontend/` | `/product/dashboards/sentry-dashboards/frontend/` |
-| `/product/insights/frontend/web-vitals/` | `/product/dashboards/sentry-dashboards/frontend/web-vitals/` |
-| `/product/insights/frontend/web-vitals/web-vitals-concepts/` | `/product/dashboards/sentry-dashboards/frontend/web-vitals/web-vitals-concepts/` |
-| `/product/insights/frontend/network-requests/` | `/product/dashboards/sentry-dashboards/outbound-api-requests/` |
-| `/product/insights/frontend/assets/` | `/product/dashboards/sentry-dashboards/frontend/assets/` |
-| `/product/insights/frontend/session-health/` | `/product/dashboards/sentry-dashboards/frontend/session-health/` |
-| `/product/insights/backend/` | `/product/dashboards/sentry-dashboards/backend/` |
-| `/product/insights/backend/queries/` | `/product/dashboards/sentry-dashboards/backend/queries/` |
-| `/product/insights/backend/requests/` | `/product/dashboards/sentry-dashboards/outbound-api-requests/` |
-| `/product/insights/backend/queue-monitoring/` | `/product/dashboards/sentry-dashboards/backend/queues/` |
-| `/product/insights/backend/queue-monitoring/queues-page/` | `/product/dashboards/sentry-dashboards/backend/queues/` |
-| `/product/insights/backend/caches/` | `/product/dashboards/sentry-dashboards/backend/caches/` |
-| `/product/insights/backend/caches/cache-page/` | `/product/dashboards/sentry-dashboards/backend/caches/` |
-| `/product/insights/mobile/` | `/product/dashboards/sentry-dashboards/mobile/` |
-| `/product/insights/mobile/mobile-vitals/` | `/product/dashboards/sentry-dashboards/mobile/mobile-vitals/` |
-| `/product/insights/mobile/mobile-vitals/app-starts/` | `/product/dashboards/sentry-dashboards/mobile/mobile-vitals/app-starts/` |
-| `/product/insights/mobile/mobile-vitals/screen-loads/` | `/product/dashboards/sentry-dashboards/mobile/mobile-vitals/screen-loads/` |
-| `/product/insights/mobile/network-requests/` | `/product/dashboards/sentry-dashboards/outbound-api-requests/` |
-| `/product/insights/mobile/session-health/` | `/product/dashboards/sentry-dashboards/mobile/session-health/` |
-| `/product/insights/web-vitals/` (no "frontend") | `/product/dashboards/sentry-dashboards/frontend/web-vitals/` |
-| `/product/insights/queries` (widgets.mdx used this) | `/product/dashboards/sentry-dashboards/backend/queries/` |
-| `/product/insights/requests` | `/product/dashboards/sentry-dashboards/outbound-api-requests/` |
-| `/product/insights/caches/` | `/product/dashboards/sentry-dashboards/backend/caches/` |
-
-**AI:** Leave under `docs/ai/`. No URL changes for AI monitoring docs. Links that pointed to `/product/insights/ai/*` should be updated to the current `docs/ai` URLs (e.g. `/ai/monitoring/agents/`, `/ai/monitoring/mcp/`).
-
----
-
-## Files to update (links) — outside `docs/product/insights/`
-
-Update these files to use the new paths from the table above. Replace any `/product/insights/...` with the corresponding `/product/dashboards/sentry-dashboards/...` (or merged path).
-
-### Product docs
-
-- `docs/product/alerts/alert-types.mdx` — metrics, latency, Apdex, failure rate, throughput
-- `docs/product/alerts/index.mdx` — metrics, latency, failure rate
-- `docs/product/dashboards/widget-library/index.mdx` — Apdex
-- `docs/product/issues/issue-details/performance-issues/index.mdx` — Insights and Tracing
-- `docs/product/issues/issue-details/performance-issues/web-vitals/index.mdx` — Web Vitals, opportunity
-- `docs/product/issues/issue-details/performance-issues/endpoint-regressions/index.mdx` — Span Summary / transaction-summary
-- `docs/product/projects/project-details/index.mdx` — Apdex, failure rate, TPM
-- `docs/product/releases/release-details.mdx` — Failure Rate
-- `docs/product/explore/discover-queries/query-builder/query-equations.mdx` — Apdex
-- `docs/product/explore/profiling/mobile-app-profiling/metrics.mdx` — Mobile Vitals
-- `docs/product/sentry-basics/integrate-frontend/configure-scms.mdx` — Insights
-- `docs/product/sentry-basics/performance-monitoring.mdx` — (if it links to insights; verify)
-- `docs/product/crons/alerts-backend-insights-migration.mdx` — "Insights > Backend" (naming)
-- `docs/product/pricing/legacy-pricing.mdx` — Insights features
-- `docs/product/dotnet/common/enriching-events/transaction-name/index.mdx` — Insights product (naming + link)
-
-### Concepts
-
-- `docs/concepts/key-terms/key-terms.mdx` — Insights Overview, performance monitoring
-- `docs/concepts/key-terms/tracing/index.mdx` — Insights page, caching issues, Learn more Insights
-- `docs/concepts/key-terms/tracing/distributed-tracing.mdx` — metrics
-- `docs/concepts/search/searchable-properties/issues.mdx` — transactions, transaction-summary
-- `docs/concepts/search/searchable-properties/events.mdx` — Apdex, User Misery
-
-### Platforms (tracing / overview)
-
-- `docs/platforms/android/tracing/index.mdx` — tracing/overview
-- `docs/platforms/android/overhead/index.mdx` — **performance-overhead** → sentry-dashboards
-- `docs/platforms/android/enriching-events/transaction-name/index.mdx` — Insights product
-- `docs/platforms/apple/common/overhead/index.mdx` — **performance-overhead** → sentry-dashboards
-- `docs/platforms/apple/common/features/index.mdx` — Tracing, Mobile Vitals
-- `docs/platforms/apple/common/tracing/instrumentation/automatic-instrumentation.mdx` — Mobile Vitals (×2)
-- `docs/platforms/apple/common/tracing/instrumentation/swiftui-instrumentation.mdx` — Mobile Vitals TTID/TTFD
-- `docs/platforms/apple/common/tracing/instrumentation/performance-metrics.mdx` — custom performance measurements
-- `docs/platforms/apple/guides/visionos/features/index.mdx` — Frame rate / mobile-vitals
-- `docs/platforms/apple/guides/tvos/features/index.mdx` — Frame rate
-- `docs/platforms/apple/guides/macos/features/index.mdx` — Frame rate
-- `docs/platforms/dart/common/features/index.mdx` — Tracing/overview
-- `docs/platforms/dart/common/tracing/instrumentation/performance-metrics.mdx` — custom performance measurements
-- `docs/platforms/dart/common/overhead/index.mdx` — **performance-overhead** → sentry-dashboards
-- `docs/platforms/dart/guides/flutter/tracing/index.mdx` — tracing/overview
-- `docs/platforms/dart/guides/flutter/tracing/instrumentation/performance-metrics.mdx` — (if present; verify)
-- `docs/platforms/dart/guides/flutter/overhead/index.mdx` — **performance-overhead** → sentry-dashboards
-- `docs/platforms/dotnet/common/tracing/index.mdx` — tracing/overview
-- `docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx` — Insights product
-- `docs/platforms/javascript/common/configuration/integrations/browsertracing.mdx` — tracing/overview
-- `docs/platforms/javascript/common/tracing/instrumentation/automatic-instrumentation.mdx` — Mobile Vitals, Web Vitals
-- `docs/platforms/powershell/tracing/instrumentation/performance-metrics.mdx` — custom performance measurements
-- `docs/platforms/react-native/tracing/instrumentation/performance-metrics.mdx` — custom performance measurements
-- `docs/platforms/react-native/tracing/instrumentation/time-to-display.mdx` — Mobile Vitals TTID/TTFD
-- `docs/platforms/react-native/tracing/instrumentation/automatic-instrumentation.mdx` — Mobile Vitals, Web Vitals
-- `docs/platforms/react-native/overhead/index.mdx` — **performance-overhead** → sentry-dashboards
-- `docs/platforms/react-native/enriching-events/transaction-name/index.mdx` — Insights product
-- `docs/platforms/ruby/common/migration.mdx` — tracing/overview
-- `docs/platforms/rust/common/tracing/index.mdx` — Insights
-- `docs/platforms/unity/tracing/index.mdx` — tracing/overview
-- `docs/platforms/unity/tracing/instrumentation/performance-metrics.mdx` — custom performance measurements
-- `docs/platforms/unreal/tracing/index.mdx` — tracing/overview
-
-### Guides & other
-
-- `docs/guides/custom-spans.mdx` — Sentry Agent Monitoring (`/product/insights/ai/agents/`) → use `/ai/monitoring/agents/` (or current AI doc URL)
-- `docs/contributing/approach/sdk-docs/write-getting-started.mdx` — points to insights getting-started; update path to sentry-dashboards getting-started (or index)
-
-### Develop-docs (optional)
-
-- `develop-docs/backend/application-domains/transaction-clustering/index.mdx` — Insights product, metrics
-- `develop-docs/sdk/telemetry/traces/opentelemetry.mdx` — performance monitoring product
-
-### Middleware and redirects
-
-- **`src/middleware.ts`:**  
-  - Change every `to: '/product/insights/...'` to the new destination (see path mapping).  
-  - `to: '/product/insights/performance-overhead/'` → `to: '/product/dashboards/sentry-dashboards/'`.  
-  - `to: '/product/insights/retention-priorities/'` → `to: '/organization/dynamic-sampling/'`.  
-  - Remove or replace redirect to `/product/insights/overview/trends/` (e.g. send `/product/performance/trends/` to `/product/dashboards/sentry-dashboards/`).
-- **`redirects.js`:** Add redirects for all old `/product/insights/*` URLs to the new sentry-dashboards paths. `redirects.js` already has `product/insights/retention-priorities/` → `organization/dynamic-sampling/`; add the rest of the insights → sentry-dashboards mappings.
-
----
-
-## Product naming (Insights → Sentry dashboards)
-
-Where the **product** is named "Insights," change to "Sentry dashboards" (or "Sentry Dashboards" where appropriate). Examples:
-
-- "Insights" (standalone) → "Sentry dashboards"
-- "Insights tab" → "Sentry Dashboards tab" or "dashboards"
-- "Insights Overview" → "Sentry Dashboards" or "Sentry dashboards overview" (depending on context after merge)
-- "Insights and Tracing" → "Sentry dashboards and Tracing" or "Sentry Dashboards and tracing"
-- "Insight Domain" → "Sentry dashboards domain" or rephrase
-- "Insights for Mobile Vitals" → "Sentry dashboards for Mobile Vitals" or "Mobile Vitals in Sentry Dashboards"
-- "[Insights](/product/insights/)" → "[Sentry dashboards](/product/dashboards/sentry-dashboards/)"
-
-**Files to review for naming (in addition to link updates above):**
-
-- `docs/product/insights/*` (content that moves into sentry-dashboards): replace "Insights" with "Sentry dashboards" in titles, descriptions, and body.
-- `docs/product/sentry-basics/performance-monitoring.mdx` — "Insights" pages
-- `docs/product/issues/issue-details/performance-issues/index.mdx` — "Insights and Tracing"
-- `docs/product/crons/alerts-backend-insights-migration.mdx` — "Insights > Backend"
-- `docs/concepts/key-terms/key-terms.mdx` — "Insights Overview"
-- `docs/concepts/key-terms/tracing/index.mdx` — "Insights" page, "Sentry's Insights"
-- `docs/platforms/dotnet/common/enriching-events/transaction-name/index.mdx` — "Insights product"
-- `docs/platforms/react-native/enriching-events/transaction-name/index.mdx` — "Insights product"
-- `docs/platforms/android/enriching-events/transaction-name/index.mdx` — "Insights product"
-- `docs/product/pricing/legacy-pricing.mdx` — "Insights features"
-
----
-
-## Performance Overhead
-
-- **Page:** `docs/product/insights/performance-overhead.mdx` is deleted; content merged or summarized in Sentry dashboards index.
-- **Redirect:** Add (in `redirects.js` or middleware):  
-  `/product/insights/performance-overhead/` → `/product/dashboards/sentry-dashboards/`
-- **Links to update (→ `/product/dashboards/sentry-dashboards/`):**
-  - `docs/platforms/android/overhead/index.mdx`
-  - `docs/platforms/apple/common/overhead/index.mdx`
-  - `docs/platforms/dart/common/overhead/index.mdx`
-  - `docs/platforms/dart/guides/flutter/overhead/index.mdx`
-  - `docs/platforms/react-native/overhead/index.mdx`
-- **Middleware:** Update rule that sends old performance-overhead URL to insights; point to sentry-dashboards instead.
-
----
-
-## Summary checklist
-
-- [ ] Move/merge all content from `docs/product/insights/` to `docs/product/dashboards/sentry-dashboards/` per migration plan (including single `queues.mdx`, merged outbound-api-requests, etc.).
-- [ ] Migrate `img` folders with each moved doc; fix image paths in MDX.
-- [ ] Update every link in the "Files to update" list to use new paths (path mapping table).
-- [ ] Replace product name "Insights" with "Sentry dashboards" in moved content and in the "Product naming" files.
-- [ ] Add redirects for all old `/product/insights/*` URLs to new sentry-dashboards URLs (redirects.js and/or middleware).
-- [ ] Performance overhead: redirect + update 5 platform overhead docs.
-- [ ] Middleware: retention-priorities → `/organization/dynamic-sampling/`; trends → remove or send to sentry-dashboards.
-- [ ] Fix widgets.mdx Queries link: `/product/insights/queries` → `/product/dashboards/sentry-dashboards/backend/queries/` (in migrated/salvaged content).
-- [ ] AI: ensure any remaining `/product/insights/ai/*` links point to current `docs/ai` URLs (e.g. `/ai/monitoring/agents/`).
\ No newline at end of file
This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.

- [ ] Performance overhead: redirect + update 5 platform overhead docs.
- [ ] Middleware: retention-priorities → `/organization/dynamic-sampling/`; trends → remove or send to sentry-dashboards.
- [ ] Fix widgets.mdx Queries link: `/product/insights/queries` → `/product/dashboards/sentry-dashboards/backend/queries/` (in migrated/salvaged content).
- [ ] AI: ensure any remaining `/product/insights/ai/*` links point to current `docs/ai` URLs (e.g. `/ai/monitoring/agents/`).
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Internal migration tracking document accidentally committed

High Severity

The file INSIGHTS-TO-SENTRY-DASHBOARDS-MIGRATION.md is an internal migration planning document with checklists, TODO-style items, and implementation notes (e.g., "Files to update," "Summary checklist" with unchecked boxes). This is not user-facing documentation and appears to be accidentally included in the published docs directory. It will likely be served to users on the docs site.

Fix in Cursor Fix in Web

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Forgot to ignore this. I'll be removing before releasing.

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

{
source: '/product/dashboards/sentry-dashboards/performance-metrics/',
destination: '/product/dashboards/sentry-dashboards/transaction-summary/',
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Redirects comment has typo "reduirects"

Low Severity

The comment on line 1353 reads // End of Insights reduirects. — "reduirects" is a typo for "redirects." This is a minor code comment issue but reduces readability of the redirects configuration.

Fix in Cursor Fix in Web

Comment on lines +1345 to +1352
{
source: '/product/insights/overview/metrics/',
destination: '/product/dashboards/sentry-dashboards/transaction-summary/',
},
{
source: '/product/dashboards/sentry-dashboards/performance-metrics/',
destination: '/product/dashboards/sentry-dashboards/transaction-summary/',
},
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The new redirect for /product/insights/overview/metrics/ in redirects.js does not preserve URL hash fragments, breaking existing anchor links from other documentation pages.
Severity: MEDIUM

Suggested Fix

Update the redirect configuration in redirects.js to handle hash fragments. The migration guide suggests the destination should be /product/dashboards/sentry-dashboards/transaction-summary/#metrics-in-this-view. The redirect should be modified to either permanently point to this anchor or dynamically preserve the original hash fragment if possible.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: redirects.js#L1345-L1352

Potential issue: The new redirect from `/product/insights/overview/metrics/` to
`/product/dashboards/sentry-dashboards/transaction-summary/` does not preserve URL hash
fragments. Numerous documentation pages link to specific sections of the old page, such
as `/product/insights/overview/metrics/#apdex`. Because Next.js redirects do not forward
the hash fragment by default, users clicking these links will land at the top of the new
page instead of the intended section. This breaks in-page navigation from multiple
source documents, including `alerts/index.mdx` and `filters-display/index.mdx`. The
project's own migration guide acknowledges the intended destination should include an
anchor, but the implementation in `redirects.js` omits it.

Did we get this right? 👍 / 👎 to inform future reviews.

description: "Learn more about cache monitoring with Sentry and how it can help improve your application's performance."
---

A cache can be used to speed up data retrieval, thereby improving application performance. A cache stores data temporarily to speed up subsequent access to that data. This allows your application to get data from cached memory (if it is available) instead having to download that data again or retrieving it from a potentially slow data layer. Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A cache can be used to speed up data retrieval, thereby improving application performance. A cache stores data temporarily to speed up subsequent access to that data. This allows your application to get data from cached memory (if it is available) instead having to download that data again or retrieving it from a potentially slow data layer. Caching can speed up read-heavy workloads for applications like Q&A portals, gaming, media sharing, and social networking.
Caches can improve application performance by storing frequently-accessed data so it can be retrieved more quickly rather than repeatedly fetching it from slower data sources. This is especially beneficial for read-heavy apps like Q&A platforms, gaming, media sharing, and social networks.


## Sample List

To help you compare the performances of cache hits (where a value was found in the cache) versus misses (where no value corresponding to the key was found in the cache) over time, Sentry automatically surfaces a distribution of both samples for the timeframe selected from the **Caches** page.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
To help you compare the performances of cache hits (where a value was found in the cache) versus misses (where no value corresponding to the key was found in the cache) over time, Sentry automatically surfaces a distribution of both samples for the timeframe selected from the **Caches** page.
To help you compare the performances of cache hits versus cache misses over time, Sentry automatically surfaces a distribution of both samples for the timeframe selected from the **Caches** page.

You've already defined these towards the top of this doc, I think omitting the definitions here keeps things a little clearer.

og_image: /og-images/product-insights-backend.png
---

Sentry's [**Backend Performance**](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page gives you an overview of the health of your application. You'll be able to see things like the **Most Time-Consuming Queries**, **Most Time-Consuming Domains**, **p50** and **p75 Duration**, and so on.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Sentry's [**Backend Performance**](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page gives you an overview of the health of your application. You'll be able to see things like the **Most Time-Consuming Queries**, **Most Time-Consuming Domains**, **p50** and **p75 Duration**, and so on.
Sentry's [**Backend Performance**](https://sentry.io/orgredirect/organizations/:orgslug/insights/backend/) page gives you an overview of the health of your application. You'll be able to see things like the **Most Time-Consuming Queries**, **Most Time-Consuming Domains**, **p50** and **p75 Duration**, and more.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants