anchor.diff:  == Monitoring and management over HTTP
   If you are developing a Spring MVC application, Spring Boot Actuator will auto-configure
   all enabled endpoints to be exposed over HTTP. The default convention is to use the
  -`id` of the endpoint as the URL path. For example, `health` is exposed as `/health`.
  +`id` of the endpoint with a prefix of `/application` as the URL path. For example, `health`
  +is exposed as `/application/health`.
   
   
   
  
positive.code: `health` endpoint provides basic application health information.
  
  The way that endpoints are exposed will depend on the type of technology that you choose.
  Most applications choose HTTP monitoring, where the ID of the endpoint is mapped
  to a URL. For example, by default, the `health` endpoint will be mapped to `/health`.
  
  The following technology agnostic endpoints are available:
  
  
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.
  For example, your application might already use `/application` for another purpose.
  You can use the `management.context-path` property to change the prefix for your management endpoint:
  
  [source,properties,indent=0]
  ----
  	management.context-path=/manage
  ----
  
  The `application.properties` example above will change the endpoint from `/application/{id}` to
  `/manage/{id}` (e.g. `/manage/info`).
  
  You can also change the "`path`" of an endpoint (using `endpoints.{name}.path`) which then
  changes the default resource path for the MVC endpoint. There is no validation on
  those values (so you can use anything that is legal in a URL path). For example, to change
  the location of the `/health` endpoint to `/ping/me` you can set
  `endpoints.health.path=/ping/me`.
  