Chat now with support
Chat with Support

Foglight for Databases Shared 7.1.0 - Deployment Guide

Deployment pre-requisites

Welcome to the Foglight for Databases Deployment Guide. This guide provides the pre-requisites for optimal deployment, to ensure the best user experience possible.

This section describes important deployment information required to monitor the leading RDBMS: Oracle®, SQL Server®, SAP ASE®, DB2 for LUW, and Azure® SQL.

Architecture

There are three main components:

•
Foglight Management Server and Foglight Repository — Responsible for managing, alerting, and viewing the collected data. Both components can be set to run on the same machine or reside on separate machines.
•
Foglight Agent Manager (FglAM) — Hosts the monitoring database agents (also known as DB Agent) and SQL PI domain manager agent.
•
SQL PI Database — Refers to a SQL Server database under a SQL Server instance that holds PI collected data.
A single repository can hold up to 300 agents for a specific domain (for example, SQL Server, Oracle, SSAS). Multiple repositories can reside on a single SQL Server instance.
The total number of monitored instances on a single SQL Server instance is limited to 600.
Figure 1. Foglight for Databases Components

In recent cartridge releases, Foglight facilitates the ad-hoc query execution over HTTPS which eliminates the need to open a dedicated port. The relevant cartridge releases that support this are listed below:

Cartridge
Release
Dedicated port - Not needed

Foglight for SQL Server

7.1.0.10

3265

Foglight for Azure SQL Database

7.2.1.10

3260

Foglight for Oracle

7.2.2.10

 

3723

Foglight for DB2

 

7.2.2.10

3725

* 
NOTE: The the use of a dedicated port is still required if there is a need to use ad-hoc query on a Federator server.
* 
NOTE:  
•
A single FglAM can handle up to 800 DB agents.
•
A single FglAM can handle one PI domain manager agent per domain. Currently, it is up to 4 (SQL Server, Azure SQL Database, Oracle, SSAS).
•
Each PI domain manager agent can monitor up to 300 instances for a single domain (For example, SQL Server, Oracle, SSAS).
•
Each PI domain manager can save data into a single repository.

Examples

Refer to the following examples for detailed information:

Example 1

To monitor 100 SQL server instances, 120 Oracle instances, and 15 SSAS instances, all including PI:

•
FglAM 1:
•
100 SQL server DB agents monitor the 100 SQL server instances.
•
120 Oracle DB agents monitor the 120 Oracle instances.
•
15 SSAS DB agents monitor the 15 SSAS instances.
•
3 PI domain manager agents – each managing a single domain – SQL Server, Oracle, SSAS.
•
SQL Server Instance 1:
•
PI repository 1 – database for saving the PI data of 100 SQL server instances.
•
PI repository 2 – database for saving the PI data of 120 Oracle instances.
•
PI repository 3 – database for saving the PI data of 15 SSAS instance.

Example 2

To monitor 600 SQL server instances and 300 Oracle instances, all including PI:

•
FglAM 1:
•
300 SQL server DB agents monitor 300 SQL server instances.
•
300 Oracle server DB agents monitor 300 Oracle instances.
•
2 PI domain agent managers – one manages the SQL server instances while the other manages the Oracle instances.
•
FglAM 2:
•
300 SQL Server db agents monitor the 300 SQL Server instances.
•
1 PI domain agent manager collects PI data from the 300 SQL Server instances.
•
SQL Server instance 1:
•
PI repository 1 – database for saving PI data from 300 monitored SQL Server instances.
•
PI repository 2 - database for saving PI data from 300 monitored Oracle instances.
•
SQL Server instance 2:
•
PI repository 3 – database for saving PI data from 300 monitored SQL Server instances.

Deployment in Centralized vs Distributed

In monitoring environments that exceed a total of 20 agents, a distributed installation is necessary:

•
The FMS should be installed on a dedicated server.
•
External FglAMs should be used for DB Agents and with each installed on a dedicated server.
•
Each instance of the SQL PI repository should be installed on a separate server.

In All-in-One installations on virtual machines (VMs), the machine is highly recommended to reserve CPU and Memory for better performance.

Once the total number of agents exceeds 20, All-in-One installations are no longer supported.

* 
NOTE: The FMS should use the same timezone as the monitored instance. This is in order to display the collected data on UI dashboards in the same timeframe as when it was collected from the monitored instance.

Hardware requirements

Identify your hardware requirements, which are determined by whether SQL PI is configured and by the number of monitoring agents.

•
SQL PI configured
•
SQL PI not configured
 
* 
NOTE: The Numbers of agents refers to DB agents. The Infrastructure Cartridge (IC) agent’s resources are included within the DB agent resource calculations. Sizing requirements are exclusively for Foglight components and these resources should not compete with any other resources required for the operation system (OS) or applications installed on the same system.
Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating