September 2022 Nodewatch Maintenance Tracker

[philknows]

On September 15, 2022, ChainSafe officially launched its effort to complete some maintenance upgrades for Nodewatch.io with potential for future implementations. Our main initial effort (as tracked by this issue) will be to prioritize relevance for Nodewatch and for it to be a useful tool going forward post-merge.

The following primary tasks will be targeted for upkeep:

• Excessive IP Data Fetching nodewatch-api#229
• Add Basic Metrics nodewatch-api#231
• Configure Datadog nodewatch-api#239
• Update terminology
  • Remove all references to Eth2 on UI  #61
• Remove irrelevant content
  • Remove Altair content #60
• Test and refine data collected and distributed by eth2-crawler for accuracy
  • Add ForkDigest filter nodewatch-api#205
  • Modification of agent version for Lodestar nodewatch-api#200
  • Review client type distribution collection nodewatch-api#208
  • Review operating systems distribution nodewatch-api#209
  • Review network types distribution nodewatch-api#210
  • Review version variance across clients nodewatch-api#211
• Infrastructure upgrades for nodewatch.io
  • API rate limiting nodewatch-api#92
  • Review github workflows nodewatch-api#214
• Rename eth2-crawler to nodewatch-api
  • Renaming eth2-crawler to nodewatch-api nodewatch-api#207

The following secondary tasks will be targeted for potential upgrades:

• Checkpointz beacon state distribution for weak subjectivity sync and verification
• Metrics request issue template
• Additional metrics to show centralized vs distributed (e.g. staking pools vs solo operators) validators
• Supported testnet data aggregation
• Execution layer client diversity metrics
• Disk usage metrics of various EL clients
• Network related metrics (e.g. missed block slots in last 24 hours, sync committee period data, etc.)
• Slot estimator (e.g. When will slot X be scheduled for a block proposal?)
• Any additional requests from the community for useful metrics.