Spring Cloud Services v3.0

Spring Boot Actuator Endpoints

Page last updated:

The Spring Cloud Config Server backing app for a Config Server service instance uses Spring Boot Actuator. Actuator adds a number of endpoints to the app, including the endpoints that are summarized below.

ID Function
health Displays information about the health and status of the app
info Displays selected information about the app

See the Endpoints section of the Actuator documentation for the full list of endpoints.

A Config Server service instance’s backing Spring Cloud Config Server app enables the Spring Boot Actuator health and info endpoints. See below for information about how to access these endpoints.

Locating the Service Instance URL

To obtain the URL of the service instance’s backing app, run the cf service command, giving the name of the service instance:

$ cf service my-config-server
Showing info of service my-config-server in org myorg / space dev as user...

name:            my-config-server
service:         p.config-server
plan:            standard
description:     Config Server

Copy the URL given for dashboard, removing the /dashboard path. This is the URL of the service instance’s backing app. In the example above, this would be:

Accessing Endpoints

You can access an Actuator endpoint on the service instance by appending the path /actuator/ENDPOINT to the URL of the service instance’s backing app, where ENDPOINT is the ID of the endpoint. To view the output of the health endpoint, append /actuator/health to the backing app’s URL. The following example uses cURL to make a request of the endpoint:

$ curl

Given an unauthenticated request, the health endpoint displays only summary health information. With the cf CLI, you can use the cf oauth-token command to obtain an OAuth 2.0 token for use in making an authenticated request to this endpoint:

$ curl -H "Authorization: $(cf oauth-token)"
Create a pull request or raise an issue on the source for this page in GitHub