What’s new

Turbonomic is powered by a robust architecture that enables the core platform to scale with large application and infrastructure environments in a single-instance deployment. This eliminates complexity and provides scale-on-demand capabilities, while continuing to assure application performance and health.

Note:

Frequent changes to the product or third-party targets require that some features are updated, deprecated, removed, or no longer supported. For more information about these features, see Feature updates and notices.

Version 8.18.1

  • Expanded Azure VM instance support: This release introduces support for additional Azure VM instance series across multiple families.

    Instance family Instance series
    D Dadsv6, Daldsv6, Dalsv6, Dasv6, Ddsv6, Dldsv6, Dlsv6, Dpdsv6, Dpldsv6, Dplsv6, Dpsv6, Dsv6
    DC DCadsv6, DCasv6
    E Eadsv6, Easv6, Edsv6, Epdsv6, Epsv6, Esv6
    EC ECadsv6, ECasv6
    F Falsv6, Famsv6, Fasv6
    FX FXmdsv2, FXmsv2
    L Laosv4, Lasv4, Lsv4
    M Mbsv3, Mbdsv3, Mdsv3-MM, Msv2-MM, Msv3-MM

    For the complete list of supported instance series, see Supported Azure VM instance types.

  • VM move actions across vCenter DVPGs: Turbonomic can now execute VM move actions across Distributed Virtual Port Groups (DVPGs) when the DVPGs share the same name within the same vCenter target. In these cases, a merge policy is no longer required.

  • Enhanced discovery of hosts and VMs from APM targets: You now have greater control over how Turbonomic discovers virtual machines and hosts for the following APM targets, helping prevent duplicate entities:

    • Cisco AppDynamics
    • Dynatrace
    • Instana
    • New Relic

    New target configuration properties include:

    • Display discovered virtual machines: When enabled, Turbonomic displays virtual machines that are discovered exclusively through the APM target, along with those discovered through related infrastructure targets.
    • Display discovered hosts: When enabled, Turbonomic displays hosts that are discovered exclusively through the APM target. Hosts that are also discovered through infrastructure targets are merged into a single host entity.

    As a recommendation, consider enabling these settings when your environment has an APM target, but no vCenter target.

