サポートと今すぐチャット
サポートとのチャット

Foglight Evolve 9.2 - Performance Tuning Field Guide

Overview Hardware and Operating System Tuning Management Server Tuning Java Virtual Machine Tuning Backend Database Tuning High Availability (HA) Tuning Agent Tuning Appendix: Performance Health Check Appendix: Analyzing a Support Bundle

Database Checks

•
The Foglight® database growth rate cannot be assessed in the early stages of an installation. To properly assess the Foglight growth rate, wait a couple of weeks and then measure the database growth rate (slope of the curve).
•
Set up the registry variables that Foglight uses to monitor its own size. If alarms occur, then database purge operations are required.

Possible Actions

•
Set a retention policy to ensure that data is deleted after a certain amount of time has passed. This can be done globally, per type, or per metric.

Is There Too Much Data to Process?

It is possible for Foglight® to be performing fine, but still be overloaded. Foglight does have documented limits for the amount of load it can handle. If these limits are exceeded, Foglight will consume a lot of CPU on the Management Server system and on the database system, and have a slow browser interface (that is, it will exhibit the union set of all symptoms).

Data Volume is Healthy if ...

•
Data is not being dropped. If Foglight is able to process all the incoming data, then the data volume is fine.
•
The measured unit number for data is fine.
関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択