Add workload id as metric to builder #315
Open
+304
−1
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.
📝 Summary
Adds workload ID computation and metrics to the builder for TEE workload
identification. The workload ID uniquely identifies a TEE workload based on its measurement registers
and is now exposed as a Prometheus metric for monitoring and observability.
Key changes:
a unique workload identifier
💡 Motivation and Context
When running the builder in a TEE, it's important to be able to identify and monitor which specific
workload/measurement is running
By exposing this as a metric, operators can:
The implementation follows the
https://github.com/flashbots/flashtestations/tree/7cc7f68492fe672a823dd2dead649793aac1f216 and same workload id from solidity and rust verified.
✅ I have completed the following steps: