jboyd01

We want to expose Metrics from Catalog via prometheus to enable monitoring and track key metrics and provide the ability 
to alert on specific conditions.

Prometheus provides a client api that enables you to register a HTTP handler (ie /metrics) that automatically exposes 
Prometheus metrics objects.  Many core components within Kubernetes already do this including the CAdvisor, Kubelet, 
Scheduler, Proxy,  and many more.  The Prometheus server can be easily configured with scrap configurations that will 
poll the /metrics endpoints and provide a centralized UI for discovery & analysis.  Advanced analytic and graphing tools
such as Grafana can consume Prometheus data are often used to augment monitoring.

Kubernetes API Servers are exposing Prometheus metrics out of the box, Prometheus must be 

jboyd01

You can validate Service Catalog using a couple of different approaches.  The Service Catalog E2E is one (see the instructions 
for syncing Service Catalog to OpenShift).  Additionally, you can utilize the OpenShift web console or the CLI and add 
applications exposed by the Template Service Broker or Ansible Service Broker.  Note that some Templates create applications 
directly and some use the Service Catalog.  Python & HTTPD don't use Service Catalog, most templates with "persistent" in the 
name do.  For those that don't, there is no ServiceInstance, Class or binding created.  Once you add applications to your 
project, you should be able to see them via the CLI (oc get serviceinstances --all-namespaces)

In the OpenShift web console (https://127.0.0.1:8443) login as Developer (any password works) and select MyProject (or any 
other project and then "Add to Project", "Browse Catalog".  I believe the Ansible Service Broker offerings have (APB) in the 
name.