Second Ethereum RPC metrics are not tracked

Do you want to request a feature or report a bug?
Bug

What is the current behavior?
When adding a second Ethereum RPC, we lose visibility in Grafana of the time for eth_getLogs calls - deployment_eth_rpc_request_duration. This was done recently for the matic network on the Hosted Service.

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Add two Ethereum RPCs, the second of which should be a non-archive node (so it is used for eth_getLogs calls). The deployment_eth_rpc_request_duration is no longer tracked. eth_call duration will be tracked (as those hit the archive URL)

Hypothesis: possibly graph node tries to register the same metric twice, one for each url, which is an error

What is the expected behavior?
Metrics should be tracked for all nodes - ideally we should also be able to distinguish metrics by node?

この issue ではファイルやテストが指定されていません。まず2つの Ethereum RPC を使ってセットアップを再現し、その後、eth_getLogs と eth_call に対する deployment_eth_rpc_request_duration の登録と収集を追跡してください。完了条件は、設定されたすべてのノードでリクエスト所要時間のメトリクスが引き続き利用でき、理想的にはノードごとに区別できることです。