For sake of improving user experience of bridge we would need enable automated alerts for bridge frontend which require setup of appropriate monitoring.
There two main approaches which make sense for me at the moment.
Health checks. e2e selenium
Real user monitoring. GitHub - akamai/boomerang: End user oriented web performance testing and beaconing
One would be setup of scheduled health checks which would trigger scripted selenium usage of the web application. This would have shortcomings of only detecting already know problems more in line with existing infrastructure of testing. Also the time frame of detection would very large due to the time it takes for this to execute. Also additional flakiness introduced by the complexity of the setup. Similar approach was taken by the wallet team in e2e tests.
Real user monitoring would enable to capture general usage/stats of web application.
Capture response codes from all API calls, javascript errors, performance metrics.
All this data would enable us to have simple yet robust detection of incidents.
This kind of service is offered through Google and many more companies.
I would prefer to keep it open source in a spirit of NEAR.
Also with tooling it’s not our intention to spy people, but to collect minimal amount of data
needed for monitoring.
Some people which could help out with this or simply give insight.
@chadoh @alex.shevchenko