Log to logstash when VIP Search ratelimiting starts. #1916
Merged
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
We need a way to know if VIP Search is currently rate limited or not on specific sites when debugging. By logging to logstash when rate limiting kicks off and knowing how long rate limiting lasts, it makes debugging much easier since you don't need to guess.
Changelog Description
Log to logstash when VIP Search rate limiting begins
To assist with debugging VIP Search related issues, we need an easy way to determine if rate limiting is currently in effect for queries or indexing operations. The easiest way to accomplish this right now is by logging when rate limiting starts to logstash.
#1916
Checklist
Please make sure the items below have been covered before requesting a review:
Steps to Test