Log GetPayload events during block building

[ferranbt]

Describe the feature

This is an example of the Reth logs at the time of block building

2025-05-13T13:38:49.661049Z DEBUG provider::static_file: Commit segment=Headers path="/root/.local/share/reth/901/static_files/static_file_headers_0_499999" duration=3.712541ms
2025-05-13T13:38:49.661947Z DEBUG engine::tree: received new engine message msg=Request(ForkchoiceUpdated { state: ForkchoiceState { head_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23, safe_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23, finalized_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23 }, has_payload_attributes: true })
2025-05-13T13:38:49.662137Z  INFO reth_payload_builder::service: New payload job created id=0x03899bddc6660b56 parent=0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23
2025-05-13T13:38:49.662142Z DEBUG reth::cli: Event: Handler(ForkchoiceUpdated(ForkchoiceState { head_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23, safe_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23, finalized_block_hash: 0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23 }, Valid))
2025-05-13T13:38:49.662184Z  INFO reth_node_events::node: Forkchoice updated head_block_hash=0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23 safe_block_hash=0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23 finalized_block_hash=0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23
2025-05-13T13:38:49.662243Z DEBUG payload_builder: building new payload id=0x03899bddc6660b56 parent_header=0xf5f34b79288aab1b07d05799cbc69b97b61d9751bf2ba85456bbc458e08eff23 parent_number=5

It logs things like the start of the block building routine New payload job created or when the FCU gets updated Forkchoice updated .... My feature request is for Reth to log also the GetPayload call from the builder.

[mattsse]

we have these here

reth/crates/optimism/rpc/src/engine.rs

Line 331 in dfbbc2e

trace!(target: "rpc::engine", "Serving engine_getPayloadV2");

but we should also add the payload_builder target to these logs:

reth/crates/payload/builder/src/service.rs

Line 289 in dfbbc2e

trace!(%id, "resolving payload job");

reth/crates/payload/builder/src/service.rs

Line 296 in dfbbc2e

trace!(%id, "terminated resolved job");

@ferranbt which targets are you using rn?

[ferranbt]

info and debug. To use trace seems a little too much for us. My assumption is that if someone is running a block builder, he might want some of those logs at least on debug.

Something like

reth/crates/optimism/rpc/src/engine.rs

Line 331 in dfbbc2e

trace!(target: "rpc::engine", "Serving engine_getPayloadV2");

with the payload id would be useful.

[fantasyup]

Let me take this :)