Version 8.18.0

  • Application performance management

    • Datadog response time metrics: Response time data is now available for business applications, services, and transactions discovered through Datadog targets. To enable data discovery and accurate metric aggregation, configure your primary tags in the Datadog APM settings. These tags, such as app-name, allow trace metrics to be grouped correctly by agent-level attributes.

  • Container platform resource management

    • Action center view for container actions: You can now view the most effective, non-disruptive actions that you can take to enhance performance and improve reliability for your containerized workloads. For more information, see Top actions (Containers).

    • Integration with IBM Kubecost Free and OpenCost (public preview): Turbonomic now seamlessly integrates with Kubecost Free and OpenCost to help you gain visibility into the financial impact of Kubernetes resource optimizations. In this release, the integration allows you to see potential savings and investments associated with workload controller resize actions, empowering cost-aware decisions directly in the platform. For more information, see Configuring a cost source for Kubernetes and Red Hat OpenShift.

    • One-click and automated updates for Kubeturbo and Prometurbo: You can now update the Kubeturbo and Prometurbo agents deployed to Kubernetes or Red Hat OpenShift clusters with a single click in the Turbonomic user interface. For full automation, script-based updates are available via the API. For more information, see Updating the Kubeturbo version through the Turbonomic user interface and Updating the Prometurbo version through the Turbonomic user interface.

    • CPU and memory resize up actions for workload controllers in Red Hat OpenShift Virtualization: Turbonomic now supports CPU and memory resize up actions for workload controllers (virtual machines) in Red Hat OpenShift Virtualization. With this support, the associated container specs can be resized up or down to assure optimal resource utilization.

  • Cloud resource management

    • Parking actions for Azure SQL Managed Instances: This release introduces parking actions for Azure SQL Managed Instances. Turbonomic adds SQL Managed Instances to the Workloads tab in the Parking page, enabling you to park them on demand or according to a schedule, or add them to a workload set. You can also park these instances using parking policies. For more information, see Parkable database servers.

      To enable parking for SQL Managed Instances, add the following permissions to the Azure service principal for Turbonomic.

      • Microsoft.Sql/managedInstances/distributedAvailabilityGroups/read
      • Microsoft.Sql/managedInstances/start/action
      • Microsoft.Sql/managedInstances/stop/action
      • Microsoft.Sql/locations/instanceFailoverGroups/read
      • Microsoft.Sql/locations/startManagedInstanceAzureAsyncOperation/read
      • Microsoft.Sql/locations/startManagedInstanceOperationResults/read
      • Microsoft.Sql/locations/stopManagedInstanceAzureAsyncOperation/read
      • Microsoft.Sql/locations/stopManagedInstanceOperationResults/read
    • Discovery and parking of Azure Kubernetes Service (AKS) clusters: Turbonomic now discovers AKS clusters from your Azure service principal targets and presents them as container platform entities in the supply chain. To view detailed information for a specific AKS cluster, scope to the corresponding container platform entity (for example, from the Search page or from the supply chain). For more information, see Container platform cluster (AKS cluster).

      Turbonomic adds AKS clusters to the Workloads tab in the Parking page, enabling you to park them on demand or according to a schedule, or add them to a workload set. You can also park these clusters using parking policies. For more information, see Parkable container platform clusters.

      To enable parking for AKS clusters, add the following permissions to the Azure service principal for Turbonomic.

      • Microsoft.ContainerService/managedClusters/start/action
      • Microsoft.ContainerService/managedClusters/stop/action
    • Discovery of Azure zones: Turbonomic now supports discovery of Azure zones and scoping of entities to these zones. For more information, see Azure regions.

    • Parking actions for Google Cloud managed instance groups (MIGs): This release introduces parking actions for Google Cloud MIGs. Turbonomic adds MIGs to the Workloads tab in the Parking page, enabling you to park them on demand or according to a schedule, or add them to a workload set. You can also park MIGs using parking policies. For more information, see Parkable virtual machine specs.

      To enable parking for MIGs, add the following permissions to the Google Cloud custom role assigned to the Turbonomic service account:

      • compute.autoscalers.get
      • compute.autoscalers.update
      • compute.instanceGroupManagers.get
      • compute.instanceGroupManagers.update
    • Improved discovery and stitching of Red Hat OpenShift nodes on Google Cloud: Turbonomic now offers more reliable discovery and stitching of Red Hat OpenShift nodes running on Google Cloud. When expected identifiers are missing, Turbonomic leverages additional metadata to ensure node states are accurately represented in the UI.

      Supported identifiers for stitching now include:
      • InstanceId
      • providerId
      • nodeId annotation
      • resourceId
    • Maximum duration for pausing parking schedules: Administrators, Site administrators, and Parking administrators can now configure the maximum duration for pausing parking schedules to prevent non-administrators from pausing schedules beyond the configured duration. For more information, see Pausing a parking schedule.

    • Currency filter in Realized savings and Realized investments charts: A new Currency filter in the Realized savings and Realized investments charts allows you to view data by a specific currency. This filter is especially useful when billing data from your cloud providers is in multiple currencies. By default, the charts show the currency that you set in Settings > Billing and costs.

    • Connected VM state filter for cloud volumes: When you search for volumes in the Search page or create volume groups in the Groups page, you can now use the Connected VM state filter to find cloud volumes based on the state of their attached VMs. For example, this filter can help identify volumes that are attached to idle or parked VMs, making them safer to scale.

  • On-prem resource management

    • IBM SAN Volume Controller (SVC) target: Turbonomic now supports IBM SVC as a storage target. IBM SVC is an enterprise-class storage virtualization solution that enables centralized management of heterogeneous storage resources across your IT infrastructure. For more information, see IBM SAN Volume Controller (SVC) target.

    • Control discovery of storage entities for Nutanix and vCenter targets: You can now control how Turbonomic discovers storage entities when connecting to Nutanix and vCenter targets, helping to prevent duplicate entities. New target configuration properties include:

      • Merge storage entities: Available for both Nutanix and vCenter targets. When enabled on both, Turbonomic merges storage entities discovered from Nutanix with those discovered from vCenter (through Nutanix), creating a unified set of storage entities.
      • Storage only mode: Available for Nutanix targets. This property prevents Turbonomic from discovering VMs, hosts, and clusters from non-Nutanix targets. Use this setting to when Nutanix is your primary infrastructure source to avoid duplicate entities.

      These properties are configurable from the Advanced configuration page when creating or editing each applicable target. For more information, see Nutanix and vCenter server.

    • Virtual machine migration plan: You can now configure a Virtual machine migration plan to simulate the migration of on-prem virtual machines between vCenter and Nutanix targets or between targets of the same type. This plan assesses whether additional host or storage resources are required to support the migration and identifies opportunities to optimize the deployment. For more information, see Migrate virtual machines plan.

    • Migrate to on-prem plan: You can now configure a Migrate to on-prem plan to simulate the migration of cloud-based virtual machines to on-prem infrastructure. This plan optimizes performance by selecting the most suitable on-prem resources for hosting your virtual machines and their associated volumes. For more information, see Migrate to on-prem plan.

    • Carbon footprint and energy usage data for on-prem entities: This release introduces the following enhancements:

      • The Carbon Footprint and Energy charts for on-prem entities have been enhanced to include usage data aggregation for more accurate tracking, a new bar chart visualization for easier analysis of usage trends, and a 'Group by' option to visualize chart data by groups. With these improvements, you can better understand your Carbon footprint and energy usage, quickly identify high-impact areas, and make informed decisions to optimize your on-prem resources.

      • Optimize on-prem plans now include carbon and energy impact in the plan summary, empowering you to make informed decisions that drive both performance and sustainability.

  • Platform management

    • Support for the AWS AP (Mumbai) and AWS AP (Singapore) regions: Turbonomic SaaS instances can now be deployed to the AWS AP (Mumbai) and AWS AP (Singapore) regions. If you require your SaaS instance to run in either region, contact your Turbonomic representative to initiate the deployment process.

      When your instance is running and ready to use, you can set up an IAM role that uses the credentials for the AWS AP (Mumbai) or AWS AP (Singapore) region and then specify that IAM role when you add an AWS target. For more information, see Setting up an AWS IAM role for SaaS deployments.