New to Observability? Let's fix that! New to Observability? Let's fix that right away!
Instrumentation/Supported Frameworks

Hikari CP Instrumentation #

As part of the JDBC instrumentation, Kamon can automatically gather performance metrics out of Hikari connection pools and use the pool information when creating Spans from Statements execution.

Metrics #

All Hikari connection pools will get the following metrics:


Tags included by default:
  • jdbc.pool.vendor: Name of the connection pool vendor.
  • jdbc.pool.name: Name of the connection pool for which the metric is being tracked.
  • db.vendor: Name of the JDBC driver vendor.

Tags included by default:
  • jdbc.pool.vendor: Name of the connection pool vendor.
  • jdbc.pool.name: Name of the connection pool for which the metric is being tracked.
  • db.vendor: Name of the JDBC driver vendor.

Tags included by default:
  • jdbc.pool.vendor: Name of the connection pool vendor.
  • jdbc.pool.name: Name of the connection pool for which the metric is being tracked.
  • db.vendor: Name of the JDBC driver vendor.

Tags included by default:
  • jdbc.pool.vendor: Name of the connection pool vendor.
  • jdbc.pool.name: Name of the connection pool for which the metric is being tracked.
  • db.vendor: Name of the JDBC driver vendor.

Manual Installation #

In case you are not using the Kamon Bundle, add the dependency below to your build:


libraryDependencies += "io.kamon" %% "kamon-jdbc" % "2.5.1"



    <dependency>
      <groupId>io.kamon</groupId>
      <artifactId>kamon-jdbc_2.13</artifactId>
      <version>2.5.1</version>
    </dependency>


implementation 'io.kamon:kamon-jdbc_2.13:2.5.1'

You must start your application with the instrumentation agent for this module to work properly.

On this article
Not sure where to analyze your Telemetry data?
Create alerts, analyze metrics, and find slow & failed traces in Kamon APM
Kamon APM Heatmap Try Kamon APM
Start with a Free account - Learn more