I am getting very high cardinality from the docker input measurements on AWS, where the lifecycle of containers are short. Some cron type, jobs, and crash/restart scenarios. Running in AWS using the Container service, makes a few of the tag values random each time a container starts.
I can see that a couple tags that are added based on docker labels will increase the cardinality:
I can exclude these via the configuration, so that will reduce cardinality somewhat. The container name is another issue as it contains a generated identifier for example “container_name=ecs-ion-integration-49-receptionist-c6f18886a79fc4ba2f00”
It appears in code that the input simply adds the container name as a tag.
Does anyone have a solution to this?
I’m thinking the only way to do this is to add a generic tag exclusion, not just one on labels? Something like “tag_exclude” in the configuration that would remove any tags listed before the measurement is pushed?