feat(transport): Client Report Support #1181
Merged
+360
−52
Conversation
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
kamilogorek
reviewed
Sep 2, 2021
Co-authored-by: Kamil Ogórek <kamil.ogorek@gmail.com>
mitsuhiko
changed the title
kamilogorek
suggested changes
Sep 10, 2021
kamilogorek
approved these changes
Sep 13, 2021
This was referenced Feb 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for client reports to the python SDK. This will cause the SDK to send a report once every 30 seconds or once a minute. After 30 seconds it will attempt to attach the report to a scheduled envelope if there is one, after 60 seconds it will send it as a separate envelope. Attempts of sending are only made as a byproduct of attempted event / envelope sending or an explicit flush.
The feature can be turned off via the
send_client_reportsoption which is on by default.Refs: getsentry/relay#1074