Merge pull request #1725 from agrare/remove_ocp_hawkular

Remove hawkular metrics documentation

Author: Fryguy

_includes/provider-ocp-add-container.md

@@ -64,7 +64,7 @@
 
 8. In the **Metrics** endpoint tab optionally configure the metrics service details:
 
-    1.  Select a service type (Prometheus or Hawkular) or leave disabled
+    1.  Select a service type (e.g.: Prometheus) or leave disabled
 
     2.  Select a **Security Protocol** method to specify how to
         authenticate the service:
@@ -80,16 +80,6 @@
             provider’s CA certificate to the **Trusted CA
             Certificates** box in PEM format.
 
-            **Note:**
-
-            In OpenShift, the default deployment of the router generates
-            certificates during installation, which can be used with the
-            **SSL trusting custom CA** option. Connecting a Hawkular
-            endpoint with this option requires the CA certificate that
-            the cluster uses for service certificates, which is stored
-            in `/etc/origin/master/service-signer.crt` on the first
-            master in a cluster.
-
           - **SSL without validation**: Authenticate the provider
             insecurely using SSL. (Not recommended)
 
@@ -111,7 +101,7 @@
 
         In this example you would use `prometheus-k8s-openshift-monitoring.ocp.example.com` as the metrics hostname.
 
-    4.  Enter the **API Port** if your Hawkular or Prometheus provider
+    4.  Enter the **API Port** of your metrics endpoint
         uses a non-standard port for access. The default port is `443`.
 
     5.  Click **Validate** to confirm that {{ site.data.product.title_short }} can connect

api/reference/providers.md

@@ -264,10 +264,10 @@ Compound credentials set:
 
 When creating or updating providers, connection configurations can be
 set. Connection configurations can be used to specify resources such as
-an `amqp` event provider for OpenStack, adding Hawkular metrics, or an
+an `amqp` event provider for OpenStack, adding Prometheus metrics, or an
 authentication token.
 
-Hawkular metrics:
+Prometheus metrics:
 
 ``` json
 {
@@ -277,16 +277,16 @@ Hawkular metrics:
   "connection_configurations": [
     {
       "endpoint": {
-        "role"                  : "hawkular",
-        "hostname"              : "hawkular_host",
-        "port"                  : "1443",
+        "role"                  : "prometheus",
+        "hostname"              : "prometheus_host",
+        "port"                  : "443",
         "security_protocol"     : "ssl-without-validation",
         "certificate_authority" : "-----BEGIN CERTIFICATE-----",
         "verify_ssl": 0
       },
       "authentication": {
-        "role"     :  "hawkular",
-        "auth_key" :  "hawkular_auth_key"
+        "role"     :  "prometheus",
+        "auth_key" :  "prometheus_auth_key"
       }
     }
   ]

api/reference/settings.md

@@ -123,9 +123,6 @@ The complete updated settings is returned:
     “purge_window_size” : 500
   },
   ...
-  "hawkular_tenant_labels": {
-    "_hawkular_admin": "Hawkular Admin"
-  }
 }
 ```
 

integration_with_openshift_container_platform/_topics/ocp-metrics.md

@@ -11,10 +11,6 @@
 
 {% include_relative _topics/prerequisites.md %}
 
-## Enabling OpenShift Container Platform Metrics
-
-{% include_relative _topics/ocp-metrics.md %}
-
 ## Retrieving the OpenShift Container Platform Management Token
 
 {% include_relative _topics/ocp-retrieve-tokens.md %}

integration_with_openshift_container_platform/index.md

@@ -51,7 +51,7 @@ Edit information about a provider such as the name, hostname, IP address or port
 
     5.  Click **Validate** to confirm that {{ site.data.product.title_short }} can connect to the OpenShift Container Platform provider.
 
-6.  Under **Endpoints** in the **Metrics** tab, configure the following for gathering capacity and utilization metrics for Hawkular or Prometheus based on the selection:
+6.  Under **Endpoints** in the **Metrics** tab, configure the following for gathering capacity and utilization metrics for Prometheus based on the selection:
 
     1.  Select a **Security Protocol** method to specify how to authenticate the provider: