stronk-dev / orchestratortracker

Pretend Broadcaster looking for quick Orchestrators in your area

This program consists of three components:

• A master which consolidates orchestrator statistics from various clients
  • Publishes GetOrchestrator responses and discovery time
  • Publishes orchestrator price info
  • Observes Livepeer Inc performance leaderboards results to Prometheus
  • TODO integration with email / telegram
  • TODO api to subscribe for notifications and cancel it
• A client which pushes stats to master
  • Gets the list of active Orchestrators from the Livepeer subgraph
  • Test each of them and upload results
• TODO A frontend where users can (un)subscribe to notifications

orchestratortracker's Issues

Do not restore data for sources no longer active

If we eg move from Boston to Michigan, we now have an entry for Boston which no longer gets update. When we reboot and init the prometheus state we should ignore tracks which no longer get updated like that

Explain why `process.env.NODE_TLS_REJECT_UNAUTHORIZED = "0";` is neccessary

https://github.com/stronk-dev/OrchestratorTracker/blob/1533893e35e85e9b18847f828679c4a6cb05c5d1/client/src/routes/orchTester.js#LL10C1-L11C1

Make ENS endpoint a config var

Investigate weird response times

edc0c3d might fix some of the weird jumps we saw with ping times now that it actually uses a fresh client for each request.

Monitor and try to find the cause of some O's having very inconsistent results

rewrite timestamps for orch data on recovery?

should have the same deltas but for the new current time?

Prober can get stuck on `Getting orchestrator data from the subgraph...`

Fix Uptime Ratio

Currently it is 100% for everyone, probably because all O's are able to respond to a ping call from somewhere so there should be a cutoff and an explicit NO if they fail te respond withing a certain timeframe

Remove references to Frontend, Notifications and test stream results

We will be using https://github.com/stronk-dev/OrchestratorNotifier to subscribe to notifications about O's

Modify ping time

If no response was be made, we would like to see a gap in the response times. Currently it just keeps the last known value in there