Skip to content

Commit 59224fd

Browse files
committed
Document Actuator's ObjectMapper isolation
Closes gh-47039
1 parent eeebc37 commit 59224fd

File tree

1 file changed

+11
-0
lines changed
  • spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator

1 file changed

+11
-0
lines changed

spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/endpoints.adoc

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -383,6 +383,17 @@ management:
383383
TIP: See javadoc:org.springframework.boot.actuate.autoconfigure.endpoint.web.CorsEndpointProperties[] for a complete list of options.
384384

385385

386+
[[actuator.endpoints.json]]
387+
== JSON
388+
389+
When working with JSON, Jackson is used for serialization and deserialization.
390+
By default, an isolated javadoc:com.fasterxml.jackson.databind.ObjectMapper[] is used.
391+
This isolation means that it does not share the same configuration as the application's `ObjectMapper` and it is not affected by `spring.jackson.*` properties.
392+
To disable this behavior and configure Actuator to use the application's `ObjectMapper`, set configprop:management.endpoints.jackson.isolated-object-mapper[] to `false`.
393+
Alternatively, you can define your own javadoc:org.springframework.boot.actuate.endpoint.jackson.EndpointObjectMapper[] bean that produces an `ObjectMapper` that meets your needs.
394+
Actuator will then use it for JSON processing.
395+
396+
386397

387398
[[actuator.endpoints.implementing-custom]]
388399
== Implementing Custom Endpoints

0 commit comments

Comments
 (0)