---
title: "Services"
chapter: false
weight: 7
---
## Services

Web applications consist of web pages that are served by web servers and web application processes, for example Tomcat. Web and mobile applications are built upon services that process requests like web requests, web service calls, and messaging. 

Such "server-side services" can take the form of web services, web containers, database requests, custom services, and more. Services may in turn call other services such as web services, remote services, and databases services.

### 👍 How this helps

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, application perspectives. Since time is always scarce, being able to do this in a single place can shorten assessment timelines.

### Services

Let’s now take a look at all the services being monitored by clicking on the `Services` left side Dynatrace menu.

The filtered list should now look like this:

![image](/images/aws-lab1_lab1-trans-services.png)

Choose the `frontend` service.

On the `frontend` service page, find the `Dynamic Web Requests` section on the right and click the `view Dynamic Requests` button to see what it calls. 

![image](/images/aws-lab1_lab1-dynamic-requests-arrow.png)

On this page you can view the transactions as time-series charts.

![image](/images/aws-lab1_lab1-dynamic-requests-chart.png)

On this page you can view the "top requests" and their response time consumption.  You should recognize the URLs from the sample app!

![image](/images/aws-lab1_lab1-dynamic-requests-list.png)

By clicking on one of the requests, the time-series charts are filtered to just that one request.

![image](/images/aws-lab1_lab1-request-filter.png)

### Analysis View

On the top if the page on the right is a button labeled `Create Analysis view`, click that.

![image](/images/aws-lab1_lab1-analysis-view-button.png)

Tryout the options available to view, filter and analyze data.

![image](/images/aws-lab1_lab1-analysis-view.png)

### Analyze Service Flow

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 S`Service 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.

### 👍 How this helps

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.