Skip to content

Commit caa8e5c

Browse files
authored
Merge branch 'master' into feat/layout-centered-content-and-anchored-asides
2 parents 44f3b14 + ab2976c commit caa8e5c

File tree

30 files changed

+491
-307
lines changed

30 files changed

+491
-307
lines changed

app/[[...path]]/page.tsx

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -47,7 +47,12 @@ export const dynamic = 'force-static';
4747
const mdxComponentsWithWrapper = mdxComponents(
4848
{Include, PlatformContent},
4949
({children, frontMatter, nextPage, previousPage}) => (
50-
<DocPage frontMatter={frontMatter} nextPage={nextPage} previousPage={previousPage}>
50+
<DocPage
51+
frontMatter={frontMatter}
52+
nextPage={nextPage}
53+
previousPage={previousPage}
54+
fullWidth={frontMatter.fullWidth}
55+
>
5156
{children}
5257
</DocPage>
5358
)

docs/organization/integrations/cloud-monitoring/aws-lambda/index.mdx

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,6 @@ sidebar_order: 1
44
description: "Learn more about Sentry's AWS Lambda integration and how you can automatically instrument your Node or Python Lambda functions with Sentry without changing your code."
55
---
66

7-
<Alert>
8-
9-
This method of setting up Sentry in your Lambda functions only works if your Lambda functions are run in Node CommonJS (`require` syntax) or in Python.
10-
For all other setups, check out these docs for [Node](/platforms/javascript/guides/aws-lambda/) or [Python](/platforms/python/integrations/aws-lambda/) instead.
11-
12-
</Alert>
13-
147
Connect Sentry to your AWS account to automatically add Sentry error and performance monitoring to your Node/Python Lambda functions.
158

169
## Install
@@ -111,7 +104,7 @@ If you're using [Serverless framework](https://www.serverless.com/), note that t
111104

112105
You can confirm that the output works by inputting `aws lambda get-function-configuration --function-name <yourFunctionName>`. However, when you perform a subsequent `sls deploy` the environment variables aren't maintained even though it looks like the reference to the layer is retained.
113106

114-
You can set the layer definition and environment variables in `serverless.yml` as a workaround, but you'll have to do two things manually: maintain the latest layer version and add the reference to the SDK layer for every function you want "Sentrified".
107+
You can set the layer definition and environment variables in `serverless.yml` as a workaround, but you'll have to do two things manually: maintain the latest layer version and add the reference to the SDK layer for every function you want to add Sentry to.
115108

116109
**Serverless Framework Using Node:**
117110

@@ -123,12 +116,12 @@ provider:
123116
region: <AWS_REGION>
124117
environment:
125118
SENTRY_TRACES_SAMPLE_RATE: "1.0"
126-
SENTRY_DSN: "<SENTRY_DSN>"
127-
NODE_OPTIONS: "-r @sentry/aws-serverless/dist/awslambda-auto"
119+
SENTRY_DSN: "___PUBLIC_DSN___"
120+
NODE_OPTIONS: "--import @sentry/aws-serverless/awslambda-auto"
128121

129122
custom:
130123
layers:
131-
- arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDK:26
124+
- arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDKv10:15
132125
# - arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryNodeServerlessSDK:latest
133126

134127
functions:
@@ -147,11 +140,11 @@ provider:
147140
region: <AWS_REGION>
148141
environment:
149142
SENTRY_TRACES_SAMPLE_RATE: "1.0"
150-
SENTRY_DSN: "<SENTRY_DSN>"
143+
SENTRY_DSN: "___PUBLIC_DSN___"
151144

152145
custom:
153146
layers:
154-
- arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryPythonServerlessSDK:6
147+
- arn:aws:lambda:${self:provider.region}:943013980633:layer:SentryPythonServerlessSDK:167
155148
# - arn:aws:lambda:${self:provider.region:943013980633:layer:SentryPythonServerlessSDK:latest
156149

157150
functions:

docs/platforms/android/session-replay/index.mdx

Lines changed: 0 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -124,22 +124,3 @@ Errors that happen while a replay is running will be linked to the replay, makin
124124
- The replay was rate-limited and couldn't be accepted.
125125
- The replay was deleted by a member of your org.
126126
- There were network errors and the replay wasn't saved.
127-
128-
## FAQ
129-
130-
Q: **Why are parts of my replay not masked?**
131-
132-
A: Text fields, input fields, images, video players and webviews are all masked by default. Local assets, such as colors or vector drawables, aren't masked because the likelihood of these assets containing PII is low. If you encounter a view/component that should be masked by default, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
133-
134-
Q: **Does Session Replay work with Jetpack Compose?**
135-
136-
A: Yes, by default, text, input field, and image composables should be masked. Masking within embedded Android views (`AndroidView`)
137-
in Compose isn't currently supported. If you encounter composables that aren't masked but should be, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
138-
139-
Q: **What's the lowest version of Android supported?**
140-
141-
A: Recording only happens on Android 8 (API level 26) or newer. For devices running an older version, SDK features other than recording work normally.
142-
143-
Q: **Why is my issue missing a replay?**
144-
145-
A: An issue may be missing a replay because the user's device was [offline](/product/explore/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video.
Lines changed: 31 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,31 @@
1+
---
2+
title: Troubleshooting
3+
sidebar_order: 5503
4+
notSupported:
5+
description: "Troubleshooting issues with Session Replay"
6+
---
7+
8+
<Expandable title="Why are parts of my replay not masked?" permalink>
9+
10+
Text fields, input fields, images, video players, and webviews are all masked by default. Local assets, such as colors or vector drawables, aren't masked because the likelihood of these assets containing PII is low. If you encounter a view or component that should be masked by default, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
11+
12+
</Expandable>
13+
14+
<Expandable title="Does Session Replay work with Jetpack Compose?" permalink>
15+
16+
Yes, by default, text, input field, and image composables should be masked. Masking within embedded Android views (`AndroidView`)
17+
in Compose isn't currently supported. If you encounter composables that aren't masked but should be, consider opening a [GitHub issue](https://github.com/getsentry/sentry-java/issues).
18+
19+
</Expandable>
20+
21+
<Expandable title="What's the lowest version of Android supported?" permalink>
22+
23+
Recording only happens on Android 8 (API level 26) or newer. For devices running an older version, SDK features other than recording work normally.
24+
25+
</Expandable>
26+
27+
<Expandable title="Why is my issue missing a replay?" permalink>
28+
29+
An issue may be missing a replay because the user's device was [offline](/product/explore/session-replay/mobile#frequently-asked-questions) while `sessionSampleRate` was specified, your project/organization was rate-limited, or (in rare cases) the device failed to capture the replay video.
30+
31+
</Expandable>

0 commit comments

Comments
 (0)