Hey everyone!
We make heavy use of Netscaler VIPs in our environment. Usually these are used for clusters, but we still use them for single nodes for three reasons:
1. It somewhat hides the name of the originating server that the traffic is being directed to.
2. It allows us to change only the VIP if a server is upgraded/moved.
3. It allows us to perform SSL termination, which is handy for older software that doesn't support HTTPS (more common at a University than I'd like!)
I have seen the notes in the feature request for AppInsight clusters about pointing AppInsight for IIS at VIP -- which means monitoring it as WMI as agent based can't do that. In this case, I'm asking for a single node.
In an ideal world, I'd like to have two component monitors in AppInsight - one for the internal HTTP/HTTPS bindings, and one for the external bindings (going through the DNS lookup). I am pretty sure I could do this with a standard application template, but I'm not sure I can add new component monitors to AppInsight.
For those who have encountered this kind of issue, how have you handled it? Do you point IIS's components at the VIP instead of the root server? Do you ignore the VIP? Do you set up a second application template that just monitors the VIP? -- that idea is kind of my fallback, but I'm worried about SAM licenses because I'm sure it will treat the VIP as a separate node and application license versus the heavy duty lifting of AppInsight.
