View Issue Details

IDProjectCategoryView StatusLast Update
0005485Talerdeployment and operationspublic2019-06-24 23:38
ReporterFlorian Dold Assigned ToMarcello Stanisci  
PrioritynormalSeverityfeatureReproducibilityhave not tried
Status closedResolutionno change required 
Summary0005485: periodic deployment health checks
DescriptionWe 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.
TagsNo tags attached.

Activities

Marcello Stanisci

2018-11-26 13:13

reporter   ~0013366

Given the last reports from users, we should make sure the health-checks run on the 'demo' deployment too.

Marcello Stanisci

2019-01-29 13:34

reporter   ~0013511

The sanity checks should also make sure that Postgresql and nginx (and all the corollary services) are running, and TLS certificates are valid.

Marcello Stanisci

2019-06-24 18:40

reporter   ~0014576

@13366, exists: https://buildbot.taler.net/#/builders/4

Marcello Stanisci

2019-06-24 23:29

reporter   ~0014585

Last edited: 2019-06-24 23:38

Closing because:

1) Demo services *are* checked by the Buildbot (via Curl, see [1]).
2) Benchmarks-driven tests will be replaced by the headless wallet.
3) No reason to keep this open just for the far-fetched Selenium-based tests. If need be, we'll open a dedicate issue for that.
4) What says note 13511 does not apply here.

[1] https://git.taler.net/deployment.git/tree/buildbot/checks.sh?id=72adb0fdd752978cf89301a102880cfac3fa40cc

Issue History

Date Modified Username Field Change
2018-11-26 12:56 Florian Dold New Issue
2018-11-26 13:13 Marcello Stanisci Note Added: 0013366
2019-01-29 13:34 Marcello Stanisci Note Added: 0013511
2019-01-31 19:16 Christian Grothoff Severity minor => feature
2019-06-24 18:40 Marcello Stanisci Note Added: 0014576
2019-06-24 23:29 Marcello Stanisci Note Added: 0014585
2019-06-24 23:29 Marcello Stanisci Note Edited: 0014585
2019-06-24 23:30 Marcello Stanisci Assigned To => Marcello Stanisci
2019-06-24 23:30 Marcello Stanisci Status new => closed
2019-06-24 23:30 Marcello Stanisci Resolution open => no change required
2019-06-24 23:38 Marcello Stanisci Note Edited: 0014585