If you want to monitor AWS Fargate with Dynatrace and deploy OneAgent you have three options according to your scenario:
As you may notice the parameter:
--set-host-group=my_host_group
is not supported in Fargate but for many of us this is a gruesome headache because we use hosts groups for many purposes like assigning membership to MZ's among others.
But the following guide is a step by step solution to resolve this using a workaround.
- No matter what option you selected to create the container please add an Enviroment Variable in your dockerfile.
ENV DT_CUSTOM_PROP "Host_Group=AWS-EKS-FARGATE-SWITCH"example:
- As you see in STEP 1 after ENV use DT_CUSTOM_PROP
- And finally set your Environment Metadata "Host_Group=my_host_group" in my example "HOST_GROUP=AWS-EKS-FARGATE-SWITCH"
- After this please deploy your Fargate container.
- If everything goes as expected you will be able to see the Environment custom metadata on your process group
- Well so far so good, now it's time to add an autotagging rule as follows:
Please pay attention to the options on the numbers 1 to 8.
- Well after this your Host(Container),Process Group, Process Group Instances and Services will have the tag from the rule of your (much the same as)"Host_Group" Environment custom metadata.
- Feel free to add these entities to your MZ.
________________________________________________________________________________________________
My main inspiration for writing this PRO TIP is to create a guide based on ideas I saw in another post. This is the guide I wish I had found in the first place for this topic. Using that solution as a base I had to sort and test ideas and adapt to the new interface, I want to thank to @abraham_villega original answer on that post. and to my fellow 
Jason @ct_27 for contacting me, you were the trigger to start writing.
