aboutsummaryrefslogtreecommitdiff
path: root/exporters/stats/stackdriver
diff options
context:
space:
mode:
Diffstat (limited to 'exporters/stats/stackdriver')
-rw-r--r--exporters/stats/stackdriver/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/exporters/stats/stackdriver/README.md b/exporters/stats/stackdriver/README.md
index e90dc105..ef0e85f3 100644
--- a/exporters/stats/stackdriver/README.md
+++ b/exporters/stats/stackdriver/README.md
@@ -76,7 +76,7 @@ can correctly identify your pod, cluster and container. Follow the Kubernetes in
[here](https://cloud.google.com/kubernetes-engine/docs/tutorials/custom-metrics-autoscaling#exporting_metrics_from_the_application)
and [here](https://kubernetes.io/docs/tasks/inject-data-application/environment-variable-expose-pod-information/).
-Otherwise, Exporter will use [a global Stackdriver monitored resource with no labels](https://cloud.google.com/monitoring/api/resources#tag_global),
+Otherwise, Exporter will use [a global Stackdriver monitored resource with a project_id label](https://cloud.google.com/monitoring/api/resources#tag_global),
and it works fine when you have only one exporter running.
If you want to have multiple processes exporting stats for the same metric concurrently, and your