NEW - You can now accelerate your migration and modernization with AWS Transform. Read [Getting Started](https://docs.aws.amazon.com/transform/latest/userguide/getting-started.html) in the *AWS Transform User Guide*.

# Access details for an application
<a name="application-details"></a>

There are several ways you can access the **Application details** view. 

Click on the **Application name** of any application on the **Applications** page. 

![\[Applications page showing one active application named "App 3" with migration status and health indicators.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-1.png)


Click on the **Application** of any server on the **Source servers** page. 

![\[Source servers page showing one server with application "arch-app" ready for cutover.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-2.png)


Click on the **Application name** in the **Server info** tab. 

![\[Server info tab showing Application name field with "App 3" value highlighted.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-3.png)


Click on the **Application name** of any application in the **Applications** table inside **Wave details** -> **Applications** tab. 

![\[Dashboard showing application status with alerts, migration progress, and details for App 3.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-4.png)


The **Application details** view shows information and options for an individual application. Here, you can control and monitor the individual application. 

![\[Application details view showing overview, alerts, data replication, and migration lifecycle status.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-5.png)


 You can also perform a variety of actions on the application, and perform batch operations such as launch Test and Cutover instances for the servers associated with the application. 

The **Application details** view is divided into several dashboards: 

**Topics**
+ [

# Review overall application status
](application-overview-dashboard.md)
+ [

# Source server migration metrics
](application-source-server-migration-metrics.md)
+ [

# Review application source servers
](application-source-servers-table.md)
+ [

# Review application tags
](application-cirrus_tags.md)

# Review overall application status
<a name="application-overview-dashboard"></a>

The **Overview** dashboard provides an overview of the overall application status, including: 
+  **Description** – The description of the application. 
+  **State** – The state of the application. **State** can be in one of two states: **Active** or **Archived**. 
+  **Last status update** – Time stamp of when application status was updated (update occurs every five minutes). 
+  **Wave name** – Name of the wave that the application is associated with. 
+  **Migration status** – The application migration status. 

   Application **Migration status** can have one of the following values: 

   **Not started** – If none of its servers has started replication yet. 

   **Completed** – If all of its servers completed migration (have been cutover). 

   **In progress** – At least one of its servers has started replication and not all of its servers completed migration. 
+  **Alerts** – The application alert. 

   An application that has at least one server that is experiencing significant issues, such as a stall, will display a **Stalled** status. 

   An application that has at least one server that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. 

   A healthy active application will display a **Healthy** status. 

   An archived application will not display a status. 

# Source server migration metrics
<a name="application-source-server-migration-metrics"></a>

The source server migration metrics show an aggregated overview of the application associated servers on three topics: **Alerts**, **Data replication status** and **Migration status**. 

# Review source server alerts
<a name="application-source-server-migration-metrics-alerts"></a>

The source server **Alerts** migration metric presents an aggregated overview of the application associated servers alerts. You can look up an individual source server **Alerts** status at the **Source servers** table at the bottom of the page. 

![\[Pie chart showing server status: 2 healthy servers (66.7%) and 1 launched server (33.3%).\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-7.png)

+ A healthy server for which a test or cutover instance has not been launched will display a **Healthy** status. 
+ A healthy server for which a test of cutover instance has been launched will display a **Healthy** status. 
+ A server that is experiencing a temporary issue such as lag or backlog will display a **Lagging** status. 
+ A server that is experiencing significant issues, such as a stall, will display a **Stalled** status. 

# Review source server data replication status
<a name="application-source-server-migration-metrics-drs"></a>

The source server **Data replication status** migration metric presents an aggregated overview of the application associated servers data replication status. You can look up an individual source server **Data replication status** status at the **Source servers** table at the bottom of the page. 

![\[Pie chart showing data replication status: 66.7% healthy, 33.3% initial sync.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-8.png)


Source server **Data replication status** can have one of the following values: 
+  **Transferring snapshot** 
+  **Initial sync** 
+  **Finalizing sync** 
+  **Lagging** 
+  **Healthy** 
+  **Stalled** 
+  **Rescanning** 
+  **Not started** 
+  **Initiating** 
+  **Creating snapshot** 
+  **Paused** 
+  **Disconnected** 

# Review the application source server migration lifecycle
<a name="application-source-server-migration-metrics-migration"></a>

The source server **Migration lifecycle** metric shows an aggregated overview of the application associated servers migration lifecycle. You can look up an individual source server **Migration lifecycle** status at the **Source servers** table at the bottom of the page. 

![\[Pie chart showing migration lifecycle status: 33.3% each for Ready for cutover, Ready for test, and Not ready.\]](http://docs.aws.amazon.com/mgn/latest/ug/images/app-9.png)


Source server **Migration lifecycle** can have one of the following values: 
+  **Stopped** 
+  **Not ready** 
+  **Ready for testing** 
+  **Test in progress** 
+  **Ready for cutover** 
+  **Cutover in progress** 
+  **Cutover complete** 
+  **Disconnected** 
+  **Discovered** 

# Review application source servers
<a name="application-source-servers-table"></a>

The **Source servers** table lists all the servers that are associated with the application. 

To perform batch operations on all the servers, use the application **Actions** menu at the top of the page. To perform an operation on a single server, go to the specific server's **Server details** page by clicking the server **Source server name**.

# Review application tags
<a name="application-cirrus_tags"></a>

The **Tags** section shows any tags that have been assigned to the application. A tag is a label that you assign to an AWS resource. Each tag consists of a key and an optional value. You can use tags to search and filter your resources or track your AWS costs. Learn more about AWS tags in [this Amazon EC2 article. ](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Using_Tags.html)