Actions by entity type
Turbonomic generates actions based on how entity types use or provide resources, and what each entity type supports.
The following tables show the actions that each entity type supports:
Application entity types
Entity type | Supported actions |
---|---|
Business application |
None Turbonomic does not recommend actions for a Business Application, but it does recommend actions for the underlying Application Components and infrastructure. The Pending Actions chart for a Business Application lists these actions, thus providing visibility into the risks that have a direct impact on the Business Application's performance. |
Business transaction |
None Turbonomic does not recommend actions for a Business Transaction, but it does recommend actions for the underlying Application Components and infrastructure. The Pending Actions chart for a Business Transaction lists these actions, thus providing visibility into the risks that have a direct impact on the Business Transaction's performance. |
Service |
|
Application component |
Resize Resize the following resources to maintain performance:
The resources that Turbonomic can resize depend on the processes that it discovers from your Applications and Databases targets. Refer to the topic for a specific target to see a list of resources that can be resized. |
Container platform entity types
Entity type | Supported actions |
---|---|
Service |
Scale (through workload controllers) Turbonomic recommends actions to scale the replicas that back the container platform services. Set the scope to the associated Workload Controller to view and execute the actions. For details, see Workload Controller Scale Actions. |
Container |
Resize Turbonomic generates container resize actions for Bare Pods where the workload has no controller. |
Container spec |
Resize (through workload controllers) A container spec retains the historical utilization data of ephemeral containers. Turbonomic uses this data to make resize decisions that assure optimal utilization of resources. By default, all replicas of the same container for the same workload type resize consistently. For details, see Workload Controller Resize Actions. |
Namespace |
Resize quota Turbonomic treats quotas defined in a namespace as constraints when making resize decisions. If existing actions would exceed the namespace quotas, Turbonomic recommends actions to resize up the affected namespace quota. Note that Turbonomic does not recommend actions to resize down a namespace quota. Such an action reduces the capacity that is already allocated to an application. The decision to resize down a namespace quota should include the application owner. For details, see Namespace Actions. |
Workload controller |
|
Container pod |
|
Container platform cluster |
None Turbonomic does not recommend actions for a container platform cluster. Instead, it recommends actions for the containers, pods, nodes (VMs), and volumes in the cluster. Turbonomic shows all of these actions when you scope to a container platform cluster and view the Pending Actions chart. |
Container platform node (VM) |
A node (cloud or on-prem) is represented as a Virtual Machine entity in the supply chain. Note:
For nodes in the public cloud, Turbonomic reports the cost savings or investments attached to these actions. For details, see Node Actions. |
Cloud infrastructure entity types
Entity Type | Supported Actions |
---|---|
Virtual machine (cloud) | For details about cloud VM actions, see the following topics: |
Virtual machine spec |
|
App component spec |
None Turbonomic does not recommend actions for App Component Specs, but it does recommend actions for the underlying Virtual Machine Specs. For details, see Virtual Machine Spec Actions. |
Database server (cloud) |
|
Database (cloud) |
|
Data warehouse |
Suspend Suspend a Redshift provisioned cluster to reduce compute costs. For details, see Suspend actions for Redshift provisioned clusters. |
Document collection |
Scale Scale Request Units (RUs) to optimize performance and costs. For details, see Document Collection Actions. |
Volume (cloud) |
For details, see Cloud Volume Actions. |
Zone |
None Turbonomic does not recommend actions for a cloud zone. |
Region |
None Turbonomic does not recommend actions for a cloud region. |
On-prem infrastructure entity types
Entity type | Supported actions |
---|---|
Virtual machine (on-prem) |
For details, see On-prem VM Actions. |
Volume (on-prem) |
|
Database server (on-prem) |
Resize Resize the following resources:
|
Virtual datacenter |
None Turbonomic does not recommend actions for a virtual datacenter. Instead, it recommends actions for the entities that provide resources to the virtual datacenter. |
Business user |
Move Move a business user between desktop pools to address:
Note:
To support moves, you must configure placement policies that merge similarly configured desktop pools. For details, see Desktop Pool Placement Policies. |
Desktop pool |
None Turbonomic does not recommend actions for a desktop pool. It recommends actions for the business users running active sessions in the pool. |
View pod |
None Turbonomic does not recommend actions for a view pod. Instead, it recommends actions for the business users that are running active sessions. |
Host |
For details, see Host Actions. |
Chassis |
None Turbonomic does not recommend actions for a chassis. |
Datacenter |
None Turbonomic does not recommend actions for a datacenter. Instead, it recommends actions for the entities running in the datacenter. |
Storage |
For details, see Storage Actions. |
Logical pool |
|
Disk array |
|
Storage controller |
Provision For high utilization of the storage controller’s CPU, provision a new storage controller, and then move disk arrays to it. |
IO module |
Suspend For low utilization of net resources, move VMs to another host that provides compatible network connectivity and suspend this IO Module. |
Switch |
Resize Resize PortChannel for a switch to increase bandwidth. |