FHIR Chat · test.fhir.org: FHIRServer - 9/27/2021 7:08:19 AM · test.fhir.org/internal

Stream: test.fhir.org/internal

Topic: test.fhir.org: FHIRServer - 9/27/2021 7:08:19 AM


view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:08):

Zulip notification bot starting up.
Caller: terminology-service-liveness-monitor, version: 0.0.15.0. Target: .NETCoreApp,Version=v5.0
OS: Microsoft Windows 10.0.14393:X64

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:08):

Monitoring Service initializing...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:08):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:09):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:09):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:10):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:10):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:11):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:11):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:12):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:12):

Waiting on first HTTP success from service: FHIRServer (may take a few minutes)...

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 07:13):

HTTP Test Results:

Time HTTP ms Fail Mem (MB) Handles Threads #Conn
7:13:28 AM 200:OK 482 0/0 0.000 0 0 102

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 08:13):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 09:13):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 10:14):

HTTP Test Results:

view this post on Zulip Grahame Grieve (Sep 27 2021 at 10:27):

@Gino Canessa what's going on here with all the 0s?

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 11:14):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 12:14):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 13:14):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 14:15):

HTTP Test Results:

view this post on Zulip Gino Canessa (Sep 27 2021 at 14:34):

@Grahame Grieve First guess is that it doesn't have the proper executable name in the config. The information missing is all stuff it gets from the Process. The setting in question is in appsettings.json, ProcessName, which needs to be set to the process being monitored.

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 15:15):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 16:15):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 17:15):

HTTP Test Results:

view this post on Zulip Terminology Service Monitor Bot (Sep 27 2021 at 18:16):

HTTP Test Results:

view this post on Zulip Grahame Grieve (Sep 27 2021 at 18:51):

@Gino Canessa thanks. you were right


Last updated: Apr 12 2022 at 19:14 UTC