Add another actuator endpoint in example of exposing gateway actuator endpoint

Question

Actuator endpoints priority against custom routes should be documented. For instance, if I have a route for /** configured in my application

- id: frontend
      uri: ${frontend.base.url}
      predicates:
        - Path=/**

and have

management.endpoints.web.exposure.include=gateway,health

I will get actuator health report on /actiator/health as I want, but it is not so obvious when reading https://cloud.spring.io/spring-cloud-gateway/reference/html/#_actuator_api.
Actually I am not sure if this is expected behavior (I mean that I am getting actuator response and not my UI response for /**)

So could you please explicitly mention this aspect in documentation?

Start with the Spring Cloud Gateway reference section linked as “Actuator API” and review the route example using Path=/** plus management.endpoints.web.exposure.include=gateway,health. Update the documentation to explain actuator endpoint priority against custom routes and clarify the expected response for /actuator/health; done when this behavior is explicit.