​
Overview

An operation is performed and recorded for all changes made to resources, environments, and stacks. As operations are performed, operation logs are outputted and stored within Aptible. Operations are designed with reliability in mind - with minimal downtime and automatic rollbacks.

A collective record of operations is referred to as activity.

​
Type of Operations

​
Operation Logs

For all operations performed, Aptible collects operation logs. These logs are retained only for active resources.

​
Activity Dashboard

The Activity dashboard provides a real-time view of operations for active resources in the last seven days. Through the Activity page, you can:

  • View operations for resources you have access to
  • Search operations by resource name, operation type, and user
  • View operation logs for debugging purposes
Troubleshooting with our team? Link the Aptible Support team to the logs for the operation you are having trouble with.

​
Activity Reports

Activity Reports provide historical data of all operations in a given environment, including operations executed on resources that were later deleted. These reports are generated on a weekly basis for each environment, and they can be accessed for the duration of the environment’s existence. All Activity Reports for an Environment are accessible for the lifetime of the Environment.

​
Minimal downtime operations

To further mitigate the impact of failures, Aptible Operations are designed to be interruptible at any stage whenever possible.

In particular, when deploying a web application, Aptible performs Zero-Downtime Deployment. This ensures that if the Operation is interrupted at any time and for any reason, it still won’t take your application down.

When downtime is inevitable (such as when resizing a Database volume or redeploying a Database to a bigger instance), Aptible optimizes for minimal downtime.

For example, when redeploying a Database to another instance, Aptible must perform the following steps:

  • Shut down the old Database Container.
  • Unmount and then detach the Database volume from the instance the Database was originally scheduled on.
  • Attach then remount the Database volume on the instance the Database is being re-scheduled on.
  • Start the new Database Container.

When performing this Operation, Aptible will minimize downtime by ensuring that all preconditions are in place to start the new Database Container on the new instance before shutting down the old Database Container. In particular, Aptible will ensure the new instance is available and has pre-pulled the Docker image for your Database.

​
Operation Rollbacks

Aptible was designed with reliability in mind. To this extent, Aptible provides automatic rollbacks for failed operations. Users can also manually rollback an operation should they need to.

​
Automatic Rollbacks

All Aptible operations are designed to support automatic rollbacks in the event of a failure (with the exception of a handful of trivial operations with no side effects (such as launching Ephemeral SSH Sessions).

When a failure occurs, and an automatic rollback is initiated, a message will be displayed within the operation logs. The logs will indicate whether the rollback succeeded (i.e., everything was restored back to the way it was before the Operation) or failed (some changes could not be undone).

Some side-effects of deployments cannot be rolled back by Aptible. In particular, database migrations performed in before_release commands cannot be rolled back (unless you design your migrations to roll back on failure, of course!). We strongly recommend designing your database migrations so that they are backwards compatible across at least one release. This is a very good idea in general (not just on Aptible), and a best practice for zero-downtime deployments (see Concurrent Releases for more information).

​
Manual Rollbacks

A rollback can be manually initiated within the Aptible CLI by using the aptible operation:cancel command.

​
FAQ