Origin of the name "Network Monitor"?

[David Teh]

Ok, this is more for the fun of it.

Anyone knows why the “Network Monitor” is called the “Network Monitor”?

I have always found it odd, as it is definitely not monitoring the network. 🙂

Topic

[Robert Kersemakers]

I agree: ‘Thread Monitor’ sounds way cooler… 8)

Zuyderland Medisch Centrum; Heerlen/Sittard; The Netherlands

[Chris Williams]

“Network” has a certain cachet. “Thread Monitor” sounds like the teacher’s pet in a sewing class.

[Anonymous]

Well, I guess it is because it monitor’s the internal Cloverleaf “network” of threads and interfaces.  But if you think about it, in a way it does monitor your hospitals network.  If a network is down or a connection to an ancillary system is severed for any reason, then your Cloverleaf thread will go to in “opening” status and will return “up” again once that connection has been re-established.   There have been times when our alerts on the Cloverleaf engine have been the first to identify a problem with either a network problem or a connectivity in general.

So I guess the name “Network Monitor” is a good name!

Tom Rioux

[David Teh]

Hi Thomas,

I too can attest to the fact that usually Cloverleaf operators are the first to take action although the real problem lies elsewhere. 🙂

But, in a true sense, the other systems jolly well have their own monitoring mechanisms. Should there be a hard break, either due to network or the other system’s failure, Cloverleaf may not receive any TCP/IP segment to disconnect. The thread remains ‘UP’ 🙂

Thomas G Rioux wrote:

Well, I guess it is because it monitor’s the internal Cloverleaf “network” of threads and interfaces.

[Author]

Replies