Path: ...!news.mixmin.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Don Y <blockedofcourse@foo.invalid>
Newsgroups: sci.electronics.design
Subject: Predictive failures
Date: Mon, 15 Apr 2024 10:13:02 -0700
Organization: A noiseless patient Spider
Lines: 11
Message-ID: <uvjn74$d54b$1@dont-email.me>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 15 Apr 2024 19:13:08 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="da2971c44a50358724a18132e5903f1e";
	logging-data="431243"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18/L+JXYzlLq4IdEl1bzP/L"
User-Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:102.0) Gecko/20100101
 Thunderbird/102.2.2
Cancel-Lock: sha1:X99tkglJ6uea0eykZUF4F6Kj1SU=
Content-Language: en-US
Bytes: 1463

Is there a general rule of thumb for signalling the likelihood of
an "imminent" (for some value of "imminent") hardware failure?

I suspect most would involve *relative* changes that would be
suggestive of changing conditions in the components (and not
directly related to environmental influences).

So, perhaps, a good strategy is to just "watch" everything and
notice the sorts of changes you "typically" encounter in the hope
that something of greater magnitude would be a harbinger...