-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Change Zipkin receiver behavior according to host ingestion status #148
Change Zipkin receiver behavior according to host ingestion status #148
Conversation
Codecov Report
@@ Coverage Diff @@
## master #148 +/- ##
==========================================
+ Coverage 73.05% 73.69% +0.63%
==========================================
Files 95 95
Lines 5789 5827 +38
==========================================
+ Hits 4229 4294 +65
+ Misses 1350 1318 -32
- Partials 210 215 +5
Continue to review full report at Codecov.
|
var responseStatusCode int | ||
var zPageMessage string | ||
if zr.backPressureState == configmodels.EnableBackPressure { | ||
responseStatusCode = http.StatusServiceUnavailable |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In the future we can also try to be smart and calculate queue drain speed and the time it will be required for it to drain to certain reasonable level and report that in "Retry-After" header. Not for this PR, just something to consider for later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This change makes the Zipkin receiver respond to received data according to the host status regarding ingestion.
9048b08
to
47e0826
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
This change makes the Zipkin receiver respond to received data according to the host ingestion status.
This is part of #76