Instana

Prerequisites

• Instana release-242 or later

  Turbonomic version 8.8.3 (or later) requires release-242 or later to manage an on-prem or SaaS instance of Instana.

• An on-prem or SaaS instance of Instana

  This instance must be configured to monitor applications running in your environment.

  For an on-prem instance, you must also install BeeInstana. If BeeInstana is not installed, Turbonomic will return a NullPointerException and will not be able to collect metrics for Application Components and the underlying entities in the supply chain.

• Virtual machines and/or containers that are running applications managed by Instana

  For Turbonomic to discover applications through Instana, the applications must be running on virtual machines or containers in your environment. Also, these entities must be managed by Turbonomic hypervisor, public cloud, or container platform targets.

• A valid Instana API token

  This must be an API token created with the default permissions.

Adding an Instana Target

1. Click Settings > Target Configuration.

2. Click New Target > Applications and Databases.

3. Select Instana.

4. Configure the following settings:

   • Hostname or IP Address

     Specify the hostname or IP of the Instana server.

   • API Token

     Specify the Instana API token.

   • Collect Virtual Machine Metrics

     If you select this option, Turbonomic uses the virtual machine metrics that it collects from this target, instead of the metrics that can be collected from related infrastructure targets.

   • Collect Tag Information

     If you select this option, Turbonomic collects tags assigned to virtual machines that have been specified in the configuration.yaml file for Instana.

     The full directory is: <instana-agent-dir>/etc/instana/configuration.yaml.

     Instana tags do not use key:value pairs. Tags are defined in the Instana agent configuration files as:

      tags:
      - 'production'
      - 'app1'

     You can manually define a key:value pair by separating two strings with a colon. If you have not defined a key:value pair, the key is used as the value. For example:

      tags:
      - 'IamATag'
      - 'IamAKey:IamAValue' 

     In Turbonomic, this example displays as:

     IamATag IamATag
     
     IamAKey IamAValue

     You can use these tags in Turbonomic when you search for, filter, or group entities discovered from the target. To view the collected tags, set the scope to a particular entity and then check the Related Tag Information chart.

   • Validate Server Certificates

     If you select this option, Turbonomic verifies the target certificate and proxy, if in use.

   • Proxy Information

     Specify proxy information only if you connect through a proxy.

     • Proxy Host

       Specify the address of the proxy used for this target.

     • Proxy Port

       Specify the port to use with the proxy used for this target. By default, this is 8080.

     • Proxy Username

       Specify the username to use with the proxy.

     • Proxy Password

       Specify the password to use with the proxy.

     • Secure Proxy Connection

       Select this option if Turbonomic will connect to the proxy via HTTPS.

Entity Mapping

After validating your targets, Turbonomic updates the supply chain with the entities that it discovered. The following table describes the entity mapping between the target and Turbonomic.

Instana Permissions

Monitored Resources

Turbonomic monitors the following resources:

• Business Application

  • 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).

  • Transaction

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

  • Service Level Indicator (SLI)

    A service level indicator (SLI) is the defined quantitative measure of one characteristic of the level of service that is provided to a customer. Common examples of such indicators are error rate or response latency of a service.

    Note:

    Currently, SLI data is available in the Entity Information chart and Response Time chart.

• Business Transaction

  • 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).

  • Transaction

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

  • Service Level Indicator (SLI)

    A service level indicator (SLI) is the defined quantitative measure of one characteristic of the level of service that is provided to a customer. Common examples of such indicators are error rate or response latency of a service.

    Note:

    Currently, SLI data is available in the Entity Information chart and Response Time chart.

• Service

  • 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).

  • Transaction

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

  • Service Level Indicator (SLI)

    A service level indicator (SLI) is the defined quantitative measure of one characteristic of the level of service that is provided to a customer. Common examples of such indicators are error rate or response latency of a service.

    Note:

    Currently, SLI data is available in the Entity Information chart and Response Time chart.

• Application Component

  • Virtual CPU (VCPU)

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

  • Virtual Memory (VMem)

    Virtual Memory is the measurement of memory that is in use.

  • 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).

  • Remaining GC Capacity

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

    This commodity applies only to Java applications.

  • Heap

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

    This commodity applies only to Java applications.

• Database Server

  • Virtual CPU (VCPU)

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

    This commodity applies only to Oracle, MySQL, and SQL databases.

  • Virtual Memory (VMem)

    Virtual Memory is the measurement of memory that is in use.

    This commodity applies only to Oracle, MySQL, and SQL databases.

  • Database Memory (DBMem)

    Database memory (or DBMem) is the measurement of memory that is utilized by a Database Server.

    This commodity applies only to MySQL and SQL databases.

  • DB Cache Hit Rate

    DB cache hit rate is the measurement of Database Server accesses that result in cache hits, measured as a percentage of hits versus total attempts. A high cache hit rate indicates efficiency.

    This commodity applies only to Oracle, MySQL, and SQL databases.

  • 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).

  • Transaction

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

    This commodity applies only to Oracle databases.

  • Connection

    Connection is the measurement of database connections utilized by applications.

    This commodity applies only to Oracle databases.

• Container

  • Virtual Memory (VMem)

    Virtual Memory is the measurement of memory that is in use.

    This commodity applies only to Docker containers.

• Virtual Machine

  • Virtual CPU (VCPU)

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

  • Virtual Memory (VMem)

    Virtual Memory is the measurement of memory that is in use.

Actions

Turbonomic supports the following actions:

• Application Component

  • Resize Heap

    This action can only be executed outside Turbonomic.

• Database Server

  • Resize Database Memory (DBMem) - MySQL and SQL Server only

    This action can only be executed outside Turbonomic.

    Actions to resize database memory are driven by data on the Database Server, which is more accurate than data on the hosting VM.

  • Resize Connection Capacity - Oracle only

    This action can only be executed outside Turbonomic.

Turbonomic does not recommend actions for Instana Business Applications, Business Transactions, or Services. However, it considers resource utilization by these applications when recommending actions for the underlying virtual machines or containers. Turbonomic propagates this underlying information upward in the supply chain to show the impact of infrastructure risks on the Business Applications, Transactions, and Services.