12 Mar 2023 10:41 AM - last edited on 24 Mar 2023 02:40 AM by Michal_Gebacki
When installing ActiveGates on a Windows machine, the requirements are really low (in https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-activegate/installation/win...)
Now, I normally try to secure and optimize machines where I have access. These are some services that I typically check if I can disable in Services:
Disabling these services has mainly an impact on memory usage, and that is especially true if you are running in a 2 GB environment. Of course, you have to be careful when disabling Services. Please check if they aren't really needed, as I won't be responsible for something failing on your side 😃
Another thing that can be done is limit the Modules that you configure in an ActiveGate. By default, all of them are Enabled, as can be seen below.
In most cases, most of them might not be needed. You can disable them according to: https://www.dynatrace.com/support/help/setup-and-configuration/dynatrace-activegate/configuration/co...
I always recommend making the AG have more resources than what is recommended. Especially if you are going to expand your monitoring for your organization. Plugins/Extensions, Cloud monitoring and such consume resources, so that's why we lean towards more than what is listed as the requirements.
Its also very important to have an organized AG set up. AGs for Kubernetes and just kubernetes extensions, AGs for VMware entities and just those entities. This allows for redundancy, and the old adage of "Don't put all your eggs in one basket"
Yes, many AGs have very specific functions. That's why I suggested that users deactivate services and Dynatrace modules that are not needed... Besides that, FinOps is an important aspect for my clients, and I tend to tell them that Dynatrace can really run in servers with very few resources 😁