ProfessorProfessorThis is very encouraging -- thank you for the update! There is one remaining architectural issue to resolve -- there is no way to reference ILPs within alerts or other places where tokens can be used. Is this something that will be included in the final version? It would be helpful to show at least some of those values in related alerts.
One more observation on the interface description filtering behavior -- I have developed an API-based method to do the same thing and the one problem we run into is that AD will not update the description of an interface that is has operStatus != up at the time AD runs. This means that if you want to exclude ports from alerting based on description and you change the description to stop LM from alerting, it will not matter if the interface is already down -- this defeats the purpose of avoiding alarms for unimportant interfaces, at least not without manual instance tuning. I have played with removing the operStatus filter from AD, but the results were not good. It really seems like there should be some datapoints that are can be updated regardless of the filter and others that update only when the filter applies. Or more generally, datapoint groups within a datasource, each able to have a distinct filter.
The new DS should also have a default nonunicast threshold, though my challenge there is I care less about one DP with that happening (in most cases) that seeing it across multiple ports and/or multiple devices.
Thanks,
Mark
