From 51b569c7b7cce83c8a6e2f7492854e728b5d5dbd Mon Sep 17 00:00:00 2001 From: Tejeev Date: Fri, 26 Jul 2019 14:29:17 +0100 Subject: [PATCH] Reworded custom metrics monitoring Seemed to say that custom metrics monitoring would work only if project monitoring was the only metrics enabled. --- .../rancher/v2.x/en/project-admin/tools/monitoring/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/project-admin/tools/monitoring/_index.md b/content/rancher/v2.x/en/project-admin/tools/monitoring/_index.md index 60578c82c98..c82f4fcbe08 100644 --- a/content/rancher/v2.x/en/project-admin/tools/monitoring/_index.md +++ b/content/rancher/v2.x/en/project-admin/tools/monitoring/_index.md @@ -49,7 +49,7 @@ Grafana | 100m | 100Mi | 200m | 200Mi | No If [cluster monitoring]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/) is also enabled for the project, [workload metrics]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/tools/monitoring/cluster-metrics/#workload-metrics) are available for the project. -If only project monitoring is enabled, you can monitor custom metrics from any [exporters](https://prometheus.io/docs/instrumenting/exporters/). You can also expose some custom endpoints on deployments without needing to configure Prometheus for your project. +You can monitor custom metrics from any [exporters](https://prometheus.io/docs/instrumenting/exporters/) as long as project monitoring is enabled. You can also expose some custom endpoints on deployments without needing to configure Prometheus for your project. ### Example