Using the Dashboard
Page last updated:
Note: Service Registry for Pivotal Cloud Foundry (PCF) is currently based on Spring Cloud® OSS Camden. If binding a Spring Cloud OSS Angel application to a Service Registry service instance, you may see irregular behavior in the Service Registry service instance dashboard’s listing for the application.
For information on current client dependencies provided for use with Spring Cloud Services service instances, see the Client Dependencies topic.
To find the dashboard, navigate in Pivotal Cloud Foundry® Apps Manager to the Service Registry service instance’s space, click the listing for the service instance, and then click Manage.
If you are using version 6.8.0 or later of the Cloud Foundry Command Line Interface tool (cf CLI), you can also use
cf service SERVICE_NAME, where
SERVICE_NAME is the name of the Service Registry service instance:
$ cf service service-registry Service instance: service-registry Service: p-service-registry Bound apps: Tags: Plan: standard Description: Service Registry for Spring Cloud Applications Documentation url: http://docs.pivotal.io/spring-cloud-services/ Dashboard: https://spring-cloud-broker.wise.com/dashboard/p-service-registry/a9bcaf09-ba0a-4650-bdfc-75784882245e Last Operation Status: create succeeded Message: Started: 2016-09-19T21:05:32Z Updated:
Visit the URL given for “Dashboard”.
The dashboard shows the URL of the Service Registry service instance, the count of backing applications for the service instance (the High Availability or HA count), and the URLs of any peer service instances, as well as the applications currently registered with the service instance or with any peer service instances.
If the Service Registry service instance has been configured to replicate its registry with any peers, peers are listed according to their status in the “replicas” fields under General Info. Peers which are registered with this service instance are listed in “registered-replicas” and, if currently in service, will be listed in “available-replicas”. Peers which have been configured for this service instance but have not registered will be listed in “unavailable-replicas”.
Before you have bound any applications to the Service Registry instance, the Service Registry dashboard displays only
EUREKA-SERVER (the Service Registry backing application itself) under “Registered Apps”. If you bind an application which uses
@EnableDiscoveryClient to the service instance (see the Writing Client Applications topic), restage the application, and wait for it to register with Eureka, you will see it listed in the dashboard.