Cisco Switch ErrDisabled Status on Port in LM Exchange Posted October 4 1 minute ago, Stuart Weenig said: Agreed, a DataSource would fix the multiple alerts that results from an EventSource running. Although i think the larger question of alert correlation (multiple alerts being statically or dynamically grouped into incidents) is something you should be requesting from your CSM. Even something like occurrence counts on alerts would be good. The same problem happens with SNMP traps; traps can come in every minute and be about the same thing still in an unwanted state. Each one should just increment a counter on the alert. Counter thresholds should be something we can add to alert rules. Even regular datapoints could benefit from this, counting the number of poll cycles/minutes that a particular metric has been over threshold. Sounds like submitting to CSM should work, but here is usually what happens. "You should submit a feature request or feedback item." To me, those have a pretty small chance of success, so I have stopped trying except in a few cases. I once was able to peer into the feedback tickets via export and discuss with our CSM, but those are normally complete blackholes. Feature requests rarely result in any constructive activity and they lack basic support for escalation, voting, etc. Really we need one ticket system to be able to track all of these things with suitable categories (which I have also suggested that multiple times). And yes, every event source should have the ability to correlate new events with open events. I have been pushing for this for a long time, but I suspect now the answer is "get LMLogs" and this will never get any traction. Being able to get data averages datapoints over time has also been a long-time open request. This is important to look for issues where the status might oscillate, but overall levels are high (e.g., resource usage like CPU, bandwidth, etc.).