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
I am not sure there is a design problem to be solved here. In my opinion, the decision was brilliant to have consistent design, alert handling and escalation rules at the expense of having to edit an escalation rule to stop syslog clears (or other clears you may not want).
It allows all users of all skills to both navigate and configure the LogicMonitor web portal easily. You don't have to be an SME, but it's as usable for someone who is.
Let's also not forget that syslog alerting is not a core strength for LogicMonitor. If a particular organization's troubleshooting methodology is primarily via syslog events, then I would propose that a dedicated syslog application is merited. LogicMonitor's strength is in performance metrics and discovery of new items that now should be monitored.
My team's primary troubleshooting method is not syslog, but for those events that we don't want clears on, we simply disable them.
