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.

Sign up for GitHub

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

Jump to bottom

Conditional tracing for credit_flow events #137

Closed
michaelklishin opened this issue Apr 30, 2015 · 0 comments · Fixed by #139
Closed

Conditional tracing for credit_flow events #137

michaelklishin opened this issue Apr 30, 2015 · 0 comments · Fixed by #139
Assignees
@michaelklishin
Labels
effort-low enhancement
Milestone
3.6.0

Comments

@michaelklishin
Copy link
Member

We need to have a way to collect events about processes being blocked and unblocked by credit_flow. However, it is important to not introduce runtime overhead while doing so. Since this feature is intended for contributors and not users (at least for now), it was agreed that a pre-processor condition would be sufficient.
@michaelklishin michaelklishin self-assigned this Apr 30, 2015
@michaelklishin michaelklishin mentioned this issue May 2, 2015
Merged
@dumbbell dumbbell added this to the 3.6.0 milestone May 7, 2015
dcorbacho pushed a commit that referenced this issue Nov 18, 2020
@michaelklishin
Merge pull request #137 from rabbitmq/rabbitmq-trust-store-80
dfbc38f 
Be more defensive with TLS socket operations when opening connections
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@michaelklishin michaelklishin

Labels
effort-low enhancement
Projects
None yet
Milestone
3.6.0
Development

Successfully merging a pull request may close this issue.

Introduce conditional tracing of credit_flow events rabbitmq/rabbitmq-server
2 participants
@michaelklishin @dumbbell