feat(py-client): Add Python client implementation #153
Conversation
This file contains hidden or 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
lcian
commented
Oct 29, 2025
…on-client-initial-code
…on-client-initial-code
jan-auer
approved these changes
Oct 30, 2025
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.
Description
Adds an initial implementation for the Python client.
This is almost a 1 to 1 port of the code that currently lives in
sentry.The only change is that the the metrics backend has been abstracted, using an approach similar to what we do with
arroyoinsentry.That is, we define a
MetricsBackendinterface that the user will need to implement and pass to the client if they want to record metrics. By default,NoOpMetricsBackendwill be used.The
ClientBuilderandClientnow take aMetricsBackendparameter which they'll pass to themeasure_storage_operationcontext manager.Next steps
Issues
Close FS-169
Close FS-174