anchor.diff:  	}
   ----
   
  -TIP: You can also pass a `null` `configuredLevel` to "reset" the specific level of the
  -logger (and use the default configuration instead).
  +TIP: To "reset" the specific level of the logger (and use the default configuration
  +instead), you can pass a value of `null` as the `configuredLevel`.
   
   
   
  
positive.code: 
  If your application has custom security configuration and you want all your actuator
  endpoints to be accessible without authentication, you need to explicitly configure that
  in your security configuration. Along with that, you need to change the
  `management.security.enabled` property to `false`.
  
  If your custom security configuration secures your actuator endpoints, you also need to
  ensure that the authenticated user has the roles specified under
  `management.security.roles`.
  
  TIP: If you don't have a use case for exposing basic health information to unauthenticated
  users, and you have secured the actuator endpoints with custom security, you can set
  `management.security.enabled` to `false`. This will inform Spring Boot to skip the
  additional role check.
  
  
  
  [[production-ready-customizing-endpoints]]
  === Customizing endpoints
  Endpoints can be customized using Spring properties. You can change if an endpoint is
  `enabled` and its `id`.
  
  For example, here is an `application.properties` that changes the id of the `beans`
  endpoint and also enables `shutdown`.
  
  [source,properties,indent=0]
  ----
  
negative.code: 
  
  [[production-ready-whats-next]]
  == What to Read Next
  If you want to explore some of the concepts discussed in this chapter, you can take a
  look at the actuator {github-code}/spring-boot-samples[sample applications]. You also
  might want to read about graphing tools such as http://graphite.wikidot.com/[Graphite].
  