51 lines
2.3 KiB
Plaintext
51 lines
2.3 KiB
Plaintext
[[actuator.cloud-foundry]]
|
|
== Cloud Foundry Support
|
|
Spring Boot's actuator module includes additional support that is activated when you deploy to a compatible Cloud Foundry instance.
|
|
The `/cloudfoundryapplication` path provides an alternative secured route to all `@Endpoint` beans.
|
|
|
|
The extended support lets Cloud Foundry management UIs (such as the web application that you can use to view deployed applications) be augmented with Spring Boot actuator information.
|
|
For example, an application status page can include full health information instead of the typical "`running`" or "`stopped`" status.
|
|
|
|
NOTE: The `/cloudfoundryapplication` path is not directly accessible to regular users.
|
|
To use the endpoint, you must pass a valid UAA token with the request.
|
|
|
|
|
|
|
|
[[actuator.cloud-foundry.disable]]
|
|
=== Disabling Extended Cloud Foundry Actuator Support
|
|
If you want to fully disable the `/cloudfoundryapplication` endpoints, you can add the following setting to your `application.properties` file:
|
|
|
|
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
|
|
----
|
|
management:
|
|
cloudfoundry:
|
|
enabled: false
|
|
----
|
|
|
|
|
|
|
|
[[actuator.cloud-foundry.ssl]]
|
|
=== Cloud Foundry Self-signed Certificates
|
|
By default, the security verification for `/cloudfoundryapplication` endpoints makes SSL calls to various Cloud Foundry services.
|
|
If your Cloud Foundry UAA or Cloud Controller services use self-signed certificates, you need to set the following property:
|
|
|
|
[source,yaml,indent=0,subs="verbatim",configprops,configblocks]
|
|
----
|
|
management:
|
|
cloudfoundry:
|
|
skip-ssl-validation: true
|
|
----
|
|
|
|
|
|
|
|
[[actuator.cloud-foundry.custom-context-path]]
|
|
=== Custom Context Path
|
|
If the server's context-path has been configured to anything other than `/`, the Cloud Foundry endpoints are not available at the root of the application.
|
|
For example, if `server.servlet.context-path=/app`, Cloud Foundry endpoints are available at `/app/cloudfoundryapplication/*`.
|
|
|
|
If you expect the Cloud Foundry endpoints to always be available at `/cloudfoundryapplication/*`, regardless of the server's context-path, you need to explicitly configure that in your application.
|
|
The configuration differs, depending on the web server in use.
|
|
For Tomcat, you can add the following configuration:
|
|
|
|
include::code:MyCloudFoundryConfiguration[]
|