From 0a795b005eacbf04581e14284ea9d8c56a2db265 Mon Sep 17 00:00:00 2001 From: Stephane Nicoll Date: Tue, 20 Feb 2018 13:29:09 +0100 Subject: [PATCH] Add missing documentation See gh-12129 --- .../src/main/asciidoc/production-ready-features.adoc | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc index 655735c1003..1aaffd7816a 100644 --- a/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc +++ b/spring-boot-project/spring-boot-docs/src/main/asciidoc/production-ready-features.adoc @@ -1563,13 +1563,15 @@ is required. A `CacheMetricsRegistrar` bean is made available to make that proce [[production-ready-metrics-jdbc]] ==== DataSource Metrics -Auto-configuration enables the instrumentation of all available ``DataSource`` objects -with a metric named `jdbc`. Data source instrumentation results in gauges representing the +Auto-configuration enables the instrumentation of all available DataSource` objects with a +metric named `jdbc`. Data source instrumentation results in gauges representing the currently active, maximum allowed, and minimum allowed connections in the pool. Each of 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. +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]]