ref(metrics): Stop logging relative bucket size [INGEST-1132] #1302
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.
In an ongoing effort to reduce the number of statsd metrics we emit (see also #1295), remove the
BucketRelativeSize
, which was emitted in a loop for every bucket flush.Beside emitting a lot of statsd metrics, the
relative_size()
function was also a less precise approximation than the newcost()
function, which IMO can be removed.#skip-changelog