Revert "[8.19] (backport #17154) tbs: Update storage metrics to be reported synchronously in the existing runDiskUsageLoop
method"
#17644
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.
These changes attempted to fix reporting issue for
lsm_size
metrics where we believed were caused by the use of Observable OTEL metrics. The changes introduced a regression where we observed thelsm_size
metrics less frequently than before.After updating metrics collection to remove conflicts (#17525), we determined this was the root issue that was contributing to the infrequent
lsm_size
metrics (not the Observable OTEL metrics). The changes in this PR fixed the regression mention above.The prior implementation with Observable metrics is preferred so we will revert #17275
Draft PR:
How to test these changes
./sendotlp -insecure -endpoint=http://localhost:8200 -secret-token=<token>
storage
should be visible along with other metrics underapm-server.sampling.tail
.apm server config