# Initial Consensus Layer FOCIL Metrics & Dashboard
This document provides an overview of the FOCIL ([EIP-7805](https://eips.ethereum.org/EIPS/eip-7805)) metrics, including a description of each metric and screenshots for Lodestar. The dashboard was generated from a Kurtosis configuration with the following setup:

participants:
- el_type: geth
    el_image: jihoonsg/geth-focil:dffb273
    cl_type: lodestar
    cl_image: sibkatya/lodestar:focil-metrics-0529a69
    count: 2
network_params:
  genesis_delay: 20
  electra_fork_epoch: 0
  eip7805_fork_epoch: 1
  num_validator_keys_per_node: 256
snooper_enabled: true
additional_services:
  - dora
  - tx_fuzz
  - spamoor
  - prometheus_grafana
port_publisher:
  additional_services:
    enabled: true
    public_port_start: 65500
spamoor_params:
  spammers:
    - scenario: eoatx
      config:
        throughput: 100
    - scenario: uniswap-swaps
      config:
        throughput: 100
    - scenario: blob-combined
      config:
        throughput: 5
global_log_level: info

The json version of the dashboard can be found [here](https://github.com/ethpandaops/ethereum-package/pull/986/commits/842da84a7233b98ca76b49360b7b932a7213098e).

## Dashboard filters

The dashboard's graphs can be filtered by consensus clients and their named instances, referred to as **jobs** in Kurtosis. Some metrics also include a **source** label, which allows you to group data by the origin of the inclusion list. Using the `Sum_by` filter provides granular insights into where the lists are coming from, such as `gossip` or `api`.

## Dashboard sections

### 1. Publishing and Broadcasting
This section monitors the distribution of inclusion lists. The number of published lists should align with the `IL_COMMITTEE_SIZE` (currently 16). It also shows inclusion lists received via gossip and other potential sources.

| Name | Type | Description |
| :--- | :--- | :--- |
| `beacon_inclusion_lists_published_total` | counter | Total number of published inclusion lists. |
| `beacon_inclusion_lists_received_total` | counter | Total number of received inclusion lists. |
| `beacon_inclusion_list_transactions_received_total` | counter | Total number of transactions in received inclusion lists. |
| `beacon_inclusion_lists_arrival_time_seconds` | histogram | Inclusion list arrival time since the beginning of the slot. |


### 2. Validation
This section provides insights into the validation process for inclusion lists, covering both inclusion lists being published and those being received from the network. You can track the number and size of both valid and invalid lists, with the reject reason for invalid lists available as a metric label.

| Name | Type | Description |
| :--- | :--- | :--- |
| `beacon_inclusion_lists_valid_total` | counter | Total number of valid inclusion lists. |
| `beacon_inclusion_lists_valid_size_bytes_total` | counter | Total size of valid inclusion lists in bytes. |
| `beacon_inclusion_lists_invalid_total` | counter | Total number of invalid inclusion lists. |
| `beacon_inclusion_lists_invalid_size_bytes_total` | counter | Total size of invalid inclusion lists in bytes. |
| `beacon_inclusion_lists_validation_time_seconds` | histogram | Time taken to validate inclusion lists. |


### 3. Fork Choice

These metrics help to monitor FOCIL integrated into the fork choice rule. They help identify potential issues, such as equivocating inclusion lists or blocks that fail to satisfy their associated inclusion lists.

| Name | Type | Description |
| :--- | :--- | :--- |
| `beacon_inclusion_lists_equivocating_total` | counter | Total number of equivocating inclusion lists. |
| `beacon_inclusion_list_unsatisfied_blocks_total` | counter | Total number of unsatisfied inclusion list blocks. |


### 4. Engine API

This section monitors the communication between the consensus client and the execution client. It tracks key Engine API calls and the number of inclusion list transactions being sent to the payload.

| Name | Type | Description |
| :--- | :--- | :--- |
| `beacon_engine_getInclusionListV1_requests_total` | counter | The total number of `engine_getInclusionListV1` requests sent to the execution client. |
| `beacon_engine_getInclusionListV1_requests_duration_seconds` | histogram | The duration of `engine_getInclusionListV1` requests. |
| `beacon_engine_forkchoiceUpdatedV4_requests_total` | counter | The total number of `engine_forkchoiceUpdatedV4` requests sent to the execution client. |
| `beacon_engine_forkchoiceUpdatedV4_requests_duration_seconds` | histogram | The duration of `engine_forkchoiceUpdatedV4` requests. |
| `beacon_inclusion_list_transactions_sent_to_payload_total` | counter | The total number of transactions from inclusion lists sent to the execution payload. |


:::info
**Open Questions:**

1. Do we need a `reason` label for `beacon_inclusion_lists_invalid_total` metric? It would probably be better to investigate it with the logs, as not many invalid ILs are expected.
2. Do we need `beacon_inclusion_lists_invalid_size_bytes_total` metric?
3. What metrics should have `source` label?
4. What other metrics can be useful to monitor EIP-7805?
:::