Converse agora com nosso suporte
Chat com o suporte

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

Sampling Frequency

All converted Foglight® 4 agents have a secondary ASP (usually called SamplingFreq) that controls data collection frequencies.

To access that ASP, select an agent in the Administration module of the browser interface and then choose Edit Properties.

XML-HTTP Agent Adapter

The XML-HTTP Agent Adapter enables agents to post data in XML format over HTTP(S).

By default this adapter is configured to reject posted XML text larger than 20MB.

 
Table 4. XML-HTTP Agent Adapter
Motivation

The XML-HTTP agent adapter rejects large XML submissions to protect the server from memory overload.

Symptom

An agent that uses the XML-HTTP protocol complains that the server is rejecting its data.

Diagnosis/Verification

Check the agent logs for specific error messages indicating that the data was rejected due to size constraints.

Tuning

Open web.xml, which is located in <foglight_home>/cartridge/XmlHttpAgentAdapter-*.car, component XmlHttpAgentAdapter-5_2_4\WebApp-\foglight-xml-agent-adapter.war, file WEB-INF\web.xml, and adjust the maxContentLength parameter.

Note 1

You will need to unzip the .car file, then unzip the .war file, edit the web.xml file, and then re-package the cartridge manually (using zip).

Note 2

After you modify the cartridge, you will have to delete <foglight_home>\state\cartridge.exploded\XmlHttpAgentAdapter-*, and then restart the Management Server.

Dropped Agent Manager Log Messages

The default settings for the Foglight® Agent Manager are configured to impact the system as little as possible. However some agents put additional load on the system, which results in dropped log messages such as the following:

2010-11-29 17:03:56.816 VERBOSE Upstream Polling-0 com.quest.glue.core.comms.transport.http.Client - Upstream message exchange took 100,525 ms which is close to or above the maximum polling interval of 10,000 ms. Batch size has been decreased to 162.

.

.

.

2010-11-29 17:12:03.376 WARN CachedOutgoingQueueWorker com.quest.glue.common.comms.CachedOutgoingQueue - Removed 253 messages because the message queue is full.

To resolve this issue, increase the message cache size (that is, the max-disk-space setting in the <FglAM_home>/state/default/config/fglam.config.xml file).

Java EE Technologies

The configuration of the Cartridge for Java EE Technologies agent has the potential to significantly influence Foglight performance.

For information about configuring the Cartridge for Java EE Technologies, see the Foglight® for Java EE Technologies documentation.

 

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação