Foglight for Databases Architecture

Hi, folks. Here's a quick guide on the architecture of Foglight for Database. The first component is the Foglight Management Server this holds the UI layer and requires a repository database to be installed. On installation, you can choose the embedded [? postgress ?] option or choose External Oracle SQL server or [? postgress ?] databases. The second component is a Foglight Agent Manager. While we don't install agents on the monitor instances, we do require remote agents to gather information from them, and those remote agents reside under Foglight Agent Manager. If the SQL performance investigator module is in use, then SQL PI agents are also required. The third component is the SQL Performance Investigator Repository, and this resides on a SQL server database. So data is collected from the monitored instances via the remote agent's under Foglight Agent Manager Server. That data is then fed to the repository database of the Foglight Management Server and [? access ?] via the UI layer of the Foglight Management Server. If SQL Performance Investigator is in use, then the SQL PI agents will gather information and populate it into the SQL Performance Investigator Repository database. That data can also be accessed and visualized via the UI layer of the Foglight Management Server. Below are a list of ports required by Foglight to access data on your monitored environment, as well as communication between the Foglight components. For more information on the Foglight components and these ports, please check out the Foglight deployment and installation guides. For more information on Foglight for Databases, please go to quest.com/foglightfordatabases, and check out the Video section for videos on the prerequisites and installation of Foglight for Databases. Thanks for tuning in.