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

Determining correct mappings for User Actions going to the Default Applicaiton

jeff_rowell
Organizer

Dynatrace does not appear to currently offer any means
to easily analyze traffic related to the Default Application, to aid in a “clean
up” of the monitoring configuration. Although you can easily view the domain references
in the User Actions that maps to the Default Application, and can easily “transfer”
the request to another application, I have not been able to figure out a way to determine that services the user actions interact with (since we tag our services with an application name this would allow me to know what application is being interacted with).

I should point out that I am aware that I can view all of the User Actions and their domain references by selecting the Default Application, and that I can then drill into a user action... but I do not see any way to determine which services are being invoked.

Perhaps I am missing something... if anyone can suggest an approach that would work to determine what services are being called please let me know. Otherwise perhaps this should be a product enhancement request.

 

6 REPLIES 6

joshua_lange
Helper

Jeff,

Have you tried to analyze the service flow diagram from the application data? When drilling into an application there is a large info graphic on the top. Look at the right hand side there is a small box that indicates the number of services this application directly interacts with. When selecting that box a table will populate just below and there will be a button you can click to see the service flow. Would that help this situation?

In general my process for 'cleaning up' the default catch all application rule is to look at the 'top 3 included domains' table and use that as a basis for defining new rules. If your applications are determined by URI paths rather than top domain, then the service flow option I mentioned would be the best route.

Let me know if that helps!

Cheers,

Josh


jeff_rowell
Organizer

Thanks Josh,

Unfortunately that approach doesnt work. From the service flow I can see all of the services that the Default Application interacts with, but I cant determine, from that view, which User Actions / Domains interact with each servce. I can drill into a "Top web requests" screen for each service, which shows me the requests that came to that service from the Default application, but this info doesn't show any information on the user actions + their domain references.


joshua_lange
Helper

Got it. Since the service flow identifies which services the Application interacts with select the service of interest from the service flow and while it's highlighted there should be 3 small boxes at the top of the selected service. Starting from the left you have purepaths, filter, and analyze. Choose analyze, then perform a service backtrace. This will generate a filtered view for the selected service and map back to the application. Select the application line in the backtrace and it should populate a table which actions are making calls to the service you drilled into the backtrace from. You would then repeat this for any other service the application calls.

Am I on the right track with your goals?


jeff_rowell
Organizer

Thanks for the suggestion! I can see that those steps allow me to see which User Actions are invoking the service... the problem is, however, that when I see the list of User Actions I see no information on the full URL with the referenced domain name - I have to then drill down again on each action to see the referenced domain. The good news is that this process will work, so thank you very much for your help in working this out. The unfortunate thing is, however, that it is a lenghtly process to do this - its unfortunate that the product does no currently provide an easier way of obtaining a list of user actions that map to the Default Application and the service(s) that they directly interact with.


joshua_lange
Helper

I'm glad we're able to get you what you need for the time being. We always welcome feature requests and I encourage you to submit one here: Dynatrace RFE Forum


jeff_rowell
Organizer

Thanks again. I just posted a RFE related to this.