Skip to content

Commit a832d7e

Browse files
inventarSarahinventarSarah
authored
Merge branch 'master' into smi/quick-start/nextjs
2 parents 37d0c9e + 3ba8854 commit a832d7e

File tree

667 files changed

+2242
-1991
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

667 files changed

+2242
-1991
lines changed

‎develop-docs/ingestion/relay/transaction-span-ratelimits.mdx‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -69,19 +69,19 @@ Relay stage: customer managed, PoP-Relay or Processing-Relay. Until spans are ex
6969
should count the contained spans and generate an outcome with the contained span quantity + 1, for the segment span
7070
which would be generated from the transaction itself.
7171

72-
<Note>
72+
<Alert>
7373
While it is desirable to have span counts correctly extracted from dropped transactions, it may not be feasible
7474
to do so at any stage of the processing pipeline. For example, it may not be possible to do so (malformed transactions)
7575
or simply too expensive to compute.
76-
</Note>
76+
</Alert>
7777

7878
After spans have been extracted, the transaction is no longer a container of span items and just represents itself,
7979
thus, a dropped transaction with spans already extracted only generates outcomes for the total transactions and
8080
indexed transaction categories.
8181

82-
<Note>
82+
<Alert>
8383
Span quotas are equivalent to transactions quotas, so all the above also applies for a span quota.
84-
</Note>
84+
</Alert>
8585

8686

8787
## Examples

‎develop-docs/integrations/azuredevops/index.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -25,12 +25,12 @@ When configuring the app, use the following values:
2525
| Supported account types | Accounts in any organizational directory |
2626
| Redirect URI | `{YOUR_DOMAIN}/extensions/vsts/setup` |
2727

28-
<Note>
28+
<Alert>
2929

3030
Take note of your App ID as we'll need it later.
3131
![App ID](./app-id.png)
3232

33-
</Note>
33+
</Alert>
3434

3535
Next go to Manager -> API Permissions to add the following permissions:
3636
* Azure DevOps (`vso.code`, `vso.graph`, `vso.work_item`, `vso.service_endpoint`)

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,11 +6,11 @@ Represents an instance of a held lock (monitor object) in a thread. Typically, t
66
to determine which other thread is holding the lock in case the current thread is blocked. In languages like
77
`Java` or `Kotlin` this typically will be represented by a `java.lang.Object` type.
88

9-
<Note>
9+
<Alert>
1010

1111
Lock reasons are always part of a [thread](/sdk/data-model/event-payloads/threads/). They cannot be declared as a top-level event property.
1212

13-
</Note>
13+
</Alert>
1414

1515
## Attributes
1616

‎develop-docs/sdk/platform-specifics/javascript-sdks/browser-tracing.mdx‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ sidebar_order: 10
66

77
The tracing behavior in our browser SDKs is somewhat unique and significantly differs from tracing in the backend. This page collects the most important aspects.
88

9-
<Note>
9+
<Alert>
1010
The aspects described in this document apply to all browser SDKs. This
1111
includes `@sentry/browser` and all SDKs building on top of it like
1212
`@sentry/react`, `@sentry/angular` or `@sentry/vue` but also the client-side
1313
parts of meta frameworks like `@sentry/nextjs`.
14-
</Note>
14+
</Alert>
1515

1616
Please note that any kind of automatic tracing instrumentation in the browser requires the `browserTracingIntegration()` to be added to the SDK configuration.
1717
The default configuration of the SDK does not include any performance or tracing-related instrumentation to save on [bundle size](../bundle-size) for errors-only users.
@@ -103,13 +103,13 @@ There are sometimes discrepancies between the values we capture and the values t
103103
Generally speaking, most web vitals are accumulated while the pageload span is active and captured when we _end_ the pageload span. This works well for vitals that stabilize themselves very early in the lifecycle but
104104
it leads to discrepancies for vitals that are still changing after the pageload span ends. This is the case for `LCP` and `CLS` in particular.
105105

