Stream: tx.fhir.org/notification
Topic: Prod Tx Server: FHIRServer - 8/25/2021 9:34:02 PM
 Terminology Service Monitor Bot (Aug 25 2021 at 21:34):
Zulip notification bot starting up....
 Terminology Service Monitor Bot (Aug 25 2021 at 21:34):
Monitoring Service initializing...
 Terminology Service Monitor Bot (Aug 25 2021 at 21:34):
Http test passed! Status: 200 in 186 ms (0.186 s).
 Terminology Service Monitor Bot (Aug 25 2021 at 22:34):
Http test passed! Status: 200 in 233 ms (0.233 s).
 Terminology Service Monitor Bot (Aug 25 2021 at 23:35):
Http test passed! Status: 200 in 99 ms (0.099 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 00:35):
Http test passed! Status: 200 in 115 ms (0.115 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 01:35):
Http test passed! Status: 200 in 109 ms (0.109 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 02:35):
Http test passed! Status: 200 in 172 ms (0.172 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 03:35):
Http test passed! Status: 200 in 94 ms (0.094 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 04:36):
Http test passed! Status: 200 in 116 ms (0.116 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 05:36):
Http test passed! Status: 200 in 140 ms (0.14 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 06:36):
Http test passed! Status: 200 in 109 ms (0.109 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 07:36):
Http test passed! Status: 200 in 109 ms (0.109 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 08:37):
Http test passed! Status: 200 in 84 ms (0.084 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 09:37):
Http test passed! Status: 200 in 94 ms (0.094 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 10:37):
Http test passed! Status: 200 in 141 ms (0.141 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 11:37):
Http test passed! Status: 200 in 156 ms (0.156 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 12:38):
Http test passed! Status: 200 in 343 ms (0.343 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 13:38):
Http test passed! Status: 200 in 111 ms (0.111 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 14:38):
Http test passed! Status: 200 in 102 ms (0.102 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 15:38):
Http test passed! Status: 200 in 89 ms (0.089 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 15:43):
:warning: Http Test FAILED - no response in 34 ms (0.034 s). Failure 1 of 2 before restart.
 Terminology Service Monitor Bot (Aug 26 2021 at 15:44):
Http test passed! Status: 200 in 227 ms (0.227 s).
 Rob Hausam (Aug 26 2021 at 15:46):
@Gino Canessa Why would we get a failure message for no response in 34 ms? I wouldn't have expected that.
 Gino Canessa (Aug 26 2021 at 16:23):
@Rob Hausam Likely it threw an exception (e.g., connection reset). I'll add it to the other things I'm currently adding.
 Terminology Service Monitor Bot (Aug 26 2021 at 16:33):
:warning: Http Test FAILED - no response in 8 ms (0.008 s). Failure 1 of 2 before restart.
 Terminology Service Monitor Bot (Aug 26 2021 at 16:34):
Http test passed! Status: 200 in 154 ms (0.154 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 17:19):
:warning: Http Test FAILED - no response in 2 ms (0.002 s). Failure 1 of 2 before restart.
 Terminology Service Monitor Bot (Aug 26 2021 at 17:19):
Http test passed! Status: 200 in 78 ms (0.078 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 18:20):
Http test passed! Status: 200 in 110 ms (0.11 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 19:20):
Http test passed! Status: 200 in 200 ms (0.2 s).
 Terminology Service Monitor Bot (Aug 26 2021 at 20:20):
Http test passed! Status: 200 in 108 ms (0.108 s).
Last updated: Apr 12 2022 at 19:14 UTC