-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
21 changed files
with
953 additions
and
1,759 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -8,3 +8,4 @@ Here are some guides on developing and testing mobu. | |
|
||
idfdev | ||
github | ||
sentry |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
###### | ||
Sentry | ||
###### | ||
|
||
Footguns | ||
======== | ||
|
||
* `~sentry_sdk.Transaction.set_data` will `silently not do anything <https://github.com/getsentry/sentry-python/issues/930>`_. | ||
All calls to ``set_data`` must be called on `~sentry_sdk.Span` instances. | ||
|
||
* Unhandled errors will be reported in the scope in which they are sent to sentry, NOT the scope in which they are thrown. | ||
* This means that if you call `~sentry_sdk.new_scope`, set tags on the scope, and an exception is raised but not explicitly captured in that scope, the `tags will not show up in the Sentry UI <https://github.com/getsentry/sentry-python/issues/2857>`_. | ||
* This also means that the error events will occur in the transaction that is active when they are handled, not the active transaction when they are raised. | ||
|
||
* Alerts that are set to fire when an issue is first created, or regressed, will do so once an event that matches that issue occurs in `ANY environment <https://github.com/getsentry/sentry/issues/21612>`_, not every environment. | ||
This means that if an the first event from an issue comes from a development environment, the alert will be triggered, and will not trigger again when the first event comes from a production environment. | ||
To have such an alert trigger per-environment, we need to `change the fingerprint of the event <https://github.com/getsentry/sentry/issues/64354#issuecomment-1927839632>`_ to include the environment, which can be done by using the the ``add_environment_to_fingerprint`` helper method as a `before_send` method in your Sentry initialization. | ||
|
||
* Calling `~sentry_sdk.` |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
Oops, something went wrong.