106-
<Note>
106+
<Alert>
107107
At the time of writing, we're transitioning to a [more sophisticated `LCP` and
108108
`CLS` capturing
109109
technique](https://github.com/getsentry/sentry-javascript/issues/12714) that
110110
should improve the accuracy of these metrics. It will essentially work like
111111
`INP` collection works today.
112-
</Note>
112+
</Alert>
113113

114114
### Interaction To Next paint (INP)
115115

@@ -134,13 +134,13 @@ This tracing model has a couple of consequences that are important to understand
134134
- **Quota Management**: Since the trace state does not change throughout a single page or route, the sampling decision of the initial span is carried over for all subsequent events. This means that the sampling decision is only made once per page or route and is not reevaluated for each event. Furthermore, subsequent http (`fetch` or `XmlHttpRequest`) also propagate this sampling decision to potential downstream services. This can lead to a higher number of events being sent to Sentry than before.
135135
- **Long-lived Traces**: Not every web application features navigations (hard or soft). For pages where users simply remain on one page without making navigations (e.g. a chat application), the trace id will remain constant for the entire duration of the user journey. This can lead to very long-lived traces that can potentially grow very large.
136136

137-
<Note>
137+
<Alert>
138138

139139
As outlined above, some of the consequences have negative product or UX implications.
140140
This is a known issue and we're working on an update to the trace lifetime model to address these issues.
141141
However, this is a complex topic and we're still in the process of evaluating the best solution.
142142

143-
</Note>
143+
</Alert>
144144

145145
## Trace Propagation
146146

‎develop-docs/sdk/telemetry/check-ins.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -135,10 +135,10 @@ result in a poor DX.
135135

136136
### Schedule configuration
137137

138-
<Note>
138+
<Alert>
139139
This configuration format differs slightly from what is accepted in the
140140
monitors frontend APIs.
141-
</Note>
141+
</Alert>
142142

143143
`type`
144144

‎develop-docs/sdk/telemetry/sessions/index.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,11 +3,11 @@ title: Sessions
33
sidebar_order: 6
44
---
55

6-
<Note>
6+
<Alert>
77

88
Looking for Sentry's **Session Replay**? Click <a class href="https://docs.sentry.io/product/session-replay/">here</a> to learn more.
99

10-
</Note>
10+
</Alert>
1111

1212
For basic health tracking Sentry accepts <Link to="/sdk/data-model/envelopes/">envelopes</Link>
1313
containing session update events. These session update events can be used to

‎develop-docs/sdk/telemetry/traces/index.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ Reference implementations:
1414
- [JavaScript SDK](https://github.com/getsentry/sentry-javascript/tree/master/packages/core/src/tracing)
1515
- [Python SDK](https://github.com/getsentry/sentry-python/blob/master/sentry_sdk/tracing.py)
1616

17-
<Note>
17+
<Alert>
1818

1919
This document uses standard interval notation, where `[` and `]` indicates closed intervals, which include the endpoints of the interval, while `(` and `)` indicates open intervals, which exclude the endpoints of the interval. An interval `[x, y)` covers all values starting from `x` up to but excluding `y`.
2020

21-
</Note>
21+
</Alert>
2222

2323
## SDK Configuration
2424

‎docs/account/user-settings/index.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -14,11 +14,11 @@ Security Settings include options to reset a password, sign out of all devices,
1414

1515
After setting up your two-factor authentication codes, click "View Codes" to download, print, or copy your codes to a secure location. If you cannot receive two-factor authentication codes in the future, such as if you lose your device, use your recovery codes to access your account.
1616

17-
<Note>
17+
<Alert>
1818

1919
Clicking "Sign out of all devices" will end your sessions with any device logged in to Sentry using your account.
2020

21-
</Note>
21+
</Alert>
2222

2323
## Notifications
2424

‎docs/api/auth.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -51,8 +51,8 @@ As an example, to get information about the project which your key is bound to,
5151
curl -u {API_KEY}: https://sentry.io/api/0/organizations/{organization_slug}/projects/
5252
```
5353

54-
<Note>
54+
<Alert>
5555

5656
You **must** pass a value for the password, which is the reason the `:` is present in our example.
5757

58-
</Note>
58+
</Alert>

‎docs/api/ratelimits.mdx‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -32,8 +32,8 @@ Every API request response includes the following headers:
3232

3333
The rate limiter looks at the caller's identity instead of the bearer token or cookie. As such, the rate limit cannot be bypassed by generating multiple tokens.
3434

35-
<Note>
35+
<Alert>
3636

3737
Polling the API for updates is likely to quickly trigger rate limiting. We recommend using our [webhooks](/organization/integrations/integration-platform/webhooks/), if possible.
3838

39-
</Note>
39+
</Alert>

0 commit comments

Comments
 (0)