-
Notifications
You must be signed in to change notification settings - Fork 139
Dimension labels are mixed up #10
Comments
To add, the wrong value is assigned to the wrong label with some metrics, but will return the correct values with the correct labels with a different metric in the same namespace, Wrong values with labels:With the following config:
The metric returned:
The metric incorrectly returns:
Correct values with labels:The config below is the same as the config as above, but only the
Correct values with labels are returned:
Both |
@tul @tokyowizard I pushed a new branch named fix_label_swaping, which contains a fix for the issue, maybe you can pull it and build it and report if it solves the issue for you as well. |
@n17h31sm I had to get monitoring setup and move on to other projects. To do so, I used the "official" exporter despite that it's java based. Sorry, I won't be able to test because of that. |
@n17h31sm sorry for the long delay - yes the |
I tried to run a docker image using the
messages and no metrics at http://cloudwatch-exporter:9042/scrape. |
If a config like the following is used:
Then it produces metrics with the "service_name" and "cluster_name" values swapped over, e.g. :
aws_ecs_memory_utilization_maximum{cluster_name="bot-blah",service_name="us-east-1-prod-public",task="bots-dev"} 8.69140625
If the
aws_dimensions
entries are swapped around, to be[ 'ServiceName', 'ClusterName' ]
then the dimensions become correctly labelled.aws_ecs_memory_utilization_maximum{cluster_name="us-east-1-prod-public",service_name="bot-blah",task="bots-dev"} 8.69140625
The text was updated successfully, but these errors were encountered: