|
|
@ -1563,13 +1563,15 @@ is required. A `CacheMetricsRegistrar` bean is made available to make that proce
|
|
|
|
|
|
|
|
|
|
|
|
[[production-ready-metrics-jdbc]]
|
|
|
|
[[production-ready-metrics-jdbc]]
|
|
|
|
==== DataSource Metrics
|
|
|
|
==== DataSource Metrics
|
|
|
|
Auto-configuration enables the instrumentation of all available ``DataSource`` objects
|
|
|
|
Auto-configuration enables the instrumentation of all available DataSource` objects with a
|
|
|
|
with a metric named `jdbc`. Data source instrumentation results in gauges representing the
|
|
|
|
metric named `jdbc`. Data source instrumentation results in gauges representing the
|
|
|
|
currently active, maximum allowed, and minimum allowed connections in the pool. Each of
|
|
|
|
currently active, maximum allowed, and minimum allowed connections in the pool. Each of
|
|
|
|
these gauges has a name that is prefixed by `jdbc`.
|
|
|
|
these gauges has a name that is prefixed by `jdbc`.
|
|
|
|
|
|
|
|
|
|
|
|
Metrics are also tagged by the name of the `DataSource` computed based on the bean name.
|
|
|
|
Metrics are also tagged by the name of the `DataSource` computed based on the bean name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Also, Hikari-specific metrics are exposed with a `hikaricp` prefix. Each metric is tagged
|
|
|
|
|
|
|
|
by the name of the Pool (can be controlled with `spring.datasource.name`).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
[[production-ready-metrics-rabbitmq]]
|
|
|
|
[[production-ready-metrics-rabbitmq]]
|
|
|
|