anchor.diff:  	management.server.port=-1
   ----
   
  -
  +Above can be achieved using the property `management.endpoints.web.exposure.exclude` as well, as shown in
  +following example:
  +
  +[source,properties,indent=0]
  +----
  +	management.endpoints.web.exposure.exclude=*
  +----
  +
  +`*` can be used to select all endpoints.
  +
  +If you want to disable HTTP endpoints selectively, configure the list of endpoints IDs to be disabled in
  +`management.endpoints.web.exposure.exclude` property
  +as shown in following example:
  +
  +[source,properties,indent=0]
  +----
  +	management.endpoints.web.exposure.exclude=env,beans
  +----
  +
  +`env` and `beans` endpoints will not be exposed over HTTP.
   
   [[production-ready-jmx]]
   == Monitoring and Management over JMX
  
positive.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.
  
  
  
  [[production-ready-endpoints-custom-mapping]]
  === Actuator Web Endpoint Paths
  By default, endpoints are exposed over HTTP under the `/actuator` path by using the ID of
  the endpoint. For example, the `beans` endpoint is exposed under `/actuator/beans`. If you
  want to map endpoints to a different path, you can use the
  `management.endpoints.web.path-mapping` property. Also, if you want change the base path,
  you can use `management.endpoints.web.base-path`.
  
  The following example remaps `/actuator/health` to `/healthcheck`:
  
  .application.properties
  [source,properties,indent=0]
  ----
  	management.endpoints.web.base-path=/
  	management.endpoints.web.path-mapping.health=healthcheck
  ----
  
  
  
  
negative.code: 
  
  
  [[production-ready-customizing-management-server-context-path]]
  === Customizing the Management Endpoint Paths
  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:
  