NavigaTUM
NavigaTUM copied to clipboard
TUM-Dev
bad monitoring implementation
Monitoring alert:
9/5/2025 10:58:20 PM Fehler, HTTP/1.1 302 Found - too many redirects 9/5/2025 10:57:20 PM Warnung, HTTP/1.1 302 Found - too many redirects 9/1/2025 9:37:20 PM OK, 135 ms 9/1/2025 9:36:21 PM Warnung, HTTP/1.1 502 Bad Gateway 9/1/2025 1:37:20 PM OK, 83 ms 9/1/2025 1:36:22 PM Warnung, HTTP/1.1 502 Bad Gateway 8/31/2025 5:17:20 PM OK, 142 ms 8/31/2025 5:16:22 PM Warnung, HTTP/1.1 502 Bad Gateway 8/31/2025 2:27:20 PM OK, 166 ms 8/31/2025 2:26:22 PM Warnung, HTTP/1.1 502 Bad Gateway
Very unfortunate, especially since I had no idea that this is happening until now. I really need to fix the broken monitoring and not having a proper end to end test.
I reverted https://github.com/TUM-Dev/NavigaTUM/commit/dfa7d840c8fddf2106403b8f130a9ceb0935064c , which schould fix this in a few minutes.
The ITM monitoring detected it yesterday at 11 pm — sending you a CC might be a temporary fix.
If this is possible, that would be nice. My "fast" (not redirected via the LRZ) email is fr.elsinga (at) gmail (dot) com