Fixed links to event-payloads

Author: antonpirker

develop-docs/application/transaction-clustering/index.mdx

@@ -12,7 +12,7 @@ In terms of technical implementation, it is similar to [Data Scrubbing](/pii/).
 ## The Problem
 
 In our [Performance](https://docs.sentry.io/product/performance/) product, transactions are grouped by their name
-(the [`event.transaction`](/sdk/event-payloads/#optional-attributes) field).
+(the [`event.transaction`](/sdk/data-model/event-payloads/#optional-attributes) field).
 This works well as long as the cardinality of distinct transaction names that the SDK sends is low, for example
 by using the [route of a web framework](https://docs.sentry.io/platforms/javascript/guides/react/configuration/integrations/react-router/) as the transaction name.
 

develop-docs/sdk/data-model/envelopes.mdx

@@ -125,7 +125,7 @@ Envelopes can have a number of headers which are valid in all situations:
 
 `sdk`
 
-: *Object, recommended.* This can carry the same payload as the [`sdk` interface](/sdk/event-payloads/sdk/)
+: *Object, recommended.* This can carry the same payload as the [`sdk` interface](/sdk/data-model/event-payloads/sdk/)
   in the event payload but can be carried for all events. This means that SDK
   information can be carried for minidumps, session data and other submissions.
 

develop-docs/sdk/data-model/event-payloads/contexts.mdx

@@ -206,7 +206,7 @@ confusion about which OS context represents what. So here's some examples:
   the SDK (if at all).
 
   Additionally, the Sentry server will attempt to parse the `User-Agent` header
-  from the event's [Request Interface](/sdk/event-payloads/request/) and create a _secondary_ OS
+  from the event's [Request Interface](/sdk/data-model/event-payloads/request/) and create a _secondary_ OS
   context under the non-default key `"client_os"`.
 
 - In events reported from a JS web frontend, the SDK typically reports no OS
@@ -598,7 +598,7 @@ The `type` and default key is `"cloud_resource"`.
 
 ### Example Cloud Resource Context
 
-The following example illustrates the contexts part of the <Link to="/sdk/event-payloads/">event payload</Link> and omits other attributes for simplicity.
+The following example illustrates the contexts part of the <Link to="/sdk/data-model/event-payloads/">event payload</Link> and omits other attributes for simplicity.
 
 ```json
 {

develop-docs/sdk/data-model/event-payloads/debugmeta.mdx

@@ -29,7 +29,7 @@ system symbols, and is not required for other SDKs.
 ## Debug Images
 
 The list of debug images contains all dynamic libraries loaded into the process
-and their memory addresses. Instruction addresses in the [Stack Trace](/sdk/event-payloads/stacktrace/) are
+and their memory addresses. Instruction addresses in the [Stack Trace](/sdk/data-model/event-payloads/stacktrace/) are
 mapped into the list of debug images in order to retrieve debug files for
 symbolication.
 

develop-docs/sdk/data-model/event-payloads/exception.mdx

@@ -5,7 +5,7 @@ sidebar_order: 2
 
 The Exception Interface specifies an exception or error that occurred in a program.
 
-An <Link to="/sdk/event-payloads/">event</Link> may contain one or more exceptions in an attribute named `exception`.
+An <Link to="/sdk/data-model/event-payloads/">event</Link> may contain one or more exceptions in an attribute named `exception`.
 
 The `exception` attribute should be an object with the attribute `values`
 containing a list of one or more values that are objects in the format described
@@ -41,7 +41,7 @@ description of `ValueError`.
 
 `thread_id`
 
-: An optional value which refers to a thread in the [Thread Interface](/sdk/event-payloads/threads/).
+: An optional value which refers to a thread in the [Thread Interface](/sdk/data-model/event-payloads/threads/).
 
 `mechanism`
 
@@ -50,7 +50,7 @@ created this exception.
 
 `stacktrace`
 
-: An optional stack trace object corresponding to the [Stack Trace Interface](/sdk/event-payloads/stacktrace/).
+: An optional stack trace object corresponding to the [Stack Trace Interface](/sdk/data-model/event-payloads/stacktrace/).
 
 ## Exception Mechanism
 
@@ -206,7 +206,7 @@ information.
 ## Examples
 
 The following examples illustrate multiple ways to send exceptions. Each example
-contains the exception part of the <Link to="/sdk/event-payloads/">event payload</Link> and omits other
+contains the exception part of the <Link to="/sdk/data-model/event-payloads/">event payload</Link> and omits other
 attributes for simplicity.
 
 A single exception:

develop-docs/sdk/data-model/event-payloads/lockreason.mdx

@@ -8,7 +8,7 @@ to determine which other thread is holding the lock in case the current thread i
 
 <Note>
 
-Lock reasons are always part of a [thread](/sdk/event-payloads/threads/). They cannot be declared as a top-level event property.
+Lock reasons are always part of a [thread](/sdk/data-model/event-payloads/threads/). They cannot be declared as a top-level event property.
 
 </Note>
 

develop-docs/sdk/data-model/event-payloads/properties/contexts_trace.mdx

@@ -1,6 +1,6 @@
 `contexts.trace`
 
-: _Recommended_. A Transaction has to have a specific `contexts.trace` entry that contains tracing information. See the [Trace Context documentation](/sdk/event-payloads/contexts/#trace-context).
+: _Recommended_. A Transaction has to have a specific `contexts.trace` entry that contains tracing information. See the [Trace Context documentation](/sdk/data-model/event-payloads/contexts/#trace-context).
 
 ```json
 {

develop-docs/sdk/data-model/event-payloads/properties/spans.mdx

@@ -1,6 +1,6 @@
 `spans`
 
-: _Recommended_. A list of [Spans](/sdk/event-payloads/span/).
+: _Recommended_. A list of [Spans](/sdk/data-model/event-payloads/span/).
 
 ```json
 {

develop-docs/sdk/data-model/event-payloads/replay-recording.mdx

@@ -76,7 +76,7 @@ The payload for `"options"` is a record of configuration name -> configuration v
 
 ### Breadcrumbs
 
-Breadcrumbs are named as such because they are intercepted from the web SDK and forwarded as a custom recording event. They have the same structure as describe in <Link to="/sdk/event-payloads/breadcrumbs/">breadcrumbs interface</Link>.
+Breadcrumbs are named as such because they are intercepted from the web SDK and forwarded as a custom recording event. They have the same structure as describe in <Link to="/sdk/data-model/event-payloads/breadcrumbs/">breadcrumbs interface</Link>.
 
 ```json
 {

develop-docs/sdk/data-model/event-payloads/sdk.mdx

@@ -71,7 +71,7 @@ reference (branch, tag or SHA).
 
 ## Example
 
-The following example illustrates the SDK part of the <Link to="/sdk/event-payloads/">event payload</Link> and omits other
+The following example illustrates the SDK part of the <Link to="/sdk/data-model/event-payloads/">event payload</Link> and omits other
 attributes for simplicity.
 
 ```json