Refer to Installing the Java EE Technologies Management Capabilities section of the user guide. Sample link here mentions:
To understand what metrics are collected by Foglight for Java EE Technologies, review the agent_collector_.config files for your server type. For example, agent_collector_websphere-6.config. You can access these files from the Application Servers Administration > Java Administration > Advanced Configuration view.
Our agent instrumentation uses the following PMI when it's recording and sets them to high and adjusts back to the default when recording is complete. (For WAS5 if PMI is disabled we cannot collect from PMI)
What PMI settings the agent is designed to enable
cacheModule
jvmRuntimeModule
orbPerfModule
threadPoolModule
transactionModule
wlmModule
j2cModule
- All PMI statistics collected by JavaEE agent are as recorded in the agent collector config file.
- This config file can be located on the agent side JavaEE_Home/config/agent/collector/websphere-x.config. x is version of WebSphere appserver.
- This config can also be located on the FMS side from FMS Console> Agent Properties > JavaEE > advanced > agent_collector_websphere-x.config.
- This config file needs to be modified to control any metric collected by the agent. That is to say no modification on WebSphere will disable metric collected by the agent, unless obviously if PMI is disabled completely.
- A metric can be disabled by placing a hash (#) in front of the line.
- If config modified on the FMS, no restarts of appservers required. But if the config is modified on the agent side, modified config needs to be placed in the agent-override directory and appserver restart is required.
The config file is fairly readable for anyone familiar with WebSphere PMI and can be related to corresponding PMI modules that the agent collects data from. All metrics are being invoked with a Module Prefix. And that tells you name of the PMI module being accessed. Right after the module name comes the specific metric in that module that is being accessed. The module names and the metric names used are mostly the same as the WebSphere PMI names.
A couple of examples:
1. Example 1
"connectionPoolModule.PercentMaxed"
"connectionPoolModule.PercentUsed"
PMI Module accessed in connectionPoolModule, specific metrics being accessed are PercentMaxed and PercentUsed. These metrics correspond to Connection Pool Usage statistics shown in Foglight.
2. Example 2
/^beanModule>.+>ejb\.entity>[^>]+$/: (
"ActivateCount",
"PassivateCount",
"MethodResponseTime",
"ReadyCount",
Bean Module and its submodule for entity ejb is accessed. Metrics collected from this module are ActivateCount, PassivateCount etc. These metrics correspond to Entity EJB metrics shown in Foglight.