Hey, a packet’s a packet no matter how small…
It’s industry standard to use metaphorical language of life and death for computing systems. Heartbeat, keepalive. There is also “healthcheck” but this customer sounds stupid enough to object to that also.
In this case I might try “connectivity poll”. But frankly, I think I would fire a customer with such ridiculous constraints. Frankly this sounds like a severe case of the bike-shed effect in decision-making.
What do they think is going to happen, an IT technician will say “this router hasn’t sent a heartbeat in 4 hours” and a physician says “okay, I don’t know this guy, and he’s not dressed like a healthcare provider, and that seems like a dangerously long time to be in cardiac arrest, but I’m just going to react to this vague decontextualized information from a complete stranger and zap Mr. Router with the shock paddles.”
Even runt packets.
Most of the people around the tags are going to be nurses. Many don’t have the technical background to understand that tech often adopts terms from healthcare. Even if they did, they’re in a high-pressure medical environment and phrases like “no heartbeat” are trigger words to action for them. Not something you can afford to dither about, y’know?
So perhaps saying “it has stopping going ping” isn’t a good idea either 
No ping?
No ping, Vasily.
If one is in an operating room then maybe I could see this. But the IT tech isn’t going to be in the operating room. And they’re suggesting that a nurse would react to a command from a random stranger who isn’t wearing scrubs or a lab coat?
I mean, please walk me through the process that might lead to dithering here. Because I have worked in a medical treatment facility before, and I’ve never heard anyone suggest that a medical professional might get confused by a random person saying a “special” word.
Mostly I’m just speculating on how it could be an issue at all. I’ve never worked in a medical facility of any sort.
All I know is that the hospitals really, really, REALLY don’t like using terminology from the medical field to describe something that isn’t. And since they’re our major source of revenue, we find another way of saying something.
Wow, you guys are mean.
We “pet” our watchdog. If you don’t pet the dog, the dog bites you (reboots).
Kicking a dog is just cruel.
FWIW, our watchdog task is named “woof”.
Make up some word that doesn’t have a ready homophone, spell it in all caps to suggest an acronym, and never explain what it stands for.
“FERDD Mark.” Thereyago.
Perfect. Once you tell us how to pronounce it in all caps.
Easy. Raise it an octave, and try to pronounce it like the Swedish Chef is saying it.
There is a bit of a tendency for academics and professionals to get uppity about (what they consider to be) their terminology being appropriated for other purposes. I recall an argument, from a biologist, about how the term ‘ecosystem’ shouldn’t ever be used in computing - even though it’s a pretty apt analogy.
As I understand it, in hospitals they are very familiar with machines that go “ping”
Cooee is usually a distress call.
Amongst keen Australian hikers “Hey Bob!” is the better term for merely communicating presence without indicating distress.
To be fair, we don’t kick the dog, we kick the dog’s timer, which wakes the dog up. So by kicking the timer, we let the puppy sleep a little longer
Would hiccup still be too medical. ? That’s what came to my mind for a recurring beep.
Or Clippit (remember the annoying but kinda sweet paperclip)
Or Bueller a word now in urban dictionary meaning waiting for a response.
There’s always ACK, but that implies the device is waiting for a response, which it isn’t doing. The signal is strictly one-way.
No, that won’t do at all. ACK sounds like a person gagging or choking, and this medical staff sounds as if they’d find that very confusing.
How about its “presence” packet ? The info is “I am here” right ? So these packets will keep track of the presence of the device…