It would require some modifications (i.e. we would have to adapt software to stream the polling IP of the source element along with the raw metrics to the destination element, and to get it into the source IP polling of the destination element or at least to have the embedded webpage feature to recognize and use this ‘alternative’ polling IP). And it would only serve a limited number of cases where this capability can effectively be used (because it was really designed to pass on resources from the DMS of one company to the DMS of another company – and if that’s the case, the polling IP address will not even be reachable from within the network of the destination, and therefore this feature will still not work). I assume that the polling IP address in this case is reachable in the destination DMS ecosystem (because else this would be a mute discussion), and then I wonder if this one use case cannot be addressed with a work-around (e.g. if the number of elements that are replicated and need this are limited, you can edit the Visual Overview on the replicated element and add the native web page in there as an embedded webpage). Would that be an option?