Skip to content
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

Feature: Call tagging #30

Closed
wants to merge 4 commits into from
Closed

Feature: Call tagging #30

wants to merge 4 commits into from

Conversation

stevenbunting
Copy link
Collaborator

The tagging feature can be used to add important context to the events you fire to supergood that may not be present in the request/response structure itself. Those tags will be applied to all calls made within the context manager. These can be made across threads without concern for tags bleeding across threads as well. In the following example:

with SGClient.tagging({'variant': 'treatment1'}):
    requests.get(url1)
    requests.get(url2)
requests.get(url3)

The event associated with url1 and url2 would have the treatment1 context available to it for data slicing. The url3 event would not have that context available

@stevenbunting
Copy link
Collaborator Author

Closing, doing this in a different PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant