Fix wording around PROMETHEUS_NOLABELS

signal-ai · Apr 25, 2019 · 2c9a587 · 2c9a587
1 parent 80538d1
commit 2c9a587
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/README.md b/README.md
@@ -129,7 +129,7 @@ resource "aws_iam_role_policy_attachment" "prometheus-server-role-ec2-read-only"
 For skipping labels, set PROMETHEUS_NOLABELS to "true".
 This is useful when you use "blackbox" exporters or Pushgateway in a task
 and metrics are exposed at a service level. This way, no EC2/ECS labels
-will be exposed and the instance label will be empty.
+will be exposed and the instance label will always point to the job name.
 
 PROMETHEUS_PORT can be used for tasks using classic ELB setup with multiple
 port mappings.
diff --git a/discoverecs.py b/discoverecs.py
@@ -34,7 +34,7 @@
 For skipping labels, set PROMETHEUS_NOLABELS to "true".
 This is useful when you use "blackbox" exporters or Pushgateway in a task
 and metrics are exposed at a service level. This way, no ec2/ecs labels
-will be exposed and the instance label will be empty.
+will be exposed and the instance label will always point to the job name.
 
 PROMETHEUS_PORT can be used for tasks using classic ELB setup with multiple
 port mappings.