Configurable Domainname

Currently it is only possible to define the full hostname in the task definition. From e.g. a monitoring perspective this is problematic, because e.g. in NewRelic (and probably other monitoring tools which use the hostname for identification) all containers are then recognized as a single server.

It would be very useful, if it's possible to define a `domainname` (like e.g. `nginx.myservice.myorganization.org`) which will be appended to the container id and then used as the container hostname: `6efe0554d193.nginx.myservice.myorganization.org`.
This way it would be possible to identify the containers by hostname and at the same time they keep their unique hostnames.

Or is there already a way to achieve that?
What do you think?

Best
Fabian

The issue names no repository files, tests, or entry points. Start by checking current task-definition support and documentation for container hostname configuration; done would require a confirmed product direction for appending a configurable domainname while preserving unique container hostnames.

Written by the indexing model from the issue text.