Provided the IP address of the virtual guest Server OS doesn't change (which it shouldn't) APM will continue monitoring regardless which Hyper-V host is actually running the guest.
While they are virutalized the monitoring still works just like you said.. (IP is still good) but when they fail over to one of the Clustered or farmed servers.. (which we dont know which one or when...) then the APM's seem to be non-effective giving wrong results (as far as the users are concerned ) their applications are still running they are happy.. it is Orion's fault we are giving wrong alerts.. :(
Any ideas?
Without knowing what the errors you're receiving are it's hard to guess. I would recommend opening a case with support so we can troubleshoot this issue further. It may be something simple like access control lists, firewall policy or even a possible routing issue; but without taking a closer look at your configuration and environment it's difficult to make a reasonable guess as to what could be causing the problem. This is definitely unusual, and not expected behavior.
Thank you I will open up the case...
Jwerlein--
Please post back with your ticket # and keep us updated with your progress.
Thank you!
DH
I actually hate to respond..
Everythign was working as designed..
the virtual clustered servers under the Virtrual resource were being montored perfectly just like a regular physical server.. the service however was moved by a Server ADMIN and he never bothered to tell anybody thus it showed down on the monitor but up for the user..
technology is only as good as the communication between technical service departments.
