Skip to content

Initial setup: Add structure, README, and Fusaka index for metric standardization#3

Open
will-corcoran wants to merge 1 commit intoethereum:masterfrom
will-corcoran:master
Open

Initial setup: Add structure, README, and Fusaka index for metric standardization#3
will-corcoran wants to merge 1 commit intoethereum:masterfrom
will-corcoran:master

Conversation

@will-corcoran
Copy link

This PR sets up the EL metrics repo to mirror beacon-metrics:

  • Added README with purpose, usage, and hard fork index.
  • Created fusaka/fusaka-index.md for Fusaka EIPs (Osaka EL focus).
  • Includes proposed EL metrics for PeerDAS/GetBlobsV2.
  • Aims for unified monitoring across layers.

@SunnysidedJ
Copy link

SunnysidedJ commented Jul 21, 2025

Adding corresponding PR from CL side: ethereum/beacon-metrics#19

Could we discuss structuring by functional scope instead of Fork/EIPs?
Re-pasting part of Sunnyside Lab's previous comment here.
[structuring by Fork/EIP] doesn't seem to be that user-friendly. 1) Some metrics may be common or generic across different EIPs. 2) Following different forks for all the change history would be another pain point. Consider Ethereum in 5 years: the number of forks to follow will double (the specs repo). Only looking at metrics of functionality they debug seems to be more intuitive approach for users imo. Also, most client teams seem to structure it by functionality as well.


| Metric | Usage | Sample collection event | Besu | Erigon | Geth | Nethermind | Reth |
|--------|-------|-------------------------|------|--------|------|------------|------|
| `execution_engine_getblobs_request_total` | Number of blobs requested via getBlobsV2 | Each invocation of getBlobsV2 | □ | □ | □ | □ | □ |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we make this more generic such that we capture any getBlobs version and have the version as an attribute

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

theres a new getBlobsV3 coming

| Metric | Usage | Sample collection event | Besu | Erigon | Geth | Nethermind | Reth |
|--------|-------|-------------------------|------|--------|------|------------|------|
| `execution_engine_getblobs_request_total` | Number of blobs requested via getBlobsV2 | Each invocation of getBlobsV2 | □ | □ | □ | □ | □ |
| `execution_engine_getblobs_available_total` | Number of blobs requested via getBlobsV2 that are present in the blobpool | Each invocation of getBlobsV2 | □ | □ | □ | □ | □ |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not clear to me how this is different from the metric above execution_engine_getblobs_request_total.


| Fork Half | Activation Epoch | SFI'd EIPs | EIPs with Metrics | Meta EIP |
|-----------|------------------|------------|-------------------|----------|
| Osaka (EL) | TBD (Late 2025) | 13 | 1 | [EIP-7607: Hardfork Meta - Fusaka](https://eips.ethereum.org/EIPS/eip-7607) |
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This needs updating

- **Activation Details**: Epoch TBD; expected late 2025.
- **Blog Link**: TBD (Check ethereum.org for announcements).

## EIPs Scheduled for Inclusion
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not really sure why we need all this info in this repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants