From e3f2b756ac1cb76f2d560c8c722fedfcdc73acf0 Mon Sep 17 00:00:00 2001 From: Rasmus Dahlberg Date: Tue, 10 May 2022 21:42:35 +0200 Subject: fix naming typos --- ...-05-10--availability-monitoring-requirements.md | 38 ---------------------- 1 file changed, 38 deletions(-) delete mode 100644 archive/2022-05-10--availability-monitoring-requirements.md (limited to 'archive/2022-05-10--availability-monitoring-requirements.md') diff --git a/archive/2022-05-10--availability-monitoring-requirements.md b/archive/2022-05-10--availability-monitoring-requirements.md deleted file mode 100644 index 7522503..0000000 --- a/archive/2022-05-10--availability-monitoring-requirements.md +++ /dev/null @@ -1,38 +0,0 @@ -# Requirements for availability monitoring - - - System requirements - - Runs on a modern linux distro - - System can send email - - System can run sigsum-debug binary - - Root access is not required - - Leveled alerts, aka severity - - Error - - Warning - - Alerts via email - - Check endpoint reachability - - API §3.1 - §3.7 - - Enumerate the different ways to use an endpoint - - http, https - - ipv4, ipv6 - - onion -- Verify response data (the output of Sigsum endpoints) - - E.g., timestamp or number of witness signatures on get-tree-head-to-cosign -- Perform checks from multiple vantage points - -# Concrete milestones - -220515 - - - Sigsum endpoints - - Either IPv4 or IPv6 (whatever the system's curl uses) - - Only HTTPS - - When do they 2XX? - - No alert state - - One alert per failure - - Configurable test frequency (~1h hour) - - Notifications by email only to one single address - - "Be done very quickly but also very imperfectly" - -220530 -220831 -221031 -- cgit v1.2.3