Expose batch progress traces on the metrics route #5956
+79
−3
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.
This PR exposes more information to the metrics route, helping us debug what actually takes time when indexing documents. It can also be helpful to identify which part of the code is being executed by comparing it with other CPU/Memory/Disk graphs.
I published a prototype so that we can test on staging and expose a good Grafana visualization.
To do
humantimeand use a dependency we already depend on.a booleancompletion ratio gauges for the currently processing step (and not the whole history).The batch running progress trace
The last batch progress trace metric