DX Application Performance Management

StefanSiegl

Did you get this issue address? What was the resolution?

Here is document I recently uploaded on this topic:

https://communities.ca.com/docs/DOC-231153926

Lynn_Williams and Hiko_Davis -

I have this same problem with a 9.7 installation. Followed the steps in the doc but get nothing when trying to record a transaction in CEM. I noticed the autoprobe log still shows directives commented out after parsing default-full.pbl. Any thoughts?

> #######################

> # HTTP Header Decorator

> #

> # Enable this PBD for CEM integration.  It appends additional

> # information to the HTTP response that is then captured by CEM.

> # ================

>

> #httpheaderdecorator.pbd

>

> #######################

> # LeakHunter

> #

> # Enable this PBD to help locate the source of potential memory leaks.

> # This will incur overhead, so enable LeakHunter only when necessary.

> # See LeakHunter documentation for usage and configuration details.

> # ================

>

> #leakhunter.pbd

>

> #######################

> # BizRecording

> #

> # Enable this PBD to allow the Agent to record business transactions for

> # CEM/TESS.

> # ================

>

> #bizrecording.pbd

Finished file dump for C:\Program Files\CA APM\Introscope Agent 9.7.1.16\wily\default-full.pbl

You have to uncomment (remove the '#' in front of) httpheaderdecorator.pbd and bizrecording.pbd!

As I mentioned, I followed the instructions in the doc. So the lines *are* uncommented and this is still happening. That was the point of my post

I restarted the agent, EM, even the vm that runs everything. There are no errors in any logs. Still I don't capture anything when I attempt to record a transaction. So was hoping someone else might have run into this and had a quick answer.

Hi James,

Sounds very strange if "C:\Program Files\CA APM\Introscope Agent 9.7.1.16\wily\default-full.pbl" definitely has the above lines uncommented.

Please:

• stop the agent,
• backup/delete existing logs,
• in IntroscopeAgent.profile set:"log4j.logger.IntroscopeAgent=DEBUG, logfile" and "log4j.appender.logfile.MaxFileSize=50MB"
• restart agent & upload IntroscopeAgent.profile,  IntroscopeAgent & Autoprobe logs.

Also what AppServer is this?

Thanks

Lynn

Thanks, Lynn_Williams. I think there might have been some kind of vm issue. After a few more reboots the autoprobe log now shows httpheaderdecorator and bizrecording PBD's are being loaded. However I still don't see anything when I try to record a business transaction. For client IP I've tried 127.0.0.1, 0.0.0.0, and the internal IP address. I have several simple apps running on this server: Java/Tomcat, IIS/Webforms and IIS/MVC. I ran through each app while recording and captured nothing. Is there something else I can check?

Thanks.

Hi James,

Maybe try with an example Tomcat app first.I successfully tested recording a Tomcat 8 example JSP app with APM 10 agent & EM on same machine

With DEBUG enabled on the agent you should see this type of data in the log:

====

8/05/15 08:40:46 PM EST [DEBUG] [IntroscopeAgent.Agent] BizRecording session 700000000000000001(127.0.0.1, ) added

...

8/05/15 08:41:01 PM EST [DEBUG] [IntroscopeAgent.Agent] BizRecording component recorded

Name=/jsp/jsp2/el/basic-arithmetic.jsp

Path=/examples

Date=1438771260490

Address=127.0.0.1

Port=28080

RequestHeader=

GET /examples/jsp/jsp2/el/basic-arithmetic.jsp HTTP/1.1

host: 127.0.0.1:28080

connection: keep-alive

accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8

upgrade-insecure-requests: 1

user-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2403.125 Safari/537.36

referer: http://127.0.0.1:28080/examples/jsp/

accept-encoding: gzip, deflate, sdch

accept-language: en,en-US;q=0.8,en-AU;q=0.6

cookie: JSESSIONID=FABBE3F164098590C3210BC38584AF81

RequestBody=

ResponseHeader=

HTTP/1.1 200 OK

Content-Type: text/html

ResponseBody=nul

...

8/05/15 08:41:40 PM EST [DEBUG] [IntroscopeAgent.Agent] BizRecording session 700000000000000001 removed

=====

Thanks Lynn_Williams. I see we're using the same test apps

So far I have been testing with the .NET agent but I'll switch to the Java agent...

Here are the entries in my log:

8/05/15 10:50:25 AM EDT [DEBUG] [IntroscopeAgent.Agent] BizRecording session 700000000000000006(127.0.0.1, ) added

8/05/15 10:50:31 AM EDT [DEBUG] [IntroscopeAgent.Agent] BizRecording component rejected Address=0:0:0:0:0:0:0:1 vs ClientIPFilter=127.0.0.1 Language=en-US vs LanguageFilter=

8/05/15 10:50:43 AM EDT [DEBUG] [IntroscopeAgent.Agent] BizRecording session 700000000000000006 removed

And nothing is recorded in CEM.

Try with (IPv6) Client IP address 0:0:0:0:0:0:0:1.

Bingo (for Java)

Thank you!

But is there a config option somewhere so I can make ipv4 work?

However this does not work with the .NET agent, and my customer needs this. Any ideas?

It's a Java/app server setting, not an APM setting. Add -Djava.net.preferIPv4Stack=true to CATALINA_OPTS for Tomcat.

See tomcat6 - How does one get tomcat to bind to ipv4 address? - Server Fault

Thanks again.

Any idea why I can't get this to work with the .NET agent? I made the same config changes to the agent profile, try to record in CEM the same way, and get nothing.

Hi James,

Initially I had a similar problem on .NET of nothing being recorded. I found that ipv6 was also the root cause after enabling DEBUG instead of INFO in the 3rd line of logging.config.xml

=====

8/06/15 07:56:49 PM GMT+10 [DEBUG] [IntroscopeAgent.Agent] BizRecording component rejected

Address=::1 vs ClientIPFilter=127.0.0.1

Language=en-US vs LanguageFilter=

=====

Not sure how to force IIS to use ipv4 but after I switched the recording session Client IP to be ipv6 "::1" the recording worked.

Regards,

Lynn

Thanks again Lynn_Williams. After 2 reboots that worked. I think I have some kind of vm caching issue happening.

To make Windows prefer ipv4 you can download the MS Fixit from this link:

https://support.microsoft.com/en-us/kb/2533454

You can also modify the registry manually as explained here:

https://support.microsoft.com/en-us/kb/929852

Or you can use NETSH commands to accomplish the same thing (use help command for examples):

netsh interface ipv6 add prefixpolicy

Thanks James, glad you got there eventually

Lynn_Williams this does not work with a .NET MVC app, which brings me back around to me larger, original problem (in another thread)... .NET MVC apps "hide" the url. URLs don't display in the frontends/URLs node of the investigator, and CEM can not record a transaction if the app is MVC. This is a big problem and a few people are looking into it. fyi pageinfotracer does not work, as some have suggested it *should* work.

Do you have a MVC app you could test with? We currently have a very unhappy customer because of this.