cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

How to track web request through User Action PurePath

skumaresan
Contributor

Attachements

userexperience-config.pngcmscontent-request.pngcmscontent-considered-as-third-party.pngapache-sensor-placement.png

Issue description:

Our product detail page,

groceries.asda.com/product/muffins-donuts-cookies/asda-extra-special-4-belgian-triple-chocolate-cookies/910003076776

The following content is retrieved through Endeca Search Engine. The server doesn't contain the dtagent.

https://groceries.asda.com/cmscontent/json/pages/browse/product?Endeca_user_segments=loggedIn&Nr=AND(parentCategory.hasPrimaryShelf%3A1%2Csku.store%3A4571)&Nrs=collection()%2Frecord%5B((product.startDate%3C%3D1499366137251+and+product.endDate%3E1499366137251)+or+(product.comingSoonStartDate%3C%3D1499366137251+and+product.comingSoonEndDate%3E1499366137251))%5D&Ntt=910003076776+muffins-donuts-cookies&No=0&Nrpp=60&requestorigin=gi&_=1499366137251

We are not seeing above web request in all the product details pages.

It is coming up only in very few requests.


We would like to track and measure the performance of this request through "User Action Purepaths" in all product detail pages.

What would be the best approach?. Do we have to enable the Java Web Request sensor in Apache agent group? If yes, will it overload the data capture in Dynatrace.

Please share your thoughts.

Attached the below images for reference

1.Apache Sensor Placement.png

2.cmscontent request.png [User Action purepath having https://groceries.asda.com/product/muffins-donuts-...

3.userexperience config.png [Contains user experience configuration of the profile]

Note: In some cases, it is considered as Third Party request. Attached the image for details. [cmscontent considered as third party.png].

2 REPLIES 2

rick_boyd
Mentor

Hi,

There is no further instrumentation you can do, short of putting an agent on Endeca.

The Java Web Request sensor won't do anything in the Apache agent group, as it is not Java-based. The likelihood is either (a) those requests are hitting an endpoint that is not in your Apache agent group or (b) (more likely, if I understand your "It is coming up only in very few requests" comment), it is often being served by cache on a CDN

Hope that helps,

Rick B

skumaresan
Contributor

Thanks Rick B.