Target Configuration

A target is a service that performs management in your virtual environment. Turbonomic uses targets to monitor workload and to execute actions in your environment. Target Configuration specifies the ports Turbonomic uses to connect with these services. You must install Turbonomic on a network that has access to the specific services you want to set up as targets.

For each target, Turbonomic communicates with the service via the management protocol that it exposes — The REST API, SMI-S, XML, or some other management transport. Turbonomic uses this communication to discover the managed entities, monitor resource utilization, and execute actions.


Turbonomic does not support duplicate instances of the same target. When configuring targets, you must not configure two or more targets to the same address in your environment. For example, you must not configure two different targets to the same AWS account, nor two targets to the same vCenter Server instance.

If you do configure duplicate targets, then actions can fail to execute with an error that begins: Analysis Exception occurred...

To resolve this issue, identify the duplicate targets, and delete them until you have only one target for each address.

You can assign instances of the following technologies as Turbonomic targets:

  • Applications and Databases

    • Apache Tomcat 7.x, 8.x, and 8.5.x

    • AppDynamics 4.1+

    • AppInsights

    • Dynatrace 1.1+

    • IBM WebSphere Application Server 8.5+

    • Instana, release-209 or later

    • JBoss Application Server 6.3+

    • JVM 6.0+

    • Microsoft SQL Server 2012, 2014, 2016, 2017, and 2019

    • MySQL 5.6.x and 5.7.x

    • NewRelic

    • Oracle 11g R2, 12c, 18c, and 19c

    • Oracle WebLogic 12c

  • Cloud Native

    • Kubernetes, including any compliant k8s distribution (Rancher, Tanzu, open source, etc.)

    • Cloud-hosted k8s services (AKS, EKS, GKE, IBM, Cisco IKS, ROKS, ROSA, etc.)

    • OpenShift 3.11 and higher (OCP 4.x)

  • Fabric and Network

    • Cisco UCS Manager 3.1+

    • HPE OneView 3.00.04

  • Guest OS Processes

    • SNMP

    • WMI: Windows versions 8 / 8.1, 10, 2008 R2, 2012 / 2012 R2, 2016, 2019 and 7

  • Hyperconverged

    • Cisco HyperFlex 3.5

    • Nutanix Community Edition

    • VMware vSAN

  • Hypervisors

    • Microsoft Hyper-V 2008 R2, Hyper-V 2012/2012 R2, Hyper-V 2016, Hyper-V 2019

    • VMware vCenter 6.0, 6.5, 6.7, and 7.0+

  • Orchestrator

    • Action Script

    • Flexera One
    • ServiceNow

  • Private Cloud

    • Microsoft System Center 2012/2012 R2 Virtual Machine Manager and System Center 2016 Virtual Machine Manager

  • Public Cloud

    • Amazon AWS

    • Amazon AWS Billing

    • Google Cloud Platform (GCP)

    • Google Cloud Platform (GCP) Billing

    • Microsoft Azure Service Principal

    • Microsoft Azure Billing

    • Microsoft Enterprise Agreement

  • Storage

    • EMC ScaleIO 2.x and 3.x

    • EMC VMAX using SMI-S 8.1+

    • EMC VPLEX Local Architecture with 1:1 mapping of virtual volumes and LUNs

    • EMC XtremIO XMS 4.0+

    • HPE 3PAR InForm OS 3.2.2+, 3PAR SMI-S, 3PAR WSAPI

    • IBM FlashSystem running on Spectrum Virtualize or later ( or later recommended)

    • NetApp Cluster Mode using ONTAP 8.0+ (excluding AFF and SolidFire)

    • Pure Storage F-series and M-series arrays

  • Virtual Desktop Infrastructure

    • VMware Horizon

Transport Layer Security Requirements

Turbonomic requires Transport Layer Security (TLS) version 1.2 to establish secure communications with targets. Most targets should have TLS 1.2 enabled. However, some targets might not have TLS enabled, or they might have enabled an earlier version. In that case, you will see handshake errors when Turbonomic tries to connect with the target service. When you go to the Target Configuration view, you will see a Validation Failed status for such targets.

If target validation fails because of TLS support, you might see validation errors with the following strings:

  • No appropriate protocol

    To correct this error, ensure that you have enabled the latest version of TLS that your target technology supports. If this does not resolve the issue, please contact IBM Technical Support.

  • Certificates do not conform to algorithm constraints

    To correct this error, refer to the documentation for your target technology for instructions to generate a certification key with a length of 2048 or greater on your target server. If this does not resolve the issue, please contact IBM Technical Support.