Application component

An Application Component is a software component, application code, or a unit of processing within a Service that consumes resources to enable it to perform its function for the Business Application. For example, Apache Tomcat is a Java Servlet container that hosts a range of Java applications on the web.

Turbonomic can recommend actions to adjust the amount of resources available to Application Components.

Synopsis

Application Component in the Supply Chain
Synopsis
Provides:

  • Response Time and Transactions to Services, Business Transactions, and Business Applications

  • Response Time, Transactions, Heap, Remaining GC Capacity, and Threads to end users
Consumes: Compute resources from nodes
Discovery: Turbonomic discovers the following:

  • Apache Tomcat

  • AppDynamics Nodes

  • Dynatrace Processes

  • NewRelic APM Application Instances

  • SNMP

  • WMI

  • Prometurbo or Data Ingestion Framework metrics for container platform environments

Monitored resources

Turbonomic monitors the following resources:

Note:

The exact resources that are monitored will differ based on application type. This list includes all of the resources that you may see.

  • Virtual CPU (vCPU)

    Virtual CPU is the measurement of CPU that is in use.

  • Virtual memory (vMem)

    Virtual memory (vMem) is the measurement of memory that is in use.

  • Transaction

    Transaction is a value that represents the per-second utilization of the transactions that are allocated to a given entity.

  • Heap

    Heap is the portion of a VM or container’s memory allocated to individual applications.

  • Response time

    Response time is the elapsed time between a request and the response to that request. Response time is typically measured in seconds (s) or milliseconds (ms).

  • Connection

    Connection is the measurement of database connections utilized by applications.

  • Remaining GC capacity

    Remaining GC capacity is the measurement of Application Component uptime that is not spent on garbage collection (GC).

  • Threads

    Threads is the measurement of thread capacity utilized by applications.

The charts for an Application Component show average and peak/low values over time. You can gauge performance against the given SLOs. By default, Turbonomic does not enable SLOs in the default policy for Application Components. It estimates SLOs based on monitored values, but does not use these values in its analysis.

Note:

In container platform environments, SLOs defined in a service policy override any SLOs set in the associated Application Components to prevent conflicts. In addition, the Response Time and Transaction charts for Application Components will show SLOs specified in the service policy. For more information, see this topic.

Actions

Turbonomic supports the following actions:

Resize

Resize the following resources to maintain performance:

  • Thread pool

    Turbonomic generates thread pool resize actions. These actions are recommend-only and can only be executed outside Turbonomic.

  • Connections

    Turbonomic uses connection data to generate memory resize actions for on-prem Database Servers.

  • Heap

    Turbonomic generates Heap resize actions if an Application Component provides Heap and Remaining GC Capacity, and the underlying VM or container provides VMem. These actions are recommend-only and can only be executed outside Turbonomic.

    Note:

    Remaining GC capacity is the measurement of Application Component uptime that is not spent on garbage collection (GC).

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.