[Feature] Make public.ethereum_networks table a foreign table

[datanexus-vincent]

Description

We are working on modifying our current grafana dashboards to work with our new sharded deployment.

Our sharded deployment is currently configured with per-chain shards, as well as additional VIP shards for certain chains. The call cache for each chain is in the chain-specific VIP shard if it has one, or just the default chain-specific database if it doesn't.

Currently, to deal with the issue of tables from the subgraphs schema being sharded, we found foreign tables in a per-shard schema that we can use. Those were great for getting data from all of the tables in the subgraphs schema, but for our main "indexing status" dashboard table also includes blocks behind, which means we need to get data from public.ethereum_networks, which in our case is also sharded.

Can we add public.ethereum_networks to the list of foreign tables in each shard's foreign table schema by default?

Are you aware of any blockers that must be resolved before implementing this feature? If so, which? Link to any relevant GitHub issues.

No response

Some information to help us out

• Tick this box if you plan on implementing this feature yourself.
• I have searched the issue tracker to make sure this issue is not a duplicate.

[github-actions]

Looks like this issue has been open for 6 months with no activity. Is it still relevant? If not, please remember to close it.

[rotarur]

+1 for this feature. I'd also like to have this foreign table for grafana metrics with better overview of chains / SG's

[kw1knode]

+1