Foglight Evolve 9.3 - Performance Tuning Field Guide

Custom Tablespaces

You can create custom tablespaces by modifying the storage-config.xml file, that is located in the config directory of the Management Server installation.

Group A (configuration) tables can only be created using the SQL scripts available in the <foglight_home>/scripts/sql directory. This can be done using the database tool, foglight-database-tool.jar. For complete information, about this tool, see the Foglight Installation and Setup Guide set.

Group B (observation) tables can also be added. Adding them before the server starts for the first time causes them to be created in the custom tablespace. If the default tablespace already contains group B tables at the time storage-config.xml is updated, they remain in that tablespace until the server rolls up or purges the data in those tables.

Adding group B tables after the Management Server starts causes the server to move them over to the new tablespace as it rolls up long-term data. This means that for some tables, for example, it can take as long as three months before they are created in the database. The actual period of time depends on the configured retention policies. Some tables can remain the default tablespace indefinitely. For complete information about retention policies, see the Administration and Configuration Help.

NOTE: These names are examples. You can name your custom tablespaces whatever you want.

NOTE: These names are examples. You can name your custom tablespaces whatever you want.

Microsoft SQL Server Tuning

Foglight® Management Server accepts the instance-level default for database recovery (regardless of the recovery model of the model database, which is purely a template used to create new databases). There is no harm in changing the recovery model from full to simple, other than point-in-time recoverability is lost. If you require the ability to perform disaster recovery on your Foglight database, you should use the full recovery model and you should make frequent transaction log backups to ensure that it does not grow beyond an undesirable threshold. If you do not require point-in-time recoverability, you can use the simple recovery model, and there will be no additional ramifications.

PostgreSQL Tuning

PostgreSQL Server ships with a basic configuration tuned for wide compatibility rather than performance. Foglight Management Server have done some tuning configurations for the embedded PostgreSQL database, such as:

You could take the above configurations into consideration when setting up an external PostgreSQL database for Foglight Management Server, because these configurations have been verified and are more suitable for Foglight Management Server compared to default values. If you have set up PostgreSQL for other application previously, you could adjust these configurations as needed to keep them in the same PostgreSQL.

The Foglight Management Server uses the following configurations for embedded PostgreSQL database.

For more information about these configurations and how to tune PostgreSQL, refer to Tuning Your PostgreSQL Server and Performance Optimization.

Troubleshooting

High Foglight® Management Server load may consuming all connections to backend database. This results in any of the following problems:

To resolve this issue, increase available connections to the database.

The described configuration changes increase the load on the Foglight database server. You must make sure that you have adequate resources for both the Foglight Management server and the database server hosting the Foglight repository.

NOTE: If you need to enlist our professional services group to help size your environment, contact your sales representative. This is beyond the scope of Quest Support.