The purpose of a health check is to quickly ensure that Foglight® is functioning properly. There are many things you can check. The more important ones are documented in this chapter.
By default, Foglight® tries to reserve three quarters of the local available physical memory. It is normal for Foglight to consume all of that memory on start up. Foglight reserves its full amount of memory on start up. Foglight is configured this way to avoid excess garbage collection.
If there is enough memory reserved, the Foglight JavaTM Virtual Machine (JVM) heap graph will display an adequate amount of free memory. It is normal for the memory to cycle up and down. As long as these memory cycles are not close together (which indicates excessive garbage collection), then all is well. Also, as long as free memory continues to be returned through garbage collection, then the amount of memory configured is fine.
• |
Check the -Xmx and -Xms settings in the Foglight® log to make sure they match expectations. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Termini di utilizzo Privacy Cookie Preference Center