feat(Discover EOL): Updating docs to remove Discover pages and add Explore > Errors#18751
feat(Discover EOL): Updating docs to remove Discover pages and add Explore > Errors#18751sfanahata wants to merge 2 commits into
Conversation
…ge. Redirects should all be up to date.
|
Deployment failed with the following error: |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
bcoe
left a comment
bcoe
left a comment
There was a problem hiding this comment.
Left a few comments. There are some instances where we used the product Discover to refer to both searching "Transactions" and searching "Errors". We're now in a world where you can query Logs, Errors, Application Metrics, traces and other telemetry under explore. So, rather than replacing instances of Discover with Explore > Error, we should probably mention some of these other telemetry types; we can probably just refer to the set of datasets here, as what's available to search in "Explore".
| @@ -62,11 +62,9 @@ Learn more in [Search](/concepts/search/). | |||
|
|
|||
| Discover is a powerful query engine that builds upon your data, allowing you to reveal patterns, anomalies, and deeper insights in the health of your entire system. With this in mind, the more (custom) data you add to your events, the more flexibility you'll gain in building queries that address your environments, releases, custom development, and business characteristics through _tags_, and the end-users impacted by those events. | |||
There was a problem hiding this comment.
Should we change our language to "Explore" and we and if appropriate we could mention that it's for searching a variety of types of telemetry.
| Use the [Trace Explorer](/product/trace-explorer/) to search for traces containing spans that meet your specific query conditions. This helps you find distributed traces that give you a connected view of your application and can help you debug and optimize your code. | ||
|
|
||
| Through [Performance](/product/dashboards/sentry-dashboards/) and [Discover](/product/discover-queries/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page. | ||
| Through [Performance](/product/dashboards/sentry-dashboards/) and [Errors](/product/errors/), you can also view trace data in the [Trace View](/concepts/key-terms/tracing/trace-view/) page. |
There was a problem hiding this comment.
Here we'd probably be better to link to Explore > Tracing
| <Alert> | ||
|
|
||
| `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/). | ||
| `OR` and `AND` search conditions are only available for [Errors](/product/errors/), [Sentry Dashboards](/product/dashboards/sentry-dashboards/), and [Monitors](/product/monitors-and-alerts/monitors/). |
There was a problem hiding this comment.
Probably we can start talking about "Explore", and mention that it allows you to search a few telemetry types, vs., errors which is just one of the types.
|
|
||
| <Alert> | ||
| 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/). | ||
| 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 [Errors](/product/errors/). |
There was a problem hiding this comment.
For anything tracing related, like Vitals, probably we need to link this to Explore > Tracing rather than Explore Errors.
| You can make [custom dashboards](/product/dashboards/custom-dashboards/) by duplicating an existing dashboard, using [AI to generate a dashboard](/product/dashboards/custom-dashboards/#ai-generated-dashboards) with natural language, or starting from scratch by pressing the **Create Dashboard** button. Custom dashboards enable you to create views tailored to your organization's needs. For example, you may want to track performance of a specific feature, or track errors by a specific team's ownership. Once in edit mode, use the same filters you use to drill into a dashboard to customize your dashboard. | ||
|
|
||
| ## Open Dashboard Widgets in Discover and Issues | ||
| ## Open Dashboard Widgets in Errors and Issues |
There was a problem hiding this comment.
Worth mentioning that you can open Explore > Traces, Explore > Errors, Explore > Logs, Explore > Application Metrics.
|
|
||
| ## Overview | ||
|
|
||
| The [**Errors**](https://sentry.io/orgredirect/organizations/:orgslug/explore/errors/) page lets you query all of your error event metadata across projects and environments. You can build custom queries with flexible filters, group and stack results, visualize trends over time, and save queries for reuse by your team. |
There was a problem hiding this comment.
Right now this url redirects me to /explore/errors/queries/, let's update the link to go there so we avoid unnecessary redirects.
|
|
||
| ## Pre-built Queries | ||
|
|
||
| Pre-built queries are available from the "Saved Queries" view and are identified by the Sentry avatar. These can be duplicated, butcannot be removed. |
There was a problem hiding this comment.
| Pre-built queries are available from the "Saved Queries" view and are identified by the Sentry avatar. These can be duplicated, butcannot be removed. | |
| Pre-built queries are available from the "Saved Queries" view and are identified by the Sentry avatar. These can be duplicated, but cannot be removed. |
Surprised our typo-checker didn't catch this one. 🤔
|
Errors doesn't seem to be enabled for all accounts at present. Will this change before we merge this, or should we add a warning letting users know who currently has access? |
coolguyzone
left a comment
coolguyzone
left a comment
There was a problem hiding this comment.
The update looks good to me! Not every account has access to Errors yet, so let's address that before we merge.
3 participants
DESCRIBE YOUR PR
Summary
Sentry is removing the Discover feature set. The errors tab from Discover is moving to Explore > Errors (same functionality, new location), and the transactions tab is being removed entirely (already deprecated in favor of Trace Explorer).
Changes
New page:
/product/errors/docs/product/errors/index.mdxwithsidebar_order: 201(appears right after Traces and Spans, before Logs in the Explore/Debug nav section)Deleted:
/product/discover-queries/index.mdx,query-builder.mdx,uncover-trends.mdx,query-builder/query-equations.mdx,standard-fields.json) and associated imagesUpdated internal references (12 files)
/product/discover-queries/now point to/product/errors/Redirects
redirects.js: Added redirects from/product/discover-queriesand/product/discover-queries/:path*to/product/errors/middleware.ts: Updated all 9 legacy discover redirect destinations to/product/errors/; added new/product/discover-queries/redirectMain preview page: https://sentry-docs-git-sfanahata-featdiscover-to-errors-explore.sentry.dev/product/errors/
IS YOUR CHANGE URGENT?
Help us prioritize incoming PRs by letting us know when the change needs to go live.
SLA
Thanks in advance for your help!
PRE-MERGE CHECKLIST
Make sure you've checked the following before merging your changes: