it's difficult for support to say "it's broken" if the behavior has been consistent since inception.
Despite the many threads that report it as a bug - since 2009 - and Solarwinds never acknowledging what the expected or as-implemented behavior is, until today?
Is there a disconnect here or is it just me being cranky?
I appreciate your response aLTeReGo - it's much better in tone and technically than the ones I got from support that basically say, "it's not an issue". The "not an issue" responses trouble me big time - for above reasons, and one more:
Why does an external node accept a hostname at all if it can't support it? The fact that it does but only sticks with the first discovered IP address - with no ability to update it even manually - is against all common sense, especially that the behavior is completely undocumented. Support trying to feed me the "it clearly says, no data collection" story several times not so subtly suggests I am an idiot. Maybe I am, yet at the moment, it's quite hard for me to digest getting this kind of support for a product I am supposed to rely on for our mission critical needs. Not going to fly long term.
I'd be much happier with: "hey, we just discovered this behavior - thanks for helping us zero in on it - we didn't know about it ourselves - yeah, it doesn't look quite right - let us mull it over to see if we can implement a fix some time in the future." It doesn't offer much hope for a quick fix but at least it's an acknowledgement that yes, it is an issue, and yes, Solarwinds ought to look at it.
The "it's not doing it because it's not supposed to" responses from support - even after escalation - look just inappropriate to me. Am I the only one who thinks that way?
Clik here to view.
