Document how to use Actuator with Jersey

Closes gh-4577

spring-boot-docs/src/main/asciidoc/howto.adoc

@@ -1776,6 +1776,20 @@ See also the section on <<boot-features-error-handling, Error Handling>> for det
 how to register handlers in the servlet container.
 
 
+
+[[howto-use-actuator-with-jersey]]
+=== Actuator and Jersey
+Actuator HTTP endpoints are only available for Spring MVC-based applications. If you want
+to use Jersey and still use the actuator you will need to enable Spring MVC (by depending
+on `spring-boot-starter-web`, for example). By default, both Jersey and the Spring MVC
+dispatcher servlet are mapped to the same path (`/`). You will need to change the path for
+one of them (by configuring `server.servlet-path` for Spring MVC or
+`spring.jersey.application-path` for Jersey). For example, if you add
+`server.servlet-path=/system` into `application.properties`, the actuator HTTP endpoints
+will be available under `/system`.
+
+
+
 [[howto-security]]
 == Security
 

spring-boot-docs/src/main/asciidoc/production-ready-features.adoc

@@ -9,7 +9,8 @@ application using HTTP endpoints, with JMX or even by remote shell (SSH or Telne
 Auditing, health and metrics gathering can be automatically applied to your application.
 
 Actuator HTTP endpoints are only available with a Spring MVC-based application. In
-particular, it will not work with Jersey unless you enable Spring MVC as well.
+particular, it will not work with Jersey <<howto.adoc#howto-use-actuator-with-jersey,
+unless you enable Spring MVC as well.>>
 --