We use the real-time config notifications which seem to be mostly reliable. There are a few instances that we have noticed an incorrect user being associated to a config change or sometimes no notification at all.
It looks like the issue might be that a change will occur on the switch, followed quickly (within a few seconds) by another change. This could be two ports being shut down at the end of the day one after the next.
I'm guessing that while Solarwinds is downloading the config for the first change, it is somehow missing the log entry for the second, or just not queueing up the download job again since it is already in process of downloading the config to look for changes.
Has anyone else run into this or solved this?
