AppD Archive

EUM Manual Injection Rule - WebSphere/JSF 2.x

CommunityUser
Splunk Employee
Splunk Employee

We're working with a JSF 2.1 Web application deployed to a WebSphere 7.0.x container. We also have multiple Pro licenses for AppDynamics and the current deployed version is 3.6.1.

Automatic EUM is not detecting any business transactions so we'd like to configure the rules manually. 

Would it be possible to provide sample configurations for standard frameworks like JSF? We're using the stock implementation & not doing anything outside the box. Trying to follow the trail of JSF internal classes in order to figure out what class handles writing to the response stream is proving to be quite difficult.

I would love to know what values to fill in for the manual configuration rules:

1) Class and method to intercept

2) Pointer to the writer

3) Injection options

At least that would provide a starting point for the investigation if the rules don't end up working.

Thanks.

0 Karma

Arun_Dasetty
Super Champion

Hi Sean,

We see that JSF2.0 is the version supported by 3.6.x agents as per docs: http://docs.appdynamics.com/display/PRO12S/Supported+Environments+And+Versions#SupportedEnvironments... , However you can give a try as per sample and examples provided in below doc: http://docs.appdynamics.com/display/PRO12S/Configure+End+User+Monitoring#ConfigureEndUserMonitoring-...

Let us know if this information helps

Regards,

Arun

0 Karma

CommunityUser
Splunk Employee
Splunk Employee

Thanks -- I was already referring to that page in my attempts to configure EUM.

The application we're working with is too large & costly to use manual attribute injection (which requires code changes), so I was attempting to configure some injection rules.

This issue I'm having is that I'm not familiar with JSF internal classes, so as per my last post I don't know what values to fill in for the "Pointer to writer" & "Injection options". We don't have any custom renderers, so everything would be using the JSF stock implementation.

0 Karma

Arun_Dasetty
Super Champion

Hi Sean,

Let us know if the following information helps:

Summary of fields in manual rule:

1. In the Manual tab, click the Add icon.
The Create Manual Injection Rule screen is displayed.

2. In the Name field, enter a name for the rule.

3. Check the Enabled checkbox.

4. In the Class and method to intercept section, define the match conditions for the class and method that write to the output stream. This is the class that AppDynamics intercepts for injection.

5. If the write method is overloaded check the Is this Method Overloaded? check box, then click Add Parameter and add the parameters that define the method.

6. In the Pointer to the writer section, specify how to obtain the output writer stream in the intercepted method.

7. In the Injection options section, specify the output stream class method AppDynamics should use to inject and where to inject (before or after the footer or the header).

refer attached sample manul jsf  eum rule, and do changes accordingly that meets above requirement.

Please be sure to remove package/class details from exclude section under bci-excludes in app-agent-config.xml in <agent_dir>/conf file if the class name is part of default excludes , ex: javax

Regards,

Arun

0 Karma
Get Updates on the Splunk Community!

See just what you’ve been missing | Observability tracks at Splunk University

Looking to sharpen your observability skills so you can better understand how to collect and analyze data from ...

Weezer at .conf25? Say it ain’t so!

Hello Splunkers, The countdown to .conf25 is on-and we've just turned up the volume! We're thrilled to ...

How SC4S Makes Suricata Logs Ingestion Simple

Network security monitoring has become increasingly critical for organizations of all sizes. Splunk has ...