From f8097cb5cb68e655bfa4bdcf7cc2976c2accc954 Mon Sep 17 00:00:00 2001 From: Rodrigo Arias Mallo Date: Tue, 13 Feb 2024 11:50:38 +0100 Subject: [PATCH] Add another HTTPS probe for bsc.es As all other HTTPS probes pass through the opsproxy01.bsc.es proxy, we cannot detect a problem in our proxy or in the BSC one. Adding another target like bsc.es that doesn't use the ops proxy allows us to discern where the problem lies. Instead of monitoring https://www.bsc.es/ directly, which will trigger the whole Drupal server and take a whole second, we just fetch robots.txt so the overhead on the server is minimal (and returns in less than 10 ms). Reviewed-by: Aleix Roca Nonell --- m/hut/monitoring.nix | 1 + 1 file changed, 1 insertion(+) diff --git a/m/hut/monitoring.nix b/m/hut/monitoring.nix index 1dea2dd..bbcd48f 100644 --- a/m/hut/monitoring.nix +++ b/m/hut/monitoring.nix @@ -105,6 +105,7 @@ params = { module = [ "http_2xx" ]; }; static_configs = [{ targets = [ + "https://www.bsc.es/robots.txt" "https://pm.bsc.es/" "https://pm.bsc.es/gitlab/" "https://jungle.bsc.es/"