apollo_batcher: refactor commit metrics to read the label from the task output#14384
Conversation
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
PR SummaryLow Risk Overview
Reviewed by Cursor Bugbot for commit 6354afd. Bugbot is set up for automated code reviews on this repo. Configure here. |
…sk output The result-collection loops use the new CommitterTaskOutput::task_label() instead of hardcoding CommitBlock, and both commit labels share record_commit_block_metric ahead of adding a second commit endpoint. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
fdc71fe to
8fb9782
Compare
daf5ca3 to
6354afd
Compare
itamar-starkware
left a comment
There was a problem hiding this comment.
One non blocking comment
| // TODO(Ariel): Add dedicated metrics once we use os_input in prod. | ||
| COMMITMENT_MANAGER_COMMIT_BLOCK_LATENCY.increment(task_duration); | ||
| COMMITMENT_MANAGER_COMMIT_BLOCK_COUNT.increment(1); | ||
| record_commit_block_metric(task_duration, height, task_type) |
There was a problem hiding this comment.
Non blocking - we should consider create another metric for that.

The result-collection loops use the new CommitterTaskOutput::task_label()
instead of hardcoding CommitBlock, and both commit labels share
record_commit_block_metric ahead of adding a second commit endpoint.
Co-Authored-By: Claude Opus 4.8 (1M context) noreply@anthropic.com