-
Notifications
You must be signed in to change notification settings - Fork 41.2k
Spring Boot 2.0.0 RC2 Release Notes
For changes in earlier milestones, please refer to:
See instructions in the 2.0.0.RC1 release notes for upgra 8000 ding from v2.0.0.RC1 and earlier.
To reduce the confusion and provide an optimal structure, the management.endpoints.web.expose
property has been relocated to management.endpoints.web.exposure.include
, together with management.endpoints.web.exposure.exclude
(formerly defined as management.endpoints.web.exclude
). JMX-related settings have been migrated to management.endpoints.jmx.exposure.include
and management.endpoints.jmx.exposure.exclude
respectively.
To align with decisions in Micrometer 1.0.0
, metrics prefix for RabbitMQ, Cache and JDBC are no longer configurable. The prefixes are now rabbitmq
, cache
, and jdbc
respectively.
Also, the individual components are now dedicated auto-configurations rather than a single MetricsAutoConfiguration
. This improves the conditions report and gives you the ability to exclude something in a more fine-grained manner if necessary.
The health
endpoint has been revisited to allow more flexibility and align with the features in Spring Boot 1.x
. The show-details
property is now an enum that can be never
(default), when-authorized
and always
.
Check the updated documentation for more details.
The Repackager
has been reworked so that the order of libraries is predictable, regardless of whether a library needs to be unpacked or not.
Tip
|
Check the configuration changelog for a complete overview of the changes in configuration. |
Spring Boot RC 2 supports the GA release of Micrometer. It adds the following features:
-
Property-based filtering of meters (see the updated documentation)
-
auto-create-db
flag for Influx -
publish-unchanged-meters
for StatsD -
Support for SignalFx, New Relic and Wavefront
-
ClassLoader
and file descriptor metrics -
Tomcat metrics
-
Hikari-specific metrics are exposed with a
hikaricp
prefix. Each metric is tagged by the name of the pool (can be controlled withspring.datasource.name
)
The reference documentation now has a dedicated section on Kotlin.
It is now possible to specify a custom delimiter when binding a collection using @Delimiter
on the target field.