Merge branch 'master' into feat/add-docs-for-release-health-dataset

Author: shruthilayaj

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,16 @@
+
+
+
+<!-- Describe your PR here. -->
+
+
+
+<!--
+
+  Sentry employees and contractors can delete or ignore the following.
+
+-->
+
+### Legal Boilerplate
+
+Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

LICENSE

@@ -16,7 +16,7 @@ Additional Use Grant: You may make use of the Licensed Work, provided that you d
                       error-reporting or application monitoring features of the
                       Licensed Work.
 
-Change Date:          2025-04-15
+Change Date:          2025-05-15
 
 Change License:       Apache License, Version 2.0
 

README.md

@@ -1,7 +1,11 @@
 <p align="center">
-    <a href="https://sentry.io" target="_blank" align="center">
-        <img src="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" width="280">
-    </a>
+  <a href="https://sentry.io/?utm_source=github&utm_medium=logo" target="_blank">
+    <picture>
+      <source srcset="https://sentry-brand.storage.googleapis.com/sentry-logo-white.png" media="(prefers-color-scheme: dark)" />
+      <source srcset="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" media="(prefers-color-scheme: light), (prefers-color-scheme: no-preference)" />
+      <img src="https://sentry-brand.storage.googleapis.com/sentry-logo-black.png" alt="Sentry" width="280">
+    </picture>
+  </a>
 </p>
 
 _Bad software is everywhere, and we're tired of it. Sentry is on a mission to help developers write better software faster, so we can get back to enjoying technology. If you want to join us [<kbd>**Check out our open positions**</kbd>](https://sentry.io/careers/)_

package.json

@@ -15,8 +15,8 @@
     "@mdx-js/mdx": "^1.6.18",
     "@mdx-js/react": "^1.6.18",
     "@sentry-internal/global-search": "0.1.3",
-    "@sentry/gatsby": "^6.19.2",
-    "@sentry/tracing": "^6.19.2",
+    "@sentry/gatsby": "^7.0.0-rc.0",
+    "@sentry/tracing": "^7.0.0-rc.0",
     "@sentry/webpack-plugin": "^1.18.3",
     "@types/dompurify": "^2.0.3",
     "@types/node": "^12",

src/components/banner.tsx

@@ -7,9 +7,9 @@ import React, { useState, useEffect } from "react";
 //
 const SHOW_BANNER = true;
 const BANNER_TEXT =
-  "Sentry will be at Pycon US 2022 - join our live workshop, 'Elasticsearch and Python, a Match Made in Heaven' on Apr. 28 @ 9:00 AM MDT.";
+  "See how Calixa protected their developers' time by building a custom integration on Sentry in our live workshop on June 7 @ 10am PT.";
 const BANNER_LINK_URL =
-  "https://us.pycon.org/2022/schedule/presentation/168/";
+  "https://sentry.io/resources/calixa-sentry-workshop/?promo_name=docs-banner";
 const BANNER_LINK_TEXT = "Register here.";
 const OPTIONAL_BANNER_IMAGE = null;
 

src/components/cliChecksumTable.tsx

