Since I'm getting little bit mixed information I would like to have information from all of you guys about this topic.
We are using SAAS version of Dynatrace and trying to figure out that can we download agents trough the environment ActiveGate? I got information from support that the environment ActiveGate does not contain the agent installation packages and therefore we can't download the agents trough environment activegate.
I know that this is possible in Managed environment trough the Cluster ActiveGates but seems that we can't make the agent download process trough the environment ActiveGate?
Our case is that the monitored hosts do not have internet connection and that's why we would like to route the download process trough the environment ActiveGate. But if this is not possible we just need to think about some other solution.
Just would like to have comments from community is that possible to download the agents trough environment ActiveGate or not.
Solved! Go to Solution.
Thank you for the suggestion @christian w. and we know this possibility also.
From our perspective it would actually be easier if we could route the agent download trough the ActiveGate than manually copying the installation packet to servers.
If the agent download cant be done trough the ActiveGate we just need to think about setting up proxy or something else.
Yes, you are able to download an agent through the activegate if you have access from your local machine to the ActiveGate.
First go to the "Deploy Dynatrace" and "start installation" then select linux. Take the wget command it gives you and alter it with the activegate IP over port 999 (which is the default communication port). Your environment_ID can be gathered from your tenant URL (example: <environment_ID>.live.dynatrace.com)
I believe that you should take your URL and make it look like this:
wget -O Dynatrace-OneAgent-Linux-<Version_here> "https://<ActiveGate_IP_Address:9999>/e/<environment_ID>/api/v1/deployment/installer/agent/unix/default/latest?arch=x86&flavor=default" --header="Authorization: Api-Token - xxxxx"
Make sure to add the /e/<environment_ID>
I just tested this on my SaaS environment and it works like a charm.