2018-12-13 07:03 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005485Talerdeployment and operationspublic2018-11-26 13:13
ReporterFlorian Dold 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
Product Version 
Target VersionFixed in Version 
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.
Attached Files

-Relationships Relation Graph ] Dependency Graph ]
+Relationships

-Notes

~0013366

Marcello Stanisci (manager)

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

-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
+Issue History