立即与支持人员聊天
与支持团队交流

Foglight for Java EE Technologies 5.9.13 - Installation Guide

Installing and Configuring Foglight for Java EE Technologies Integrating with JBoss Integrating with Apache Tomcat Integrating with WebLogic Domain Startup Scripts Integrating with WebSphere Integrating with WebSphere Liberty Integrating with Oracle AS Integrating with Spring Boot for Embedded Tomcat Creating a Generic Installation for Manual Java EE Agent Integration Managing Java EE Agent Installations, Integrations, and Configurations Managing Java EE Agent Configurations Managing Java EE Installation Java EE Integration Configuration FAQ and Troubleshooting Manually Integrating Application Server Appendix A: Java EE Application Methods AppendixB: Managing Permissions for the Java EE Integration Agent

Changing custom component callbacks settings

Use the Custom Component Callbacks setting to specify the classes or interfaces that the custom components use to call customer written code. The default instrumentation settings include some custom component callbacks for Apache Struts and Spring.

For more information, see Appendix: Java EE Application Methods.

1
On the General tab of the Edit dialog box, click Edit beside CustomComponentCallbacks.
Click Add to add a single class at a time.
Click Add multiple to open a text box where you can type several classes.

If you manually edit the instrumentation.config file, use the following syntax to specify custom component callback instrumentation.

CustomComponentCallbacks = ClassList (
# Apache Struts 1.x
include "org.apache.struts.action.Action",
include "org.apache.struts.action.ActionForm",
include "org.apache.struts.action.ExceptionHandler",
);

Customizing Long Running Methods

Use the LongRunningUserMethods setting to customize the collection of performance data from methods that run over a long period of time. By default, the Java EE agent waits for a method to finish running before treating the collected data as complete. However, for methods such as the run() method of a background thread or other methods that run over a long period of time, it may be preferable to treat the data as complete at specific points in the code. This makes the data available in small pieces as the method runs instead of as one large piece when the long running method completes. Changing any of these settings can have performance implications.

The Java EE agent pauses at waypoint methods (LongRunningUserMethodWaypoints) to treat the data as complete before continuing. For best performance, use a minimal set of waypoint methods.

1
Click the Long Running Methods tab of the Edit dialog box.
2
To add long running methods, click Edit beside LongRunningUserMethods.
Click Add to add a single method at a time.
Click Add multiple to open a text box where you can type several methods.
For example, to measure each execution through a loop in a long running run() method, add the method: com.globex.plan.DominateWorldThread.run.
1
On the Long Running Methods tab of the Edit dialog box, click Edit beside LongRunningUserMethodWaypoints.
Click Add to add a single waypoint at a time.
For example, add the waypoint com.globex.plan.DominateWorldThread.executeProjectArcturus to the com.globex.plan.DominateWorldThread.run method from the previous procedure.
Each time the method executeProjectArcturus() is called from run() it is considered a single request.

If you manually edit the instrumentation.config file, use the following syntax to specify long running user methods and waypoints instrumentation.

LongRunningUserMethods = MethodList(
include "com.globex.plan.DominateWorldThread.run"
);

LongRunningUserMethodWaypoints = MethodList(
include "com.globex.plan.DominateWorldThread.executeProjectArcturus"
);

In this case, the method "com.globex.plan.DominateWorldThread.run" treats the data as complete each time the method executeProjectArcturus() is called from run(). The Java EE agent pauses at waypoint methods to treat the data as complete before continuing. A minimal set of waypoint methods allows for the best possible performance.

Named Methods settings

The Named Methods instrumentation settings determine how the agent tracks specific methods. Changing any of these settings can have performance implications. Review the provided information before changing any settings.

Changing Named Methods settings

The NamedMethods setting for a Java EE agent is used to track specific methods. Specify the names of methods by forming a regular expression that matches the name or pattern. The method signature can be specified but it must be specified using the internal JVM format, as in the "DominateWorld" example below. For more information, see http://docs.oracle.com/javase/specs/#7035.

The JVM format for constructors may not be as expected. For example, for the constructor: com.quest.controller.AuthenticateAdmin.AuthenticateAdmin(), the correct signature to specify would be: com.quest.controller.AuthenticateAdmin.<init>().

1
Click the Named Methods tab of the Edit dialog box.
2
To add named methods, click Edit beside NamedMethods.
Click Add named method to define a named method.
5
Click Add to add a single method at a time.
Click Add multiple to open a text box where you can type several methods.

Next, specify the maximum number of named methods to track, as described in Changing the Maximum Number of Methods Tracked .

If you manually edit the instrumentation.config file, use the following syntax to specify named method instrumentation.

For example:

NamedMethods = {
"TakeOver": MethodList(
include /com\.globex\.takeover\..*/
),
"DominateWorld": MethodList(
include "com.globex.plan.DominateWorldServlet.doGet(Ljavax/servlet/http/HttpServletRequest;Ljavax/servlet/http/HttpServletResponse;)V",
include "com.globex.plan.DominateWorldHelper.dominate(Ljava/lang/String;Z[B)I",
),
"Globex": MethodList(
include "com.globex.pocket.Sugar",
include "com.globex.cypresscreek.HammockHut.sit",
exclude /(\.|^)globex\./
)
};

For more information about how to monitor specific methods, see the Monitoring Methods topic, in the Foglight for Application Servers User Guide.

相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级