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

Investigate gevent transport for Sentry #792

Open
dsuch opened this issue Oct 25, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@dsuch
Copy link
Collaborator

commented Oct 25, 2017

Right now we don't specify explicitly which transport to use for integration with Sentry:

https://github.com/zatosource/zato/blob/main/code/zato-server/src/zato/server/main.py#L229

However, per documentation, the gevent one should be used because it won't be chosen by Sentry itself:
https://docs.sentry.io/clients/python/transports/

@dsuch dsuch added this to the 3.0 milestone Oct 25, 2017

@dsuch dsuch modified the milestone: 3.0 Jun 2, 2018

@dsuch dsuch self-assigned this Jun 4, 2018

@dsuch dsuch modified the milestones: 3.0, 3.1 Jun 12, 2018

@zatosource zatosource removed this from the 3.1 milestone Jun 20, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.