Add ability to set sampling rules by resource #3513
Closed
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.
What does this PR do?
This PR adds support for sampling based on resources. It does not change anything about when the rules / matchers / etc are evaluated. It just compares against the existing
resource
value in addition to thename
andservice
values.Default behavior continues to be matching all resources
Motivation:
I was looking for a way to ensure that everything from a given resource within a service was sampled at a
1.0
rate. I also noticed this feature existed in the python interface (added here) so it seemed there would be no fundamental objection.Additional Notes:
How to test the change?
Mirrored the existing testing for
name
andservice
. Additionally added in test cases for the combinations of(name,service,resource)
patterns.For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!