We just saw one way to review process and service communication, but let’s look at how Dynatrace understands and visualizes your applications’ transactions from end-to-end using SService Backtraces
and Service flows
With Service flow
, you see the flow of service calls FROM a service, request, or their filtered subset. Along with the specific services that are triggered, you can also see how each component of a request contributes to the overall response time.
With Service backtrace
, you see the calls TO a service.
As you plan your migration, it is important to gain a complete picture of interdependency to the rest of the environment architecture at host, processes, services, and application perspectives. Since time is always scarce, being able to do this in a single place can shorten assessment timelines.
Knowing the type of access, executed statements, and amount of data transferred during regular hours of operation allows for better planning and prioritization of the move groups. In some cases, you may decide to not migrate this database in favor of other services or databases that are less complex to migrate due to fewer dependencies.
Return to the frontend
service. You can use the breadcrumb
menu as shown below.
On the frontend
service page, locate the Understand dependenciessection on the right, and then click the
view Service flow` button.
You should now be on the Service flow page.
Right away, we can see how this application is structured:
Refer to the numbers in the picture above:
Refer to the numbers in the picture above:
backend
database