Syslog "Cleared" = MEANINGLESS
Syslog Issues:
#1. The person who asked to have SYSLOG present a "cleared" message.....CLEARLY does not understand that a SYSLOG is NOT A tracked condition like an OID value is....it is a SI...
Forum Discussion
Treating all events equally is a very bad policy.
A dropped ping, is very different from a syslog message about parity failure in a RAID or DBReplication failure alert.
Note in MOST (if not all) situations where we use Syslog....the effects reported would NEVER clear....at all without a tech going in and doing work.
the software sending a "cleared" email is the opposite of crying-wolf.....it's crying "all clear" when the wolf is right there chewing on your leg.
I'm very frustrated that I have to explain this twice....the customer that suggested it doesn't understand what syslog "is".
The engineers that honored the flawed request did that customer...and the rest of us...a grave disservice.
You've forced me to train my people to ignore certain messages.
The work around we have now is to filter all your Cleared messages:
Still, not sure why you didn't lead with that advisement.
You can't convince me to change my opinion on this topic : it was a poor design decision you've made here.
In time, I am very certain you will see why I am right.
