Chatta subito con l'assistenza
Chat con il supporto

Foglight for Java EE Technologies 5.9.9 - Installation Guide

Install and Configure Foglight for Java EE Technologies Integrate with JBoss Integrate with Apache Tomcat Integrate with WebLogic Domain Startup Scripts Integrate with WebSphere Integrate with Oracle AS Create a Generic Installation for Manual Java EE Agent Integration Manage Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Java EE Installation Management Java EE Integration Configuration FAQ and Troubleshooting Manual Application Server Integrations AppendixB: Managing Permissions for the Java EE Integration Agent Appendix A: Java EE Application Methods

Editing agent instrumentation configurations

The agent configuration editor provides a GUI for editing instrumentation settings. This simplifies the process for users.
* 
NOTE: In previous versions of Foglight for Java EE Technologies, these settings were manually edited in the instrumentation.config file. If you prefer this method, see Manually editing instrumentation settings .
To edit an agent instrumentation configuration:
1
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
2
On the Application Servers Administration dashboard, click Java Administration.
3
On the Java Administration dashboard, click the Agent Configuration tab.
4
On the Agent Configuration tab, click the name of the agent configuration that you want to edit.
5
On the menu that opens, click Edit instrumentation settings.
The Edit — <configuration name> dialog box opens.
For information about the settings available on each tab, see the following topics:
•
General instrumentation settings
•
Customizing Long Running Methods
•
Named Methods settings
•
Object Tracking settings
•
Requests settings
•
Customizing instrumented classes
* 
IMPORTANT: If you change the instrumentation, restart the affected application servers.

Manually editing instrumentation settings

It is possible to manually edit the settings in the instrumentation.config file instead of using the GUI editor. If you are comfortable and familiar with these settings from previous versions of Foglight for Java EE Technologies, you may prefer to use the text editor.
To manually edit the instrumentation settings:
1
On the navigation panel, under Dashboards, click Application Servers > Administration > Application Servers Administration.
2
On the Application Servers Administration dashboard, click Java Administration.
3
On the Java Administration dashboard, click the Agent Configurations tab.
4
On the Agent Configurations tab, click the name of the agent configuration that you want to edit.
5
In the menu that opens, click Manage.
The Java Agent Configuration: <configuration name> view opens.
6
From the Version list, select the version of the Java EE agent (for example 5.9.2 or 5.8) that you want to work with.
7
Click the name of the file that you want to edit. In this case, click instrumentation.
8
In the menu that opens, select Text edit.
9
Type the required information in the text editor.
10
After you set all the required values, click Save.
11
Restart the application server.

General instrumentation settings

The General instrumentation settings for a Java EE agent include instrumentation levels, simple methods, user classes, custom components, and custom component callbacks. Changing any of these settings can have performance implications. Review the provided information before changing any settings.
Related topics
•
Changing the instrumentation level for Request Metric data collection
•
Configuring instrumented simple method settings
•
Changing user classes settings
•
Changing custom component settings
•
Changing custom component callbacks settings

Changing the instrumentation level for Request Metric data collection

The Java EE agent uses instrumentation for request monitoring and to collect single traces. This instrumentation does add some overhead to your monitored servers and the information collected indirectly applies load to the Foglight Management Server. However, if you only require single traces collected at component level, or you do not require request monitoring at all, you can reduce or turn off instrumentation using the Instrumentation Level setting. This reduces the overhead on your monitored servers and the load on the Foglight Management Server.
The default instrumentation level is FullDetail. At full detail level, request monitoring can be enabled and, when single traces are collected, all nodes in the call tree are included. This level provides the most flexibility in terms of request monitoring and single trace collection and should be acceptable for most customers.
If you require request monitoring, but do not require full detail single traces, instrumentation can be set to Component Detail. At component detail level, you can enable request monitoring, but when single traces are collected, they are collected at only the component technology detail level, reducing the complexity of the call tree. This level is more restrictive in what information can be collected for single traces, but reduces both the agent overhead on the monitored server and the load on the Management Server.
If you require request monitoring but only require request metrics for HTTP, JMS, and RMI requests, instrumentation can be set to Basic Detail. At this level, no breakdowns are collected and, if single traces are collected, only HTTP, JMS, and RMI nodes are included in the Request Trace call tree. No other component or full detail methods are collected, therefore reducing both the agent overhead on the monitored server and the load on the Management Server, compared to the Component Detail instrumentation level.
If you do not require request monitoring or the ability to capture single traces, instrumentation for this purpose can be disabled by setting the instrumentation level to No Detail. At this setting, request monitoring cannot be enabled and you are unable to capture single traces at any detail level. This removes instrumentation overhead on the monitored server and greatly reduces load on the Management Server.
* 
IMPORTANT: If you want to monitor the classes or interfaces that custom components use to call customer written code, see Changing custom component callbacks settings .
To set the instrumentation level:
* 
TIP: To review how to access the instrumentation settings editor, see Editing agent instrumentation configurations .
1
On the General tab of the Edit dialog box, select the instrumentation level from the InstrumentationLevel list.
•
Full Detail — Instruments at full detail level. All methods in the call tree are captured.
•
Component Detail — Instruments at the component level only. Methods from defined component technology, including custom components, are captured.
•
Basic Detail — Instruments at a basic level. Only request metrics for HTTP, JMS, and RMI request are collected. No other component or full detail methods are captured.
•
No Detail — Turns off instrumentation that is not essential for running an agent. As a result, no request metrics are collected, and single traces call trees cannot be captured.
* 
NOTE: As a result of setting instrumentation to this level, no data is displayed in the Application Servers Monitor > Requests tab.
2
Click Save.
3
Restart your application server.
Manual configuration — InstrumentationLevel
If you manually edit the instrumentation.config file, use the following syntax to set the instrumentation level:
 
Table 5. Instrument level syntax.
Level
Syntax
FullDetail
InstrumentationLevel = "FullDetail";
ComponentDetail
InstrumentationLevel = "ComponentDetail";
BasicDetail
InstrumentationLevel = "BasicDetail";
NoDetail
InstrumentationLevel = "NoDetail";
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione