From 2c9a587a1c864ccf0468bb37cf0c052ca3f54f92 Mon Sep 17 00:00:00 2001 From: Frederico Marques Date: Thu, 25 Apr 2019 17:43:52 +0100 Subject: [PATCH] Fix wording around PROMETHEUS_NOLABELS --- README.md | 2 +- discoverecs.py | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index e45b2f4..f68deca 100644 --- 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 index 67af3eb..e52c8bb 100644 --- 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.