One of the most frequent questions I get from customers, especially those monitoring large and complex SQL Server environments, is how they can monitor SQL Servers that may be spread across different, many times untrusted Windows domains. Foglight provides a distributed architecture that enables customers to monitor these types of environments very easily, all from a single Foglight installation and user interface.
Before I get into the details of exactly how to do this, let’s briefly go over the Foglight Architecture (click on any image for a larger view):
The part worth mentioning here, is the Foglight Agent Manager (labeled 1), which connects to your SQL Server Instance(s) being monitored (labeled 2). This agent manager needs to be able to connect to the SQL Servers over whatever port SQL Server is listening on (default 1433, or whatever port you have configured), and also to the monitored operating system over the ports used for WinRM or WMI. This Foglight Agent Manager also needs to be able to leverage a Windows account to login to the SQL Server Instance (SQL Authentication can be used if required) and the Windows OS that is hosting your SQL Server instance. In an environment with multiple domains, especially when trusts are not configured between each domain, a Foglight Agent Manager should be installed onto a Windows machine that is a part of the domain that includes the SQL Server instance(s) you wish to monitor. This will allow the Foglight Agent Manager to authenticate, via Windows Authentication, to the SQL Servers being monitored. If an environment is to have several of these, non-trusted, domains, expect to need at least one Foglight Agent Manager Installation, per Windows domain. All of these distributed Foglight Agent Managers can report back into a common Foglight Management server, assuming that network connectivity and proper hardware/resource sizing can be ensured.
This process starts after Foglight for SQL Server has been initially installed, meaning that you already have a Foglight Management Server, and Foglight Repository configured into your environment.
That should be it! If you run into any issues with the above process, feel free to leave a comment, and/or contact our technical support team for assistance. I hope you have found this information valuable.