People are open to giving anonymous and maybe pseudonymous performance data, to get a better understanding of their node's health, and how best to optimise it.
Right now they fill out forms by hand, translating what their CLI test output says. We then manually translate that into charts and reports. We will need to simplify this to scale it.
🛠️ Proposed solution
We could add an optional --publish flag (and --publish-address), like the rest of our commands, that pushes to our API.
[ ] Approved design doc: link
[ ] Core team consensus on the proposed solution
Describe the solution to be implemented
🧪 Tests
[ ] Tested by new automated unit/integration/smoke tests
[ ] Manually tested on core team/canary/test clusters
[ ] Manually tested on local compose simnet
👐 Additional acceptance criteria
[ ] All of the related impact on Launchpad/API team
❌ Out of Scope
In future we could also return a launchpad URI like https://launchpad.obol.org/operator/<address>/<enr>/ that shows a more fancy test report.
🎯 Problem to be solved
People are open to giving anonymous and maybe pseudonymous performance data, to get a better understanding of their node's health, and how best to optimise it.
Right now they fill out forms by hand, translating what their CLI test output says. We then manually translate that into charts and reports. We will need to simplify this to scale it.
🛠️ Proposed solution
We could add an optional
--publishflag (and--publish-address), like the rest of our commands, that pushes to our API.Describe the solution to be implemented
🧪 Tests
👐 Additional acceptance criteria
❌ Out of Scope
In future we could also return a launchpad URI like
https://launchpad.obol.org/operator/<address>/<enr>/that shows a more fancy test report.