Explore the Application Overview Page

The Overview page of an application displays detailed information about the deployed application.

The following table describes key information that you’ll see on the application Overview page.

Element	Description
Summary	Manages application instances and the memory allotted to each application instance. In Instances, specify the number of application instances. By default, two application instances are allotted when the application is created. In Memory, specify the memory (in GB) allotted to each application instance. By default, 2 GB of memory is allotted. In Average Memory Usage, see the average for all application instances of the percentage of the total allocated memory that’s used.
More Information	Displays the following information about the application: Current version of the deployed application Date-time stamp of the last deployment Runtime environment and version used to execute the application. For Python, Ruby, .NET, and Go applications, you can use this value to find the application in DockerHub and download it from there. Type of the application, web if public and worker if private. See Preparing a Worker Application for Deployment in Developing for Oracle Application Container Cloud Service. Region to which the application was deployed Security IP List, which you can add to a security rule for a virtual machine (VM) in Oracle Cloud Infrastructure Compute Classic. This allows your application and the VM to communicate. Application cache used, if any A Manage Access link if you selected Basic or OAuth authentication during application creation. Click this link to go to Oracle Identity Cloud Service. See Use Oracle Identity Cloud Service with Oracle Application Container Cloud Service. Tags assigned to the application. You can assign or remove tags without redeploying the application. See Create, Assign, and Unassign Tags.
Resources	Lists all instances allotted for the application, including their allocated memory and memory usage. A public application has instances named web.N. A worker application has instances named worker.N. See Preparing a Worker Application for Deployment in Developing for Oracle Application Container Cloud Service.

Scale an Application Out or In

Scaling an application out or in means that you’re to increasing or decreasing the number of instances.

1. Under Instances, enter the number of desired instances, or use the up and down arrows to set the number of instances.
   After you change the number of instances, you’ll see the Apply and Cancel buttons.
2. After you've set the number of instances to your desired value, click Apply.
   A confirmation dialog box appears. Its message indicates that new instances are started and old instances are still running.
3. Click Apply. Your application scales or in to the number of instances requested.

Scale an Application Up or Down

Scaling an application up or down means that you’re to increasing or decreasing the size of each instance.

1. Under Instances, enter the desired size of each instance in GB, or use the up and down arrows to set the size of instances.
   After you change the size, you’ll see Apply and Cancel buttons.
2. After you've set the memory size of each instance to your desired value, click Apply.
   A confirmation dialog box appears. Its message indicates that all instances are restarted.
3. Select Rolling Restart or Concurrent Restart.
4. Click Apply. Your application scales all instances up or down to the desired memory size.

Considerations when Scaling Applications

Your instances start or restart depending on the scaling operation.

The direction that you scale determines if your instances restart or just start:

• If you’re scaling out, then new instances start.

• If you’re scaling in, then all instances are restarted.

• If you’re scaling up, then all instances are restarted.

• If you’re scaling down, then all instances are restarted.