Target configuration

Edit online

A target is an integration partner technology that provides resources or workload management services in your virtual environment. For example, Amazon Web Services (AWS) and VMware vCenter Server are supported targets.

Connect to your infrastructure through targets to see how Turbonomic can optimize performance and costs for your workloads. Turbonomic supports connecting to multiple types of infrastructure, including public clouds, container platforms, applications, databases, and more.

Target configuration specifies the credentials that Turbonomic uses to connect to targets. Turbonomic connects through the management protocol that it exposes, such as REST API, SMI-S, XML, or some other management transport. It uses this connection to discover resources, monitor resource utilization, and recommend actions.

After a target is added, Turbonomic discovers and processes resources and utilization metrics every 10 minutes. This mechanism is needed to generate resource optimization actions in response to continuous changes in resources and utilization over time. You can connect more targets any time.

Note:

When a specific release or version of an integration partner technology reaches end-of-life (EOL) or its end-of-support date, Turbonomic no longer provides support for that version. Turbonomic follows integration partners' official EOL timeline for version support. Targeting a non-supported version, or one that is no longer supported by the integration partner, is at your own risk.

Supported targets

Turbonomic supports the following targets.

Target category

Targets

Applications and databases

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

  • Cisco AppDynamics 4.1+

  • Datadog

  • Dynatrace 1.1+

  • IBM WebSphere Application Server 8.5+

  • Instana release 242 or later

  • JVM 6.0+

  • SQL Server 2012, 2014, 2016, 2017, 2019, or 2022

  • MySQL 8.0

  • New Relic

  • Oracle 19c or 21c

  • Oracle WebLogic 12c

Container platform

  • Kubernetes 1.27 up to the latest supported GA version, including (but not limited to) Amazon Elastic Kubernetes Service (EKS), Azure Kubernetes Service (AKS), Google Kubernetes Engine (GKE), IBM Cloud Kubernetes Service (IKS), Oracle Kubernetes Engine (OKE), and Rancher

  • Red Hat supported GA versions of Red Hat OpenShift 4.x, including (but not limited to) Red Hat OpenShift Kubernetes Service (ROKS), Red Hat OpenShift on AWS (ROSA), Red Hat OpenShift on Azure (ARO), Red Hat OpenShift on Google, Red Hat OpenShift on VMware, and Red Hat OpenShift on BareMetal

    Discovering and monitoring Red Hat OpenShift Virtualization resources is supported and available through a Red Hat OpenShift target configuration.

Data Analytics, and AI

  • Databricks Workspace

Fabric and network

  • Cisco UCS Manager 3.1+

  • HPE OneView 3.00.04

Guest OS processes

  • WMI: Windows 7, 8, 8.1, 10, 2008 R2, 2012, 2012 R2, 2016, or 2019

Hyperconverged

  • Nutanix

  • VMware vSAN

Hypervisors

  • IBM PowerVM

    • HMC 11: Power9, Power10, or Power11

    • HMC 10: Power8, Power9, or Power10

    • HMC 9: Power8 or Power9 only; Power7 LPARs and Systems are ignored.

  • Microsoft Hyper-V 2012 R2, 2016, 2019, 2022, or 2025

    Note:

    Turbonomic supports Azure Local managed with Hyper-V.

  • vCenter 8.0 or vSphere 9.0 (delivered through VMware Cloud Foundation 9.0 and vSphere Foundation 9.0)
    Note: vCenter 7.0 reached End of Service (EoS) on October 2, 2025 and is no longer supported in Turbonomic as vCenter targets and for deploying the Turbonomic platform. Upgrade to vCenter 8.0 or vSphere 9.0 to avoid functionality loss and compatibility issues.
  • Red Hat OpenStack Platform 18

Infrastructure as Code (IaC)

  • Azure DevOps

  • GitHub

  • GitLab

  • Community Edition (CE) Terraform

  • Terraform

    Use this target to connect to the following platforms:

    • HashiCorp Cloud Platform (HCP) Terraform

    • Terraform Enterprise (TFE)

  • Terraform Provider

IT management

  • Flexera

    • Flexera One SaaS

    • FlexNet Manager Suite 2023 R2 or above

  • IBM Apptio

  • ServiceNow

    Certified for ServiceNow versions:

    • Australia

    • Zurich

    • Xanadu

    • Yokohama

Observability

  • Prometheus

Orchestrator

  • Action Script

Private cloud

  • VMM for Microsoft System Center 2012 R2, System Center 2016, System Center 2019, System Center 2022, or System Center 2025

    Note:

    Turbonomic supports Azure Local managed with VMM.

Public cloud

  • Amazon Web Services (AWS)

  • AWS Billing

  • Azure Service Principal

  • Azure Billing

  • Google Cloud

  • Google Cloud Billing

  • IBM Cloud

  • Oracle Cloud Infrastructure (OCI)

Storage

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

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

  • IBM SAN Volume Controller 8.7.0+

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

  • Pure Storage F-series and M-series arrays running Purity 5.3.6 and 6.4.4 (Pure API 1.6)

Virtual Desktop Infrastructure

  • Horizon 7.0 or higher

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, contact IBM 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, contact IBM Support.

Enabling targets

A probe is a platform component that enables a Turbonomic target to connect to your infrastructure environment and discover entities, such as virtual machines and databases. The probe loads the entities into the Turbonomic supply chain and runs actions to optimize these entities. After you enable probes, add the corresponding targets on the Target configuration page in the user interface to set up the connection.

Depending on your installation method, Turbonomic may enable probes by default. Each probe uses resources in your Turbonomic installation. If probes are not needed, consider disabling them. If there are disabled probes that you need, enable them to put them into service.

To enable or disable probes, edit the cr.yaml file. You can add new probes, change the values of the enabled: properties, and apply changes to reload the platform components.

For more information, see (Optional) Enabling and disabling probe components.

Duplicate targets

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

If you configured duplicate targets, 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.