Database Licensing
Foglight database monitoring is licensed per monitored target. Each database target that Foglight monitors consumes one unit of your database license entitlement.
The definition of a target differs slightly from one database domain to another. This section explains how targets (units) are counted for each supported database domain and describes special cases, such as SQL Server high-availability configurations.
This section covers the following key areas:
How Targets Are Counted
A database license is sold per monitored target. What counts as a single target depends on the database domain being monitored, because the definition of a target differs slightly from one technology to another. In general, each monitored database instance is counted as one target. Duplications (for example, the same instance discovered through multiple paths) are removed so that each target is counted only once.
For the definitive number of units consumed by a specific configuration, or for questions about purchasing additional entitlements, contact your Quest account representative or Quest Sales.
Units Calculation by Domain
The following table describes how units are counted for each supported database domain.
| Domain | Counted By | Notes |
|---|---|---|
| SQL Server | Per instance | Relevant to all monitored SQL Server flavors (MSSQL, RDS, Managed Instance, and so on). In a high-availability configuration (replication, availability group, and so on), each monitored node is counted as a separate instance. |
| SQL Server BI | Not calculated | Not counted. |
| Azure SQL Database | Per Azure SQL Database | Elastic pools are not counted. |
| Oracle | Per Oracle instance | In a RAC configuration, the included instances are counted. ASM, CRS, Exadata, and Data Guard are not counted. |
| DB2 | Per instance | Counted per instance, not per database. |
| SAP ASE | Per MDA and/or RSA instance | — |
| MySQL | Per instance | Relevant to all monitored MySQL flavors. |
| PostgreSQL | Per instance | Relevant to all monitored PostgreSQL flavors (PostgreSQL, Aurora, and so on). |
| Snowflake | Per warehouse | — |
| MongoDB / Atlas | Per replica set | Standalone deployments are counted as a single instance. |
| DocumentDB | Per cluster | Includes instance clusters and elastic clusters. |
| Redis | Per database shard | — |
| Redshift | Per cluster | — |
| SAP HANA | Per instance | — |
| Cassandra | Per database node | — |
| AWS Host | Per host | Includes standard RDS hosts and RDS hosts for SQL Server. |
Special Cases
Certain SQL Server high-availability configurations affect how monitored targets are counted.
SQL Server Availability Groups and Replication
In an Always On Availability Group or other high-availability configuration, each SQL Server node that is monitored is counted as a separate instance. Every monitored replica is a distinct instance, so each contributes to the total number of targets consumed.
Oracle RAC
For an Oracle Real Application Clusters (RAC) configuration, each included Oracle instance is counted. Related components such as ASM, CRS, Exadata, and Data Guard are not counted.
Configurations That Are Not Counted
The following are not counted toward your database license units:
- SQL Server BI
- Azure SQL Database elastic pools
- Oracle ASM, CRS, Exadata, and Data Guard
