From 032c8c15a966df9b66586610fd669cbcbf078a44 Mon Sep 17 00:00:00 2001 From: Neil MacDougall Date: Sat, 27 Apr 2019 09:29:20 +0100 Subject: [PATCH] Metrics chart is in the SUSE repository --- docs/planning/metrics.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/planning/metrics.md b/docs/planning/metrics.md index b4e540ee94..60ea270fa3 100644 --- a/docs/planning/metrics.md +++ b/docs/planning/metrics.md @@ -12,7 +12,7 @@ can be gated. We would most likely use basic authentication and ensure HTTPS acc This basic setup would allow an administrator to deploy Prometheus and configure it to collect metrics from a Cloud Foundry deployment and for APi of Prometheus to be accessed securely. -An intial PoC to get Prometheus deployed with a firehose exported using Helm is here - https://github.com/cloudfoundry-incubator/stratos-metrics. +An intial PoC to get Prometheus deployed with a firehose exported using Helm is here - https://github.com/SUSE/stratos-metrics. In Stratos, we would add a new endpoint type "Cloud Foundry Metrics" that a user can register with the endpoint of the Prometheus API and then connect to with their credentials as configured above. This would allow the Stratos backend to be able to talk to Prometheus securely and retrieve metrics. @@ -32,4 +32,4 @@ In the case of Cloud Foundry metrics, the Stratos back-end will check the user's 1. https://prometheus.io/docs/prometheus/latest/querying/basics/ 2. https://prometheus.io/docs/prometheus/latest/querying/api/ -3. https://github.com/bosh-prometheus/firehose_exporter \ No newline at end of file +3. https://github.com/bosh-prometheus/firehose_exporter