Looks like Dynatrace do not know to connect the Virtual name of a Microsoft cluster with its real members and therefore we get different entities while the virtual name is connected to one member compared to the time it is connected to the second member (like two databases with the same name...)
Is there a way to tell it that these two hosts (members) are actually one "Logical" host ?
Solved! Go to Solution.
Dynatrace does not recognize active-passive clusters in general. If you do have two database entities that in fact is the same database, then you most likely have different connection definitions in the applications.
On the process group level (if you see two process groups that are in fact the same process in terms of functionality), this is typically solved by tuning or configuring the process group detection rules, but I'm not sure if this is your case.
Can you be more specific in describing your case?