|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005485||Taler||deployment and operations||public||2018-11-26 12:56||2018-11-26 13:13|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||Fixed in Version|
|Summary||0005485: periodic deployment health checks|
|Description||We should have periodic health checks running for all services. If one of them fails, we should receive emails about it. Specifically we should at least|
1. have very simple curl-based checks run periodically by buildbot
2. update/fix and re-enable the selenium-based tests once we're on the new server
We also may think about running taler-exchange-benchmark against the live exchange periodically, with only a small number of transactions to not overwhelm the system.
Eventually, we also might want a taler-merchant-benchmark that (in addition to testing the merchant's performance) periodically runs transactions (including tipping!) against the live merchant.
|Tags||No tags attached.|
Marcello Stanisci (manager)
|Given the last reports from users, we should make sure the health-checks run on the 'demo' deployment too.|
|2018-11-26 12:56||Florian Dold||New Issue|
|2018-11-26 13:13||Marcello Stanisci||Note Added: 0013366|