Database server (on-prem)

For on-prem, a Database Server is a database discovered through one of the associated database application targets or through APM solutions.

Synopsis

Database Server in the Supply Chain
Synopsis
Provides:
  • Response Time, Transactions, DBmem, Cache Hit Rate, and TransactionLog to end users

  • Connections to Application Components

Consumes: VM resources, including VCPU, VMem, and VStorage
Discovered through:
  • AppDynamics targets

  • Database Server targets

  • Dynatrace MySQL and SQL Server processes

  • NewRelic Infrastructure Integration (NRI): MySql, SQL Server, MongoDB, OracleDB

Monitored resources

Turbonomic monitors the following resources:

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

  • Database memory (DBMem)

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

  • Connection

    Connection is the measurement of database connections utilized by applications.

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

Actions

Turbonomic supports the following actions:

Resize

Resize the following resources:

  • Connections

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

  • Database memory (DBMem)

    Actions to resize database memory are driven by data on the Database Server, which is more accurate than data on the hosting VM. Turbonomic uses database memory and cache hit rate data to decide whether resize actions are necessary.

    A high cache hit rate value indicates efficiency. The optimal value is 100% for on-prem (self-hosted) Database Servers, and 90% for cloud Database Servers. When the cache hit rate reaches the optimal value, no action generates even if database memory utilization is high. If utilization is low, a resize down action generates.

    When the cache hit rate is less than the optimal value but database memory utilization remains low, no action generates. If utilization is high, a resize up action generates.

  • Transaction log

    Resize actions based on the transaction log resource depend on support for virtual storage in the underlying hypervisor technology.

    Currently, Turbonomic does not support resize actions for Oracle and Database Servers on the Hyper-V platform (due to the lack of API support for virtual storage).