You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Whether or not datasource metrics are published in case a metrics extension is present.
11383
+
Whether datasource metrics are published in case a metrics extension is present.
11358
11384
11359
11385
This is a global setting and is not specific to a datasource.
11360
11386
11361
-
NOTE: This is different from the "jdbc.enable-metrics" property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
11387
+
NOTE: This is different from the `quarkus.datasource."datasource name".jdbc.metrics.enabled` property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
Whether or not datasource metrics are published in case a metrics extension is present.
41
+
Whether datasource metrics are published in case a metrics extension is present.
42
42
43
43
This is a global setting and is not specific to a datasource.
44
44
45
-
NOTE: This is different from the "jdbc.enable-metrics" property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
45
+
NOTE: This is different from the `quarkus.datasource."datasource name".jdbc.metrics.enabled` property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
Whether or not datasource metrics are published in case a metrics extension is present.
41
+
Whether datasource metrics are published in case a metrics extension is present.
42
42
43
43
This is a global setting and is not specific to a datasource.
44
44
45
-
NOTE: This is different from the "jdbc.enable-metrics" property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
45
+
NOTE: This is different from the `quarkus.datasource."datasource name".jdbc.metrics.enabled` property that needs to be set on the JDBC datasource level to enable collection of metrics for that datasource.
Copy file name to clipboardExpand all lines: _versions/main/guides/datasource.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -636,10 +636,10 @@ This can be activated by setting the `quarkus.datasource.metrics.enabled` proper
636
636
For the exposed metrics to contain any actual values, a metric collection must be enabled internally by the Agroal mechanisms.
637
637
By default, this metric collection mechanism is enabled for all datasources when a metrics extension is present, and metrics for the Agroal extension are enabled.
638
638
639
-
To disable metrics for a particular datasource, set `quarkus.datasource.jdbc.enable-metrics` to `false`, or apply `quarkus.datasource.<datasource name>.jdbc.enable-metrics` for a named datasource.
639
+
To disable metrics for a particular datasource, set `quarkus.datasource.jdbc.metrics.enabled` to `false`, or apply `quarkus.datasource.<datasource name>.jdbc.metrics.enabled` for a named datasource.
640
640
This disables collecting the metrics and exposing them in the `/q/metrics` endpoint if the mechanism to collect them is disabled.
641
641
642
-
Conversely, setting `quarkus.datasource.jdbc.enable-metrics` to `true`, or `quarkus.datasource.<datasource name>.jdbc.enable-metrics` for a named datasource explicitly enables metrics collection even if a metrics extension is not in use.
642
+
Conversely, setting `quarkus.datasource.jdbc.metrics.enabled` to `true`, or `quarkus.datasource.<datasource name>.jdbc.metrics.enabled` for a named datasource explicitly enables metrics collection even if a metrics extension is not in use.
643
643
This can be useful if you need to access the collected metrics programmatically.
644
644
They are available after calling `dataSource.getMetrics()` on an injected `AgroalDataSource` instance.
0 commit comments