Changing ownership of a test

Last updated: Wed Feb 01 03:54:11 GMT 2017

When a test is created, the test is assigned to the Account Group in which the user is currently working.  If the Account Group of the test needs to be changed after creation, ownership of the test can be changed to a different Account Group, subject to certain restrictions.

The target Account Group need not be an Account Group in the same ThousandEyes organization. If a user is a member of multiple organizations, then the user can move a test from one organization's Account Group to an Account Group in another organization to which the user belongs, subject to the restrictions stated below.

In addition to providing steps to change ownership, the information below describes the way existing data is handled, and the effects of the change on other functions in the ThousandEyes platform such as alerting and monthly usage caps.

Requirements and restrictions

To perform a change of ownership, the following requirements exist:

  • The user must have the Edit Tests in Account Group permission in the source Account Group.
  • If the test to be moved is assigned to one or more Cloud Agents that are not visible in the target organization, then the Agents are replaced according to an algorithm which finds the best substitute if possible, or removes the Cloud Agent from the test.  See the Agent Replacement section below.
  • If the test to be moved has an Enterprise Agent as its target, then the Enterprise Agent must meet one of the following criteria, or the change of ownership will fail:
    1. The Enterprise Agent must already be shared from source Account Group to target Account Group or from target Account Group to source Account Group.
    2. The user moving the test must have a role in the target Account Group with the Edit Agents in this Account Group permission.  The Enterprise Agent will be automatically shared with the target Account Group.
  • If the test to be moved is assigned to one or more Enterprise Agents, then the Enterprise Agent(s) must meet one of the following criteria, or the the change of ownership will proceed but the Enterprise Agents will be removed from the test:
    1. The Enterprise Agent must already be shared from source Account Group to target Account Group or from target Account Group to source Account Group.
    2. The user moving the test must have a role in the target Account Group with the Edit Agents in this Account Group permission.  The user will be prompted as to whether to share the needed Enterprise Agent(s) to the target Account Group.
  • If the test to be moved is a Routing/BGP test, or has included Network measurements with the Collect BGP data option selected, any BGP private peer will be removed from the test configuration. BGP private peers cannot be shared across Account Groups.
  • When a test assigned to one or more Cloud Agents or a Routing/BGP test is moved to a new organization, the cost in Cloud Units to run the test will be assumed by the new organization, starting from the date of ownership change.  For organizations that have a per-month cap on Cloud Units, a check is performed during the ownership change process.  If the organization's projected usage to the end of the monthly billing cycle would exceed the cap by assuming ownership of the test, the ownership change will be blocked.  In order to make the change of ownership, the test configuration will require modification to consume fewer Cloud Units.  Review the test configuration with the ThousandEyes Pricing Calculator, and consult the Knowledge Base article How Cloud Unit consumption works.
 

Changing ownership

To change a test's Account Group, click the More Actions icon in the test's row of the Settings > Tests page and click the Transfer Ownership option:
 

User-added image
 

A dialogue appears, prompting for the target Account Group:
 

User-added image


Select the target Account Group in the same or another organization. In the example below, the target Account Group is "Testing" in the "ThousandEyes Sandbox" organization:
 

User-added image


Informational messages may be displayed, indicating what changes will be made in order to change the Account Group.
You can choose whether to keep a Live Share copy of the test in the source Account Group via a checkbox, per the image below.
 

User-added image
 

If the change is successful, the dialogue indicates that the test has been moved:
 

User-added image
 

Effects of changing ownership

In addition to the test appearing under the new Account Group, some modifications to the test configuration may occur.
 

Automatic Sharing

The test is automatically shared from the target Account Group to the source Account Group.  If not needed, the shared test can be removed from the source Account Group using either source or target Account Group context, and navigating to the Settings > Tests page.  Expand the test's row and uncheck the box with the name of the source Account Group. In the example below, the source Account Group is "Thousandeyes_dev":

User-added image


Alert Rules

Alert Rules assigned to the original test remain assigned to the shared test in the source Account Group.  If Alert Rules are needed for the test in the target Account Group, they must be created in the target Account Group and assigned to the test.
 

Agent Replacement

When the source organization does not have access to all of the Cloud Agents assigned to a test being reassigned ownership, the ThousandEyes application attempts to replace Agents which are not available in the target organization with new Agents using the following rules, in order:

  1. Replace an Agent with an Agent in the same metropolitan area.  For example, replace the "New York 2" Cloud Agent with "New York".
  2. Replace an Agent with an Agent in the same geographic region. For example, replace "San Francisco" with "Sacramento" (same state).
  3. Replace an Agent with an Agent in the same country, up to 1000 kilometers from the original Agent location.  For example, replace "San Francisco" with "Las Vegas" (same country, within 1000 kilometers).

If none of these criteria can be met, the Cloud Agent is removed.