-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Performance for Serverless on Python #2389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/sentry/sentry-docs/4n6mometq/sentry.dev |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Check out Sentry's [AWS sample apps](https://github.com/getsentry/examples/tree/master/aws-lambda/python) for detailed examples. | ||
|
||
<Alert level="info" title="Note"><markdown> | ||
|
||
If you are using another web framework inside of AWS Lambda, the framework might catch those exceptions before we get to see them. Make sure to enable the framework specific integration as well, if one exists. See [_Integrations_](/platforms/python/#integrations) for more information. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggestion to clarify:
If you are using another web framework inside of AWS Lambda, the framework might catch those exceptions before we get to see them. Make sure to enable the framework specific integration as well, if one exists. See [_Integrations_](/platforms/python/#integrations) for more information. | |
If you are using another web framework inside of AWS Lambda, the framework might catch those exceptions before they are sent to Sentry. As a result, we recommend enabling the framework-specific integration as well, if one exists. See [_Integrations_](/platforms/python/#integrations) for more information. |
## Behavior | ||
|
||
With the AWS Lambda integration enabled, the Python SDK will: | ||
|
||
- Automatically report all exceptions from your Lambda Functions | ||
- Automatically report all exceptions and transactions from your Lambda Functions | ||
- You can control transactions sample rate using `traces_sample_rate`. You can learn more about transactions in [Distributed Tracing](/performance-monitoring/distributed-tracing/#traces-transactions-and-spans) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note - the content for this setting is forthcoming in PR 2376.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok let's not merge this PR before that one then. It seems that even with the current version of #2376 this will 404, so we'll have to re-review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I took in the latest and the link still looks valid. @PeloWriter do you want me to update anything specific?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This link may be more helpful. So perhaps edit to:
- You can control the the representative sample of transactions you send to Sentry by filtering transaction events
Co-authored-by: Fiona <[email protected]>
Co-authored-by: Fiona <[email protected]>
## Behavior | ||
|
||
With the AWS Lambda integration enabled, the Python SDK will: | ||
|
||
- Automatically report all exceptions from your Lambda Functions | ||
- Automatically report all exceptions and transactions from your Lambda Functions | ||
- You can control transactions sample rate using `traces_sample_rate`. You can learn more about transactions in [Distributed Tracing](/performance-monitoring/distributed-tracing/#traces-transactions-and-spans) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok let's not merge this PR before that one then. It seems that even with the current version of #2376 this will 404, so we'll have to re-review.
This reverts commit a3a507c.
Docs has many broken/dead fragment URLs because an anchored section of a page moved or was renamed.
…also centering logo on mobile. (#2187)
Co-authored-by: Fiona <[email protected]> Co-authored-by: Bruno Garcia <[email protected]> Co-authored-by: Manoel Aranda Neto <[email protected]>
Co-authored-by: Fiona <[email protected]>
- Expose dropdown for Product navigation - Move all product pages into /product/ - Re-order sidebar to push relevant (vs marketing/discovery) docs to the top
…ocs (#2376) Also a bunch of reorganization, and reworking of some (but not all) of the JS performance docs.
@ajjindal the rebase is messed up, this PR now contains too many unrelated changes to be reviewable |
Creating a different PR |
send-default-pii