Problem
A clear and concise description of what the problem is
Ideas to solve this
A clear and concise description of what you think could solve this problem.
Number of bids for transfer (received, processed, sent, failed)
Number of bids by Router (received, failed, sent, successful)
The entry and exit time of transfer at Sequencer
transfers metrics for given origin and destination domains
Volume
number of transfers
fees earned by each router
transfer per sec
Tasks that will be completed after working on this issue:
1542
1333
1543
Acceptance Criteria
[ ] X happens
[ ] Y happens
Other
Update per P2P
P2 sequencer metrics (how many requests it got, how many bids per request were recieved, is there any request that got no bids for a long time)
RPCs/Subgraphs/Watcher/Gelato/etc. Some of them I know you monitor at your side, I plan to do RPCs monitoring for those endpoints that are specified in router config (once I would finish with all main metrics and alerts, I would move on to RPCs)
we definitely need to be calculated and exported on router container side: number of RPC connections per RPC endpoint. Cause not all RPC endpoints give such stats as above and we cannot get this info from anywhere else. If you can expose this info (just number of requests made, optionally you can specify method - it would simplify debug, as a label e.g. connext_rpc_requests{domain="6450786", url="https://bsc-dataseed.binance.org"} 351
or connext_rpc_requests{domain="6450786", url="https://bsc-dataseed.binance.org", method="eth_call"} 269
) - it would be great. Just increase this count on any request, don't need to store it - once container is restarted just start from 0. The only thing - it's better to cut off URI part not to expose credentials. It would have additional side effect - we would see when router failovers to other RPCs, not using the first one
Problem A clear and concise description of what the problem is
Ideas to solve this A clear and concise description of what you think could solve this problem.
Tasks that will be completed after working on this issue:
1542
1333
1543
Acceptance Criteria
Other Update per P2P