Without a session it is just guess work as I have not seen this before. However, for PurePaths, grayed out methods are those that were found using autosensors. If you Right-click and select details it provides that information. I suspect similar information would be provided if you right-click and select details on the User Action PurePath method. Not necessarily that it is from an autosensor but would explain where it is from.
These grey "Web Request Nodes" are what we called "Orphaned Web Requests". These are Web Requests that were executed by that Visit but could not be assigned to a User Action. Why couldnt they be assigned? Well - there could be multiple reasons for it
so - this is a new feature that we recently introduced. Its great to see all Web Requests by Visit - even those not assigned with a User Action.
It seems to be not well documented as you said - there is one reference though on the following doc page: Visits
Hi. I had a look at your "Orphaned Web Requests" session. It seems that the orphaned requests are those that are static resource downloads triggered by CSS files such as https://www.globalshop.com.au/products/DependencyHandler.axd/86b8c182a9a2130a7f2fc805db4e91c9/101186...
Dynatrace is able to "link" static downloads such as images, js and css files based on the the Refer and our Cookies. Static resources that are referenced in a CSS file and then downloaded by the browser are not yet handled in the same way. I just double checked that with engineering and they suggest to create an RFE for this. I just did. Please vote this up: RFE - Assign Static Requests from CSS files to correct User Action
Are 'Orphanedd Web Requests' considered when calculate conversion, we happen to rely on the 'purchase/complete' request as conversion goal, which was orphaned sometimes, it seems that dt ignores it when evaluate whether the visit is converted or not, as a result, the conversion reported by dt doesn't match with the customer's order system.
I just realized that the 'orphaned web request' that i wanted you to look at is 'purchase/complete' rather than those static resource downloads, i exported two visits to the above session for comparison, both visits triggered 'purchase/complete', however, it's attached to user action "Loading of purchase/complete'" in one visit but orphaned in the other.
Can you double check this and advise if this can be fixed?
Hello, Is anyone aware of a way to chart the amount of orphaned web requests occurring?
I was looking at linked and unlinked web requests. But I think orphaned requests and user action requests are all counted as "linked requests"
Hi, no there is no way to chart the number of orphaned web requests. linked/unlinked web requests are correlation internal self-monitoring metrics.
Why is the orphaned web request count important for you?