Mission Control user guide

Mission Control’s main function is to conduct various activities (actions) on Optimizely Configured Commerce environments (instances). The information in Mission Control is laid out as follows:

• Customer – A space that holds your Configured Commerce instances. User access/tenancy within Mission Control is managed at this level for all instances within the given Customer. 
• Instance – A Configured Commerce environment. This does not refer to a specific website, but rather the environment as a whole (such as sandbox or production).  
• Action – An automated activity (deploys, syncs, and so on) that can be run against a given instance (or instances).  
• Instance Status – The current state of a given instance.  
  • Created – The instance is fully provisioned and functioning.  
  • Other statuses (like Pending) – The instance is in some level of incompleteness or non-functionality.  
• Action Status – The current state of a given action run.  
  • Submitted – The action was submitted by the user but has not yet begun processing. 
  • InProgress – The action is actively running. 
  • Completed – The action has completed successfully. 
  • Failed – The action has failed in some way, and the activity was not fully completed. 
  • Cancelled – The action was cancelled partway through the run, and the activity was not fully completed. 

Running an Action: Walkthrough

The main purpose of Mission Control is to run actions on instances. To help you understand the structure of Mission Control, this section describes the process of an action from login to completion.

1. Go to the Mission Control homepage and log in with your Opti ID credentials. When you log in, you see the Customers view with all the customers you have access to.

   

2. Click on a Customer to see the Customer Detail page, which displays all Configured Commerce instances for the customer.

   

3. Click on an Instance to see the Instance Detail page. This lets you run actions, view information, and adjust configuration options.

   

4. Click Actions to see all available actions for the instance. Clicking a specific action, such as Base Code Deploy, opens the Execute Action page. This lets you configure, schedule, and run actions. Each action has different configuration options, such as selecting a version to deploy or an instance to sync to.

   

5. Click Continue to run the action and open the Action Request view. This lets you monitor an action request and its related logs. Once the action is completed, any relevant output (such as a DB backup link) is also posted here.  

   

Pages

This section highlights the different actions you can do on each available page.

Customers

Search and filter through your customers.

Instances

Search and filter through your instances. You can filter instances by Product, Status, Environment, and Region.

Dashboard

Review notifications for your instances. You can filter by Type and Product. View details about the notification types.

Global History

Review action history for your instances. You can filter by Action and Status. Clicking on an action takes you to the Action Request view and related logs.

Customer Detail

View all instances assigned to a customer. You can also review action history for instances scoped to the customer in the History tab. 

Instance Detail

Run actions, view information, and adjust configuration options for an instance. This page contains several tabs:

• Detail – Contains information about the given instance such as infrastructure configuration, deployment info, and website details.

  

  You can expand each deployment to find more information about the deployment and its history.

• Integrations – Contains technical information about any integrations and services connected to the instance (such as the Payment Service or Commerce Search v3). Functionality for this area is still under development, and as such may provide incomplete information.

  

• History – Contains the action history for the given instance.

  

• Properties – Lets you update and review various infrastructure properties, such as build alert contact information.

  

• Notifications – Provides detailed notifications for the given instance.

  This is available for only Configured Commerce instances using the v2 build service. Upgrading to v2 is a simple, no-code process that provides additional performance and reliability benefits. See Build service v2 for information.