Chat now with support
Chat with Support

Foglight 5.9.5 - 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

Model Checks

•
Check the topology change count on the Alarms page. If there are changes in every time interval, then there is a strong possibility that the model is unstable.
•
Check the topology object count as a function of time. If no agents have been added or significantly changed recently, then the model should not be growing.

Possible Actions

•
Tune agent collection to avoid changes.

Are Too Many Alarms Firing?

It is possible for Foglight® to be configured in such a way that too many alarms are firing. There are two main manifestations of alarm instability:

•
Massive alarm fire-and-clear (that is, an excessive number of alarms are firing and clearing).
•
A large number of total alarms.

A large number of alarms can create problems when viewing alarms pages and can have an adverse affect on the functioning of federation. When a large number of alarms are generated, that consumes resources on the Management Server, which can slow down other operations.

The Number of Alarms is in a Healthy State if...

•
The total alarm count on the Alarms page meets the expectations for your monitoring goals. Any total greater than 1000 should be a concern. Alarms are clipped at 10,000, so any number approaching 10,000 indicates a problem.
•
The total number of alarms, including cleared alarms, is reasonable. It is possible to have a low number of alarms while having a huge number of cleared alarms. This is an indication of massive alarm fire-and-clear.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating