anchor.diff:  
   
   
  -[[production-ready-monitoring]]
  -== Monitoring and Management over HTTP
  -If you are developing a web application, Spring Boot Actuator auto-configures all
  -enabled endpoints to be exposed over HTTP. The default convention is to use the `id` of
  -the endpoint with a prefix of `/actuator` as the URL path. For example, `health` is
  -exposed as `/actuator/health`.
  -
  -TIP: Actuator is supported natively with Spring MVC, Spring WebFlux, and Jersey.
  -
  -
  -
   [[production-ready-customizing-management-server-context-path]]
   === Customizing the Management Endpoint Paths
  -Sometimes, it is useful to customize the prefix for the management endpoints. For
  +Sometimes, it is useful to customize the prefix for the management endpoints. By default,
  +endpoints are exposed over HTTP under the `/actuator` path by using the ID of
  +the endpoint. For
   example, your application might already use `/actuator` for another purpose. You can
   use the `management.endpoints.web.base-path` property to change the prefix for your
   management endpoint, as shown in the following example:
  
positive.code: 	management.server.port=-1
  ----
  
  
  
  [[production-ready-jmx]]
  == Monitoring and Management over JMX
  
negative.code: management context path is `/management`, then the discovery page is available from
  `/management`. When the management context path is set to `/`, the discovery page is
  disabled to prevent the possibility of a clash with other mappings.
  
  
  
  