For the Foglight® Management Server to run in a virtual image, share allocations must provide the Management Server with sufficient priority over the other VMs to ensure that the Management Server can process incoming data and browser interface requests in a timely manner.
In a VMware® environment, disk (in the form of LUNs) is allocated to a Data Center, ESX® Servers, and VMs. The VMs from many ESX Servers can reside on the same LUN, which can also be shared by many ESX Servers. Therefore, the disk activity in a VM on an ESX Server can have a serious adverse impact on the performance of the VM in which the Foglight® Management Server is running, even when the VMs are running on separate ESX Servers—a situation that cannot arise when the Management Server is running on physical hardware.
The parts of the Foglight® Management Server that have the greatest influence on runtime performance are topology (management and querying), observations (conversion, storage, and retrieval), and alarms and alarm processing (derivations and rules). To provide these components and the associated calculations, an architecture that includes queues, thread-pools, caches, and so on, is required.
The Management Server architecture can be tuned in the following ways.
The server is not overloaded, and is still processing data. CPU usage on the server is high when it is providing alarm information. | |
The alarm limit may need to be reduced. MBean: *:service=Alarm Attribute: MaxAlarms Expected old value: 10000 New value: 5000 | |
You can set this parameter using the foglight.alarm.query.max_alarms JavaTM system property. For example in server.config, add: | |
You can set this parameter using the foglight.threadpool.cpu.count JavaTM system property. For example in server.config, add: |
If your dashboards are timing out, try increasing the default timeout value:
1 |
Open the <foglight_home>/server/default/deploy-foglight/console.war/scripts/ directory. |
d |
3 |
Search for DEFAULT_TIMEOUT. |
4 |
Increase the value of DEFAULT_TIMEOUT to 180000. This increases the console default timeout to 3 minutes. (The number is based on milliseconds; 1000 is one second.) |
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center