Added ability to blacklist hosts from being recorded #65
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
colinhumber
force-pushed
the
host-blacklist
branch
3 times, most recently
from
9f2d3dd
to
d6fa015
Compare
colinhumber
force-pushed
the
host-blacklist
branch
from
d6fa015
to
73592fe
Compare
|
This is a super PR! Thanks @colinhumber |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
There are cases where certain endpoints can get hit a lot, causing a lot of chattiness, like with analytics endpoints. This enhancement would allow for certain hosts to be blacklisted and not be recorded.