@@ -5,6 +5,7 @@ import styled from "@emotion/styled";
 const query = graphql`
   query CliExecutableChecksums {
     app(id: { eq: "sentry-cli" }) {
+      version,
       files {
         name
         checksums {
@@ -23,14 +24,14 @@ const ChecksumValue = styled.code`
 
 export default (): JSX.Element => {
   const {
-    app: { files },
+    app: { files, version },
   } = useStaticQuery(query);
 
   return (
     <table style={{ display: "block", overflow: "scroll" }}>
       <thead>
         <tr>
-          <th>File</th>
+          <th>Filename (v{version})</th>
           <th>Integrity Checksum</th>
         </tr>
       </thead>

src/docs/contributing/approach/sdk-docs/write-configuration.mdx

@@ -3,14 +3,14 @@ title: How to Write - Configuration
 noindex: true
 sidebar_order: 40
 redirect_from:
- - /contributing/approach/write-configuration/
+  - /contributing/approach/write-configuration/
 ---
 
 The Configuration section of the content covers, unsurprisingly, how customers can configure an SDK. In most cases, the SDK will adopt the common content, which is stored in `/platforms/common/configuration/` - feel free to peruse the files in that directory to help answer any questions.
 
 <Alert >
 
-DO NOT change the common content. That change will ripple across all SDKs that rely on the common content. Instead, open an issue on  GitHub with questions/suggestions.
+DO NOT change the common content. That change will ripple across all SDKs that rely on the common content. Instead, open an issue on GitHub with questions/suggestions.
 
 </Alert >
 
@@ -20,27 +20,27 @@ Most of these pages are pretty self-evident, so only basic information is provid
 
 Determine if the page applies:
 
-- If the content *does not apply*, add the SDK to `notSupported` list in the frontmatter of the file. This will turn off the display of the content for this SDK.
-- If the content *does apply*, add the `include` file to the correct directory as noted for each page. If the code sample is not provided, the page will display a big gray box requesting that customers open an issue for the missing sample.
+- If the content _does not apply_, add the SDK to `notSupported` list in the frontmatter of the file. This will turn off the display of the content for this SDK.
+- If the content _does apply_, add the `include` file to the correct directory as noted for each page. If the code sample is not provided, the page will display a big gray box requesting that customers open an issue for the missing sample.
 
 ### Basic Options
 
-This file is `options.mdx`. It explains all the configuration options. And by that, we do mean *all*. It is the trickiest file to manage, because it uses a variety of techniques to determine whether to display the content.
+This file is `options.mdx`. It explains all the configuration options. And by that, we do mean _all_. It is the trickiest file to manage, because it uses a variety of techniques to determine whether to display the content.
 
 To develop content for this file:
 
 1. Create the `configuration/config-intro/` statement, which covers how options can be set.
 2. For individual options that the SDK does NOT support, add the name of the SDK to the `ConfigKey` statement for that option. This will prevent that option from displaying for this SDK. For example:
 
-    `<ConfigKey name="debug" notSupported={["php"]}>`
+   `<ConfigKey name="debug" notSupported={["php"]}>`
 
-    Alternately, for individual options that the SDK DOES support, add the name of the SDK to `ConfigKey` statement for that option, which ensures the option displays. For example:
+   Alternately, for individual options that the SDK DOES support, add the name of the SDK to `ConfigKey` statement for that option, which ensures the option displays. For example:
 
-    `<ConfigKey name="send-default-pii" supported={["dotnet", "javascript", "node", "react-native", "python", "java", "php", "rust"]}>`
+   `<ConfigKey name="send-default-pii" supported={["dotnet", "javascript", "node", "react-native", "python", "java", "php", "rust"]}>`
 
 3. For a grouping of options that the SDK DOES support, add the name of the SDK to the `PlatformSection` statement for those options, which ensures the option displays. For example:
 
-    `<PlatformSection supported={["javascript", "python", "node"]}>`
+   `<PlatformSection supported={["javascript", "python", "node"]}>`
 
 ### Releases & Health
 
@@ -51,9 +51,9 @@ This file is `releases.mdx`. It explains how to configure the SDK to tell Sentry
 A few nuances:
 
 - If adding an SDK related to JavaScript, update the source maps-related paragraph, as appropriate, in the `PlatformSection supported` statement.
-- For SDKs that support Release Health, we control the display of content with a `PlatformSection supported` statement. For these SDKs, provide the following code samples:
-    - Session tracking, stored in `/src/includes/configuration/session-tracking-interval`
-    - Opt out of auto session tracking, stored in `/src/includes/configuration/auto-session-tracking`
+- For SDKs that support release health, we control the display of content with a `PlatformSection supported` statement. For these SDKs, provide the following code samples:
+  - Session tracking, stored in `/src/includes/configuration/session-tracking-interval`
+  - Opt out of auto session tracking, stored in `/src/includes/configuration/auto-session-tracking`
 
 ### Environments
 

src/docs/contributing/approach/sdk-docs/write-data-management.mdx

@@ -30,7 +30,7 @@ This file is `/sensitive-data/index.mdx`. It explains how to scrub or filter dat
 
 For data scrubbing that the SDK DOES NOT support, add the name of the SDK to the `PlatformSection notSupported` statement, which ensures the content won't display. For example:
 
-`<PlatformSection notSupported={["flutter", "apple", "perl", "native.breakpad", "native.crashpad", "native.minidumps", "native.wasm", "native.ue4", "go", "ruby", "native", "elixir"]}>`
+`<PlatformSection notSupported={["flutter", "apple", "perl", "native.breakpad", "native.crashpad", "native.minidumps", "native.wasm", "unreal", "go", "ruby", "native", "elixir"]}>`
 
 Add the code sample to these directories:
 

src/docs/contributing/platforms/index.mdx

@@ -110,8 +110,8 @@ If you wanted to make hide the content for a platform by default, but enable it
 
 ```markdown
 ---
-supported:
-  - native.ue4
+supported: 
+  - native.wasm
 notSupported:
   - native
 ---

src/docs/product/accounts/pricing.mdx

@@ -46,9 +46,8 @@ You can set a maximum monthly on-demand invoice amount by setting an on-demand b
 
 <Note>
 
-Per-category on-demand budgets are rolling out for general availability (GA) to paying customers on plans with [performance monitoring](/product/performance/) features.
+Per-category on-demand budgets are available to paying customers on plans with [performance monitoring](/product/performance/) features.
 
-Until the GA rollout is complete, the feature is still available for organizations on paid performance plans in the Early Adopter program. If you opt out of the Early Adopter program while on the per-category on-demand budget strategy, you'll retain the per-category budgets you've set and the ability to update them. However, if you switch to the shared on-demand budget strategy, you won't be able to switch back unless you opt in to the Early Adopter program again.
 Customers on plans without performance monitoring can only use the shared on-demand budget strategy.
 
 </Note>

src/docs/product/accounts/quotas/manage-event-stream-guide.mdx

@@ -152,7 +152,7 @@ To review the error events dropped because of spike protection, go to **Settings
 
 Learn more about [how spike protection works](/product/accounts/quotas/#spike-protection).
 
-## 6. Event Usage Stats {#common-workflows-for-managing-your-event-stream}
+## 8. Event Usage Stats {#common-workflows-for-managing-your-event-stream}
 
 Once you've completed the steps above, you can look at your events in aggregate in the "Usage Stats" tab of **Stats**. This information will help you answer some key questions like:
 

src/docs/product/alerts/best-practices.mdx

@@ -55,7 +55,7 @@ These routing best practices ensure that you alert the right people about a prob
   - Medium priority: Notification (for example, Slack)
   - Low priority: Email
 - **Review List**: Found in the "For Review" tab of **Issues**, the [**Review List**](/product/issues/states-triage/#mark-reviewed) is where you can check on your lowest priority issues without receiving any alerts.
-- **Build an integration**: If you would like to route alert notifications to solutions with which Sentry doesn't yet have an out-of-the-box integration, you can use our [Integration Platform](/product/integrations/integration-platform/). When you create an integration, it will be available in the alert actions menu. You might want use your own integration for:
+- **Build an integration**: If you would like to route alert notifications to solutions with which Sentry doesn't yet have an out-of-the-box integration, you can use our [integration platform](/product/integrations/integration-platform/). When you create an integration, it will be available in the alert actions menu. You might want use your own integration for:
   - Sending alerts to integrations not supported natively
   - Aggregating alerts from your different monitoring systems
   - Writing custom rules in the webhook handler to route alerts more intelligently

src/docs/product/alerts/create-alerts/issue-alert-config.mdx

@@ -85,7 +85,7 @@ Learn more about and <PlatformLink to="/enriching-events/tags/">tags</PlatformLi
   - Send a [PagerDuty](/product/integrations/notification-incidents/pagerduty/) notification
   - Send a [Microsoft Teams](/product/integrations/notification-incidents/msteams/) notification
   - Send a notification to all legacy integrations.
-  - Send a notification using an [integration](/product/integrations/) built on the [Integration Platform](/product/integrations/integration-platform/)
+  - Send a notification using an [integration](/product/integrations/) built on the [integration platform](/product/integrations/integration-platform/)
 - Create an issue for an [integration](/product/integrations/), which includes:
   - [Jira](/product/integrations/issue-tracking/jira/)
   - [Azure DevOps](/product/integrations/source-code-mgmt/azure-devops)

src/docs/product/alerts/create-alerts/metric-alert-config.mdx

@@ -102,7 +102,7 @@ Actions define how you and your team will be alerted:
 - Send a [Slack](/product/integrations/notification-incidents/slack/) notification.
 - Trigger a [PagerDuty](/product/integrations/notification-incidents/pagerduty/) incident.
 - Send a [Microsoft Teams](/product/integrations/notification-incidents/msteams/) notification.
-- Send a request using [internal integrations](/product/integrations/integration-platform/#internal-integrations).
+- Send a request using [Sentry integrations](/product/integrations/integration-platform/).
 
 Learn more about [routing alerts with integrations](/product/alerts/create-alerts/routing-alerts/).
 

src/docs/product/alerts/create-alerts/routing-alerts.mdx

@@ -2,7 +2,7 @@
 title: Alert Routing With Integrations
 sidebar_order: 30
 redirect_from:
- - /product/sentry-basics/guides/alert-notifications/routing-alerts/
+  - /product/sentry-basics/guides/alert-notifications/routing-alerts/
 description: "Learn more about routing alerts using Sentry integrations."
 ---
 
@@ -32,7 +32,7 @@ A Sentry organization owner, manager, or admin can install and configure the [Mi
 
 ## Build Your Own Integration
 
-If you would like to route alert notifications to other solutions that Sentry doesn't have an out-of-the-box integration with, you can use our [Integration Platform](/product/integrations/integration-platform/). The Integration Platform provides a way for external services to interact with the Sentry SaaS service using the REST API and webhooks.
+If you would like to route alert notifications to other solutions that Sentry doesn't have an out-of-the-box integration with, you can use our [integration platform](/product/integrations/integration-platform/). The integration platform provides a way for external services to interact with the Sentry SaaS service using the REST API and webhooks.
 
 Sending alerts to webhooks can also be helpful if you want to do things like aggregate alerts from your different monitoring systems or write custom rules to route alerts more intelligently.
 

src/docs/product/cli/installation.mdx

@@ -20,6 +20,13 @@ If you are on OS X or Linux, you can use the automated downloader which will fet
 curl -sL https://sentry.io/get-cli/ | bash
 ```
 
+We do however, encourage you to pin the specific version of the CLI, so your builds are always reproducible.
+To do that, you can use the exact same method, with an additional version specifier:
+
+```bash
+curl -sL https://sentry.io/get-cli/ | SENTRY_CLI_VERSION="{{ apps.version('sentry-cli') }}" bash
+```
+
 This will automatically download the correct version of `sentry-cli` for your operating system and install it. If necessary, it will prompt for your admin password for `sudo`. For a different installation location or for systems without `sudo` (like Windows), you can `export INSTALL_DIR=/custom/installation/path` before running this command.
 
 To verify it’s installed correctly you can bring up the help:
@@ -102,7 +109,6 @@ Options listed below control how `sentry-cli` install script behaves, when insta
 
 : If set, the script will change where it writes its output. Possible values are `stdout` and `stderr`. Defaults to `stdout`.
 
-
 ## Installation via Homebrew
 
 If you are on OS X, you can install `sentry-cli` via homebrew:
@@ -139,3 +145,6 @@ When downloading an executable from a remote server, it's often a good practice
 Below is the table of SHA256 checksums for all available build targets that our CLI supports. To calculate the hash of a downloaded file, you can use `sha256sum` utility, which is preinstalled in OSX and most Linux distributions.
 
 <CliChecksumTable />
+
+If you would like to verify checksums for historic versions of the `sentry-cli`, please refer to our release registry directly, which can be found at [https://release-registry.services.sentry.io/apps/sentry-cli/{version}](https://release-registry.services.sentry.io/apps/sentry-cli/latest).
+For example, [https://release-registry.services.sentry.io/apps/sentry-cli/1.74.4](https://release-registry.services.sentry.io/apps/sentry-cli/1.74.4).

src/docs/product/discover-queries/query-builder.mdx

@@ -24,7 +24,7 @@ From the **Discover** page, you can build a query in three ways.
 
 There are four main building blocks that impact the results of your saved query. You can use a combination of these to narrow down your search.
 
-1. Proejct, environment, and date range filters
+1. Project, environment, and date range filters
 2. Search Conditions
 3. Interactive Graph
 4. Table Columns
@@ -35,11 +35,11 @@ These common filters allow you to filter on your projects and environments, as w
 
 ## Filter by Search Conditions
 
-All events have built-in key fields or custom tags. Use the search bar to enter these keys and assign them values. This will filter down your list of events. Here are the built-in key fields.
+All events have built-in key fields or custom tags. Use the search bar to enter these keys and assign them values. This will filter down your list of events. For a list of the built-in key fields, check out our [Searchable Properties documentation](/product/sentry-basics/search/searchable-properties/).
 
-import standardFields from "./standard-fields.json";
+<!--import standardFields from "./standard-fields.json";
 
-<ParamTable fields={standardFields} />
+<ParamTable fields={standardFields} /> -->
 
 ### Syntax
 
@@ -99,12 +99,28 @@ Above the table, click "Columns" to open the modal that shows you a list of all
 
 You can also add any of the following functions as columns to stack events:
 
+- `any(...)`
+- `apdex(...)`
 - `avg(...)`
-- `count(...)`
+- `count()`
+- `count_if(...)`
+- `count_miserable(...)`
 - `count_unique(...)`
+- `epm()`
+- `eps()`
+- `failure_count()`
+- `failure_rate()`
+- `last_seen()`
 - `max(...)`
 - `min(...)`
+- `percentile(...)`
+- `p50(...)`
+- `p75(...)`
+- `p95(...)`
+- `p99(...)`
+- `p100(...)`
 - `sum(...)`
+- `user_misery(...)`
 
 Each function will ask you to assign a parameter. Some are required while others are optional. Functions will stack events based on the same values. If no functions are applied, the events in your "Query Results" table will remain individually listed. Once you are done editing the columns, click "Apply" and results will be reflected in the query results. Keep in mind, the table may horizontally scroll if many columns are added.
 

src/docs/product/integrations/debugging/rookout/index.mdx

@@ -10,7 +10,7 @@ description: "Learn more about Sentry's Rookout integration and how it adds a la
 
 Rookout adds a layer of depth to Sentry issues by allowing you to jump right from an Issue to a non-breaking breakpoint on the line that caused the error.
 
-This integration needs to set up only once per organization, then it is available for _all_ projects. It is maintained and supported by the company that created it. For more details, see [Integration Platform](/product/integrations/integration-platform/).
+This integration is maintained and supported by the company that created it. For more details, check out our [Integration Platform documentation](/product/integrations/integration-platform/).
 
 ## Install and Configure