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.
#1524 introduced a fix to queuing issues and ends up doing atFixedDelay rather than atFixedRate. The logic is sound enough, but leads to frustrating unanticipated issues.
Issues with binning exist in Graphite (and probably others). These accumulate "drift", and so metric gaps occur. See #2664 for two examples.
Hence allowing this to be configurable is desirable.
This is the lamest but easiest form of this - moving the method to an overridable method.
Usage would be (example graphite reporter)
Pseudo code:
I looked at other options but they all involved breaking or overloading constructors too much:
There's a lot of unfortunate outdated api design in DropWizard
Those are not fixable without a major breaking version change. But we can at least offer something here.