Application-detection does not work
Hello,
we are using dT 5.5 with UEM and PHP.
We get a webrequest and a visit for our application, but they do not match, so that i can't drill down.
I noticed that the application on the visit is detected. The detection for the webrequest does not work. I read that this can be a reason for the UEM-Backend-Connection: User Experience Management Administration#Troubleshooting
When I look at the details of the WR, there is no host and no Webappilcation-id detected, so that I can't configure the User-defined Applications.
What can I do?
Thanks
Jan
is dynatrace just capturing purepath based on webrequests?
we have a jboss running serveral java applications which just do job queuing processing, meaning the java applications are reading from database and send the results to external APIs.
there is no incoming transaction in form of a web request where java web servlets are involved and our applications tab in the System Profile stays empty.
the applications are also invoked via java RMI calls, this is something which can be seen as "incoming" traffic but again without any involvement of web requests.
when it comes to properly recognized applications the only thing which is autodiscovered is the JSON JMX agent where mbean information is being read via jolokia plugin and where a web request is in the game.
how could i capture purepaths for the actual job queue java apps running in Jboss, the RMI calls being made, DB calls, etc?
thanks for some help.
Hi Edwin
dynaTrace can capture PurePaths for ANY type of transaction. Out of the box we start PurePaths for Web Applications. You can however either
a) change the sensor configuration of the RMI Sensor to "active and start PurePath" (that can be done in the System Profile -> Agent Group -> Sensor Configuration) or
b) you can define your own custom entry point sensors. A custom entry point sensor is a sensor that you define, e.g: for a method that executes a job but you define it as "active and start purepath". that is an option you have in your sensor configuration
For more information see Sensor Configuration and Agent Group - Sensor Configuration
Hi,
thank you for your replies. The reason for this was a bit embarrassing. There was a wrong filter in the WebRequest-SensorPack, so that all expected Requests are missing...
As usual the problem is sitting in front of the monitor. 
Thanks for letting us know. Its not the first time we see a "Layer 8" problem 
Hi Jan,
The Web Application Id is a different thing, than the application. The Web Application Id is used for Java Web Applications. In your Web Request dashlet you should see a different column Application which should match the application from the visit. An application can be configured not only by the host header (which seems to be missing here) but also by URL --> please look at the application detection in the system profile.
But of course it would be good to have the Client IP and Host headers on the requests, so it seems that your application is using different headers for that information. Go to the server config and add your headers which are filled with the client ip and the host information.
But I'm not sure this is really your problem. So it seems what you are really want to do, is drill down from the visit to the web request (or the other way around?). So if you drill down from the visit to the user action pure path, can you than see the request you are looking for?
Please not, not all web requests are correlated to user actions. For example if a html page is triggering a ajax request 20 seconds after the load has finished, this ajax request will not be correlated to the user action. If my information does not help you, please add a support ticket. Our support members can help you very quick or contact me again.
Alex
