Allow users to monitor servers in different domains and networks
We have multiple servers in different domains. At present there is no trust between the domains and we have a seperate login for each domain. Each domain also has its own IP address range and there may be 2 or more firewalls between the servers. Is an optional agent based approach feasable where all the work happens locally & say XML is punted back & forth over a particular port?
eric twilegar commented
I think each server should just have a locally installed agent. Having to open ports like 135 between the base on the server is weird to say the least.
I'd love to see this move forward. Especially with the capacity to automatically discover new servers as they come online within a specified network.
Be sure to consider time differences. Untrusted domains may not have the same time source and therefore not be in sync. We are having problems with this very issue.
Look at the way Paessler PRTG handles this. Allow a web service to hook to multiple base monitors. PRTG calls them Probes. The web service just connects to the base monitors via ports so Admins could punch holes in firewalls to make this work. Users can login to the web server either with native or Windows accounts (hint hint) and see databases in any variety of situations domains, etc.
This is something we are considering. We have some ideas of how we could achieve this, for example a remote monitor (which can be installed on external network and will collect data and send to base monitor) but nothing is concrete yet.
Please let us know what considerations we would need to make for your own environments.