track KPIs

[thedavidmeister]

• how many blocks elapsed between opportunity and execution?
• how often does our execution succeed?

todo:

• [x] - Required changes in code: https://github.com/rainlanguage/arb-bot/pull/89
• [x] - Required tasks in hyperdx, which include, setting up correct dashboards and alerts,

update: dashboard for second kpi question is set, but the first one, it cant be achieved at least in a way that it doesnt significantly increase the hyperdx data usage, since it would a need sep trace per order, or decoupled from the orders, so it would end up needing some form of refactor in spans setup in codebase.

so this will be put into backlog for now, and will be pursued later. this issue will be updated this if I manage to find any workaround/solution for this.

Edit:

how many blocks elapsed between opportunity and execution? means to fiind the very first block the opportunity was available vs when bot found it and executed it.

• [ ] - need to be planned, probably a rust code + cli that can generate the desired data from the trades fetched from sg for a Y blockspan. I think it can go like, from the exec block go back one by one to find the very first block were sushi gave the same route and amountOut for the amountIn. once that is found then go forward block by block to find the very first one that could have been an opp. that would indicate the very first block that opp was available, then can be compared agains the exec blck that we already have. but this is very rpc intensive considering how many block it needs to go back. we can kinda do it on rust with anvil on sep thread, and running sushi lib on a sep process through rust executing bash on the anvil exposed rpc and getting its result through stdout back to the rust code

[rouzwelt]

there are some new filtering options on hyperdx, that can most probably can help us implement this easily, im gonna update this more, once I have more details

[rouzwelt]

right now the hyperdx charts have a feature that can filter logs with only specific criteria, so using that + logging the block difference we can make that KPI chart in hyperdx,

todo:

• [x] - changes to include blockk diff in logs: #154
• [x] - make the chart in hyperdx once bots are updated with the above change, set under block elapsed

[rouzwelt]

how many blocks elapsed between opportunity and execution?

means to fiind the very first block the opportunity was available vs when bot found it and executed it