feat: Allow for Custom Status Codes to Be Sampled #103
Conversation
This file contains hidden or 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
I have a public web app that has an expected number of 401s/422s/etc that are not being sampled out by Uinta. This PR makes it so I can pass in a list of allowed HTTP status codes to be considered as part of the 'success' logs, and sampled according to the existing logic.
epinault
reviewed
Sep 12, 2025
epinault
approved these changes
Sep 12, 2025
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.
I have a public web app that has an expected number of 401s/422s/etc that are not being sampled out by Uinta, and end up polluting my logs. This PR makes it so I can pass in a list of allowed HTTP status codes to be considered as part of the 'success' logs, and sampled according to the existing logic.