Request for Dynatrace ActiveGate Resource Sizing Guidance for Kubernetes Deployment

[gauravpayghan__]

 

1. During our initial deployment of Dynatrace full-stack monitoring via the Operator on AKS, we proposed the following resource sizing for ActiveGate:

   requests:
     cpu: 500m
     memory: 1.5Gi
   limits:
     cpu: 1000m
     memory: 1.5Gi

   Is there any official Dynatrace documentation or sizing guideline that supports this configuration?

2. The current configuration provided by the Infra team is:

   requests:
     cpu: 100m
     memory: 256Mi
   limits:
     cpu: 250m
     memory: 512Mi

   Are these values sufficient to support the following ActiveGate capabilities reliably?

   • routing
   • kubernetes-monitoring
   • debugging

3. What are the potential risks or limitations of operating ActiveGate with reduced resource allocations, especially in a production-grade Kubernetes environment?

4. Is there a sizing calculator, benchmark, or reference architecture from Dynatrace that we can use to justify the original resource request?

5. Can we correlate ActiveGate performance degradation (e.g., dropped metrics, delayed routing) with undersized resource limits in Dynatrace dashboards or logs?