The Config Server serves properties from multiple sources, including one or more Git repositories. For Git repositories, the Config Server makes use of an internal "mirror service" to create a mirror of each Git repository used. These mirrors are local to the VMware Tanzu Application Service for VMs (TAS for VMs) foundation, and the Config Server serves properties to client applications from these mirrors, rather than from the external Git repositories themselves.
There is a button in Apps Manager web UI, Synchronize Mirrors, which helps manually refresh a Config Server service instance's Git mirrors. The result can be found inside the same page.
It is a little bit struggling if you would like to understand whether Config Server's backing app is able to pull configurations from mirror service. That is where this article helps.
A feature, Actuator, has been available in Spring Boot since April 2014. It is used for monitoring our app, gathering metrics, and understanding traffic or the state of our database becomes trivial with this dependency.
Spring Cloud Config Server has an Actuator endpoint on a service instance. We can access it 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:
|
The path, /actuator/health, discloses a lot of useful information, one of which unveils the information we are interested in. For more details, please refer to Spring Boot Actuator endpoints.
Here is an example retrieved from the health endpoint. It shows a status "UP" which indicates the service instance's backing app works fine when retrieving the properties from the mirror service. Or there could be something wrong. Please feel free to raise a ticket if you need further assistance from Broadcom Tanzu support.