getsentry
diff --git a/‎app/globals.css
+8 b/‎app/globals.css
+8
diff --git a/‎docs/cli/metrics.mdx
+2-2 b/‎docs/cli/metrics.mdx
+2-2
diff --git a/‎docs/concepts/key-terms/enrich-data/index.mdx
+1-1 b/‎docs/concepts/key-terms/enrich-data/index.mdx
+1-1
diff --git a/‎docs/concepts/key-terms/key-terms.mdx
+13-9 b/‎docs/concepts/key-terms/key-terms.mdx
+13-9
diff --git a/‎docs/concepts/key-terms/tracing/distributed-tracing.mdx
+6-5 b/‎docs/concepts/key-terms/tracing/distributed-tracing.mdx
+6-5
diff --git a/‎docs/concepts/key-terms/tracing/event-detail.mdx b/‎docs/concepts/key-terms/tracing/event-detail.mdx
diff --git a/‎docs/concepts/search/index.mdx
+1-1 b/‎docs/concepts/search/index.mdx
+1-1
diff --git a/‎docs/concepts/search/searchable-properties/events.mdx
+12-11 b/‎docs/concepts/search/searchable-properties/events.mdx
+12-11
diff --git a/‎docs/concepts/search/searchable-properties/index.mdx
+1 b/‎docs/concepts/search/searchable-properties/index.mdx
+1
@@ -52,6 +52,14 @@
   }
 }
 
