Application map

Leaf entities

Leaf entities are child nodes with no further children. To find a leaf entity, traverse upward in the supply chain from a seed entity, such as a virtual machine, until you reach a node that doesn’t have any child nodes. The following diagram illustrates how this traversal is performed.

Creating application maps

You can create an application map from the Application Map Manager page or from a Search, Group, or Supply Chain page.

Creating application maps from the Application Map Manager page

1. Navigate to the Settings Page.

   

2. Choose Application Map.

   

3. Click Create application map and then choose the creation mode: Automatic or Manual.

   • Automatic

     Create a new application entity that is composed of tagged entities. For example, create a new business application that is composed of VMs with the Production tag.

     Turbonomic automatically adds selected entities to the proper map.

   • Manual

     Create a new application entity that is composed of a specific set of application entities and nodes.

     Manually creating the map individually allows for more flexibility.

4. Specify the required values to create the application map based on the creation mode you selected.

   Automatic

   1. Select the entity type for the seed entity that structures your application map.

   2. Specify a name prefix.

      Turbonomic automatically creates the names for the entities. You can specify an entity name prefix to help you easily identify the application entities that Turbonomic creates for you.

      The name cannot exceed 20 characters and can contain only alphanumeric or underscore (_) characters.

   3. Click the Virtual Machine + button to specify the underlying entities for your application map.

   4. Click the filter icon.
   5. Select a tag option that identifies the underlying entities.
   6. Click Save and apply, then click Save.
   7. Click Create application map.

   Manual

   1. Select the entity type for the seed entity that structures your application map.

   2. Specify the entity name.

      The name cannot exceed 20 characters and can contain only alphanumeric or underscore (_) characters.

   3. Select the underlying entity types.

   4. Enable or disable Direct Link.

      • If you select Direct Link, Turbonomic creates an application map based solely on your selected entities. This option is ideal if you require full control of your maps. For example, you might have a requirement to limit the scope of your performance monitoring to certain entities. If you do not select Direct Link, Turbonomic creates a context-based definition of the application map that you are creating and automatically updates that definition as the map evolves.

        When Direct Link is disabled, the underlying application entities and nodes that you specified act as "seed entities" for creating the definition. Turbonomic uses these seed entities to identify the highest entity in the supply chain and any other related entities ("leaf entities"), and then creates a new context-based definition. The result is an application map that closely matches your environment.

        For example, your initial intent might be to create a new Business Application entity composed of several Services (seed entities), so you can monitor performance at the Service level. However, you might not be aware of other entities that might impact performance, making it more time-consuming to identify and resolve performance issues outside of the selected scope. With Direct Link disabled, Turbonomic might discover Application Components and VMs (leaf entities) that back the Services, and then show them in the supply chain. The result is a complete representation of the Business Application that shows performance risks at each level of the discovered application stack. As the composition of the Business Application changes, Turbonomic automatically updates the definition so your supply chain view remains current.

        When Direct Link is enabled, Turbonomic creates a definition based solely on your selected entities. The system will not include other relevant entities in the map definition. This option is ideal if you require full control of your definitions. For example, you might have a requirement to limit the scope of your performance monitoring to certain entities.

5. Click Create application map.

Creating application maps from Search, Group, or Supply Chain pages

You can also create an application map from the Supply Chain page for an entity or by selecting one or more entities of the same type from a Group or Search page. This option is only available for manual application map creation. When you select one or more entities and click Create Application Map, Turbonomic pre-populates these underlying entities in your application map definition.

The type of underlying entity that you select determines the options for the seed entity that structures your application map. For example, if the underlying entity or entities you start with are Business Transactions, the only option for the seed entity is Business Application. If you start with a Service, the seed entity can be either a Business Transaction or a Business Application. For any other underlying entity types, you can choose from Business Application, Business Transaction, or Service for the seed entity.

The following image shows the Create Application Map button on a Search page for Database Servers. Clicking this button creates an application map for the selected server and populates the underlying entities.

rwlp_jaxrs2.0_atom.

The following image shows the Create Application Map button on a Supply Chain page for a Virtual Machine. Clicking this button creates an application map for the Virtual Machine and populates the underlying entities.

Managing application maps from the Options menu

When you navigate to Settings> Application Map and click the three-dot Options menu for any application map, you can choose from the following options.

• View Scope

  Scope into the custom Business Application, Business Transaction, or Service created by the application map definition to see the supply chain it represents.

• View Details

  See a brief summary of your application map definition, including:

  • Entity type

  • Application map state

  • Application map underlying entities creation criteria

  • Assigned users

• Edit Details

  Edit the application map name, underlying entities selection, and enable or disable the Direct Link option. This option is equivalent to clicking the Edit icon, which is advised when the definition is in a disconnected state.

• Assign User

  An admin can enforce role-based access control (RBAC) by assigning users with the Shared Observer role to specific application map definitions. Users with this role can view the application maps assigned to them. Admins can manage and view assigned application maps from the User Management page and can also edit the Shared Observer privileges.

• Delete

  Delete the application map definition from the application map manager and remove its created custom entity from the Turbonomic supply chain.

Application map states

You can view the state of an application map through the Application Manager view or by selecting View Details from the Options menu. The application map definition can be in one of three states:

• Connected

  The application map was created and is visible in the supply chain. You can access by selecting View Scope in the Options menu or from the search view.

• In Progress

  The application map is being created. It typically takes around 10 minutes for Turbonomic to create an application map.

• Disconnected

  The supply chain for the application map is detached or incomplete. This state occurs when the leaf entity (Business Application, Business Transaction, or Service) has no relationships to its underlying entities, or when the underlying entities are missing. In this case, you cannot access the View Scope option but you can review problem details through the View Details or Edit Details options. For more information, see Disconnected State Troubleshooting.

Troubleshooting

If you receive an error indicating that the feature has been disabled, an admin must enable the UDT probe in the YAML file. If you are not an admin or if you are a SaaS user, contact your Turbonomic representative to enable this feature.

1. Open an SSH terminal session to your Turbonomic instance.

   Log in with the System Administrator that you set up when you installed Turbonomic:

   • Username: turbo

   • Password: [your_private_password]

2. In the SSH session, open the YAML file for editing.

   /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml

3. To enable or disable currently configured probes, find the probes to edit and change the settings to true (enable) or false (disable).

   Search for UDT in the YAML file and set enabled: true.

4. Save and apply the changes.

   kubectl apply -f /opt/turbonomic/kubernetes/operator/deploy/crds/charts_v1alpha1_xl_cr.yaml

   Note:

   These changes might take up to two minutes to complete. Refresh your Turbonomic instance then attempt to create an application map.

Disconnected state troubleshooting

If your application map is in a Disconnected state, you are informed by a pop-up notification. You can then click the edit icon or select Edit Details from the Options menu to view more information. The following issues are common causes of disconnected state due to changes in your underlying entities:

• Unavailable Underlying Entities

  Preselected underlying entities are no longer available in your environment, for example, due to environment changes or target deletions.

  

• Groups Without Members

  Some groups that are defined as underlying entities might have no members.

  

• Definition by Regex Criteria

  No entities meet the defined regex criteria for the application map definition.