Add metric to track the duration of indexing/replaying EVM blocks

[m-Peter]

To get some more insights about the throughput of the EVM event ingestion engine, we should add a metric to track the duration of indexing/replaying each incoming EVM block and its transactions. Given that on mainnet the block production rate is 0.8 seconds, the ingestion engine should strictly take less time than that, to index/replay an EVM blocks. Otherwise, it will lag behind.

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• Track time taken to fully ingest EVM blocks #751

Related Issues

• Investigate feasibility of storing EVM registers on transaction level #729
• Aggregate the parsed EVM.BlockExecuted & EVM.TransactionExecuted event payloads #627
• Sort EVM related events by their EventIndex #621

🔗 Related PRs

#406 - Add evm_block_height metric [merged]
#752 - Track time taken to fully ingest an EVM block in the local state index [merged]

👤 Suggested Assignees

• m-Peter
• illia-malachyn

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!