+.icon-external-link {
+  margin-left: 0;
+
+  svg {
+    margin-left: 0.15em;
+  }
+}
+
 :root {
   /* Oranges */
   --flame0: #df5128;
 
@@ -4,7 +4,7 @@ sidebar_order: 5
 description: "Learn how Sentry's command line interface can be used for sending metrics."
 ---
 Metrics help you track and visualize the data points you care about, making it easier to monitor your application's health and identify issues.
-Learn more about [Metrics](/product/metrics).
+Learn more about [Metrics](/product/explore/metrics).
 
 ## Requirements
 - [Install](/product/cli/installation) the Sentry CLI (min v2.32.0).
@@ -35,7 +35,7 @@ sentry-cli send-metric increment -n "MyMetric" -u "MyUnit" -t "tag1:val1","tag2:
 ```
 
 The metric's name, unit, and tags will undergo normalization to only include supported characters.
-Learn more about [Limits and Restrictions](/product/metrics/#limits-and-restrictions).
+Learn more about [Limits and Restrictions](/product/explore/metrics/#limits-and-restrictions).
 
 ### Counters
 To increment a counter metric by one, you only need to provide the `--name` or `-n` parameter.
 
@@ -64,7 +64,7 @@ For instance, the Discover query below displays all the errors (total of 143 eve
 
 ![Discover Query](./img/004.png)
 
-Learn more in [Discover](/product/discover-queries/).
+Learn more in [Discover](/product/explore/discover-queries/).
 
 ### Ownership Rules
 
 
@@ -1,21 +1,21 @@
 ---
-title: Key Terms
+title: Key Terms & Features
 sidebar_order: 05
-description: "Learn about the key concepts and features of Sentry."
+description: "A few key terms and features to help you get a better understanding of Sentry."
 ---
 
-These key terms and concepts are the fundamentals of Sentry. While we define new terms as you come across them throughout our documentation, having an understanding of the key concepts and features here will make it easier to learn more complex ideas about the product.
+Some of the bellow terms have corresponding features with the same name (in upper case) in the [Key Features](#key-features) section.
 
-## Key Concepts
-
-Some of the following key concepts have corresponding features with the same name listed (in upper case) in the [Key Features](#key-features) section.
+## Key Terms
 
 - **alerts** - Alerts let you know about problems with your code in real-time by sending you notifications when certain alert rule conditions are met. There are several types of alerts available with customizable thresholds and integrations.
 
 - **attachments** - Stored additional files, such as config or log files that are related to an error event.
 
 - **data** - Anything you send to Sentry. This includes, events (errors or transactions), attachments, and event metadata.
 
+- **distributed trace** - When a trace includes work in multiple services, it's called a [distributed trace](/concepts/key-terms/tracing/distributed-tracing/), because the trace is distributed across those services.
+
 - **DSN** - Data Source Name. A DSN tells the Sentry SDK where to send events so the events are associated with the correct project. Sentry automatically assigns you a DSN when you create a project. Learn more in our full [DSN documentation](/product/sentry-basics/dsn-explainer/).
 
 - **environment** - `environment` is a Sentry-supported tag that you can add to your SDK that's intended to refer to your code deployments' naming convention, such as _development_, _testing_, _staging_, or _production_. Environments help you better filter issues and transactions among other uses. Learn more in our full [Environments documentation](/product/sentry-basics/environments/).
@@ -38,23 +38,27 @@ Some of the following key concepts have corresponding features with the same nam
 
 - **Sentry SDKs** - Sentry's programming language/framework-specific libraries for application monitoring. When you add one of our SDKs to your application, event data from your application is captured and sent to Sentry, so we can provide you with error and performance reports.
 
+- **span** - A [span](/concepts/key-terms/tracing/distributed-tracing/#traces-transactions-and-spans) is the basic unit that traces are composed of. Multiple groups of parent-child spans make up a trace in Sentry and share a trace_id, which can help you get to the root cause of a problem faster.
+
 - **team** - Teams are associated with your Sentry projects, and their members receive issue notifications as a group. Learn more about [setting up teams](/organization/getting-started/#2-set-up-teams).
 
+- **trace** - A [trace](/concepts/key-terms/tracing/) is the record of the entire operation you want to measure or track - like page load, an instance of a user completing some action in your application, or a cron job in your backend.
+
 - **transaction** - A transaction represents a single instance of a service being called to support an operation you want to measure or track, like a page load, page navigation, or asynchronous task. Transaction events are grouped by the transaction name.
 
 ## Key Features
 
-Each of these key features in [sentry.io](https://sentry.io) is represented by a page (or set of pages) in the application.
+Each of these key features have their own page (or set of pages) in the [sentry.io](https://sentry.io) application.
 
 - **Alerts** - Where you can create new alert rules and manage existing ones. Learn more in the full [Alerts documentation](/product/alerts/).
 
 - **Dashboards** - Provide you with a broad overview of your application’s health by allowing you to navigate through error and performance data across multiple projects. Dashboards are made up of one or more widgets, and each widget visualizes one or more **Discover** or **Issues** queries. Learn more in the full [Dashboards documentation](/product/dashboards/).
 
-- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/discover-queries/).
+- **Discover** - Allows you to query events across environments, providing you with visibility into your errors and transactions and unlocking insights into the health of your entire system. The **Discover** page visualizes the results of queries. Learn more in the full [Discover documentation](/product/explore/discover-queries/).
 
 - **Issues** - Displays information about grouped problems in your application. From here, you can go to the **Issue Details** page for a more granular view of any issue. Learn more in the full [Issues documentation](/product/issues/).
 
-- **Performance** - The main view in [sentry.io](http://sentry.io) where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full [Performance documentation](/product/performance/).
+- **Performance** - The main view in [sentry.io](http://sentry.io) where you can search or browse for transaction data. The page displays graphs that visualize transactions or trends, as well as a table where you can view relevant transactions and drill down to more information about them. Learn more in the full [Tracing documentation](/product/performance/).
 
 - **Projects** - Lists the projects of which you're a member, by team, and provides you with a high-level overview of your projects. From here, you can go to the **Project Details** page of each project for a more granular view. Learn more in the full [Projects documentation](/product/projects/).
 
 
@@ -184,12 +184,13 @@ The majority of the data in a transaction resides in the individual spans the tr
 - `op`: short string identifying the type or category of operation the span is measuring. Details on the structure of span operations can be [found in the Sentry developer documentation](https://develop.sentry.dev/sdk/performance/span-operations/).
 - `start_timestamp`: when the span was opened
 - `end_timestamp`: when the span was closed
-- `description`: longer description of the span's operation, which uniquely identifies the span but is consistent across instances of the span (optional)
-- `status`: short code indicating operation's status (optional)
-- `tags`: key-value pairs holding additional data about the span (optional)
-- `data`: arbitrarily-structured additional data about the span (optional)
+- `description`: longer description of the span's operation, which uniquely identifies the span but is consistent across instances of the span
+- `status`: short code indicating operation's status
+- `tags`: key-value pairs holding additional data about the span
+- `data`: arbitrarily-structured additional data about the span
 
 An example use of the `op` and `description` properties together is `op: db.query` and `description: SELECT * FROM users WHERE last_active < %s`. The `status` property is often used to indicate the success or failure of the span's operation, or for a response code in the case of HTTP requests. Finally, `tags` and `data` allow you to attach further contextual information to the span, such as `function: middleware.auth.is_authenticated` for a function call or `request: {url: ..., headers: ... , body: ...}` for an HTTP request.
+To search span data see [Searchable Properties](/concepts/search/searchable-properties/spans/)
 
 ### Important Information About Tracing, Spans & Transactions
 
@@ -249,4 +250,4 @@ Dynamic sampling ensures complete traces by retaining all transactions associate
 
 ## Viewing Trace Data
 
-Through [Performance](/product/performance/) and [Discover](/product/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page.
+Through [Performance](/product/performance/) and [Discover](/product/explore/discover-queries/), you can view trace data in the [Trace Details](/concepts/key-terms/tracing/trace-view/) page.
@@ -50,7 +50,7 @@ Here are some examples of valid comparison operator searches:
 
 <Note>
 
-`OR` and `AND` search conditions are only available for [Discover](/product/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
+`OR` and `AND` search conditions are only available for [Discover](/product/explore/discover-queries/), [Performance](/product/performance/), and [Metric Alerts](/product/alerts-notifications/metric-alerts/).
 
 </Note>
 
 
@@ -342,43 +342,43 @@ Returns results with a matching maximum value for the field entered.
 
 ### `measurements.app_start_cold`
 
-A [cold start](/product/performance/mobile-vitals/#app-start) refers to when the app launches for the first time after a reboot or update. The app is not in memory and no process exists.
+A [cold start](/product/insights/mobile-vitals/#app-start) refers to when the app launches for the first time after a reboot or update. The app is not in memory and no process exists.
 
 - **Type:** duration
 
 ### `measurements.app_start_warm`
 
-A [warm start](/product/performance/mobile-vitals/#app-start) refers to when the app has already launched at least once and is partially in memory. For instance, the user backs out of your app, but then re-launches it. The process may have continued to run, but the app must recreate the activity from scratch.
+A [warm start](/product/insights/mobile-vitals/#app-start) refers to when the app has already launched at least once and is partially in memory. For instance, the user backs out of your app, but then re-launches it. The process may have continued to run, but the app must recreate the activity from scratch.
 
 - **Type:** duration
 
 ### `measurements.cls`
 
-[Cumulative Layout Shift (CLS)](/product/performance/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process.
+[Cumulative Layout Shift (CLS)](/product/insights/web-vitals/web-vitals-concepts/#cumulative-layout-shift-cls) is the sum of individual layout shift scores for every unexpected element shift during the rendering process.
 
 - **Type:** number
 
 ### `measurements.fcp`
 
-[First Contentful Paint (FCP)](/product/performance/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport.
+[First Contentful Paint (FCP)](/product/insights/web-vitals/web-vitals-concepts/#first-contentful-paint-fcp) measures the time for the first content to render in the viewport.
 
 - **Type:** duration
 
 ### `measurements.fid`
 
-[First Input Delay (FID)](/product/performance/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport.
+[First Input Delay (FID)](/product/insights/web-vitals/web-vitals-concepts/#first-input-delay-fid) measures the response time when the user tries to interact with the viewport.
 
 - **Type:** duration
 
 ### `measurements.fp`
 
-[First Paint (FP)](/product/performance/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed.
+[First Paint (FP)](/product/insights/web-vitals/web-vitals-concepts/#first-paint-fp) measures the amount of time the first pixel takes to appear in the viewport, rendering any visual change from what was previously displayed.
 
 - **Type:** duration
 
 ### `measurements.frames_frozen`
 
-[Slow and frozen frames](/product/performance/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/insights/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 
@@ -390,7 +390,7 @@ Returns results with a matching rate of frozen frames. That is, `measurements.fr
 
 ### `measurements.frames_slow`
 
-[Slow and frozen frames](/product/performance/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
+[Slow and frozen frames](/product/insights/mobile-vitals/#slow-and-frozen-frames) measure the responsiveness of your app.
 
 - **Type:** number
 
@@ -408,7 +408,7 @@ Returns results with a matching total number of frames.
 
 ### `measurements.lcp`
 
-[Largest Contentful Paint (LCP)](/product/performance/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport.
+[Largest Contentful Paint (LCP)](/product/insights/web-vitals/web-vitals-concepts/#largest-contentful-paint-lcp) measures the render time for the largest content to appear in the viewport.
 
 - **Type:** duration
 
@@ -438,7 +438,7 @@ The [total stall time](/platforms/react-native/performance/instrumentation/autom
 
 ### `measurements.ttfb`
 
-[Time To First Byte (TTFB)](/product/performance/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content.
+[Time To First Byte (TTFB)](/product/insights/web-vitals/web-vitals-concepts/#time-to-first-byte-ttfb) measures the time that it takes for a user's browser to receive the first byte of page content.
 
 - **Type:** duration
 
@@ -480,7 +480,8 @@ Returns results with an approximate percentile of the field to the level. The le
 
 ### `platform`
 
-Name of the platform. This is only a metrics property for [valid platforms](https://github.com/getsentry/relay/blob/9d0d2dc54233d46043a369e1dacf7db900953c14/relay-general/src/protocol/constants.rs#L1-L21), defaulting to `other`.
+Name of the platform. This defaults to `other` and is only a property for platforms from this list:
+`as3`, `c`, `cfml`, `cocoa`, `csharp`, `elixir`, `go`, `groovy`, `haskell`, `java`, `javascript`, `native`, `node`, `objc`, `other`, `perl`, `php`, `python`, `ruby`
 
 - **Type:** string
 
 
@@ -12,6 +12,7 @@ Sentry's searchable properties fall into one of five categories:
 
 - [Issue properties](/product/sentry-basics/search/searchable-properties/issues/)
 - [Event properties](/product/sentry-basics/search/searchable-properties/events/)
+- [Span properties](/concepts/search/searchable-properties/spans/)
 - [Session Replay properties](/product/sentry-basics/search/searchable-properties/session-replay/)
 - [User Feedback properties](/product/sentry-basics/search/searchable-properties/user-feedback/)
 - [Release properties](/product/sentry-basics/search/searchable-properties/releases/)
Original file line number	Diff line number	Diff line change
`@@ -52,6 +52,14 @@`
`52`	`52`	`}`
`53`	`53`	`}`
`54`	`54`
	`55`	`+.icon-external-link {`
	`56`	`+ margin-left: 0;`
	`57`	`+`
	`58`	`+ svg {`
	`59`	`+ margin-left: 0.15em;`
	`60`	`+ }`
	`61`	`+}`
	`62`	`+`
`55`	`63`	`:root {`
`56`	`64`	`/* Oranges */`
`57`	`65`	`--flame0: #df5128;`