Skip to content

[OTAGENT-634] Instructions on autoscaling in DDOT Gateway #32664

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Nov 6, 2025
Merged

[OTAGENT-634] Instructions on autoscaling in DDOT Gateway #32664

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9968b26
[OTAGENT-634] Guide on autoscaling in DDOT Gateway
songy23 Nov 6, 2025
3a60c45
Update content/en/opentelemetry/setup/ddot_collector/install/kubernet…
songy23 Nov 6, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
41 changes: 41 additions & 0 deletions content/en/opentelemetry/setup/ddot_collector/install/kubernetes_gateway.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -374,6 +374,45 @@
config: | <YOUR CONFIG>
```

### Enable Autoscaling with Horizontal Pod Autoscaler (HPA)

Check warning on line 377 in content/en/opentelemetry/setup/ddot_collector/install/kubernetes_gateway.md

View workflow job for this annotation

GitHub Actions / vale

Datadog.headings 

'Enable Autoscaling with Horizontal Pod Autoscaler (HPA)' should use sentence-style capitalization.

The DDOT Collector gateway supports autoscaling with the Kubernetes Horizontal Pod Autoscaler (HPA) feature. To enable HPA, configure `otelAgentGateway.autoscaling`.

```yaml
# values.yaml
targetSystem: "linux"
agents:
enabled: false
clusterAgent:
enabled: false
otelAgentGateway:
enabled: true
ports:
- containerPort: "4317"
name: "otel-grpc"
config: | <YOUR CONFIG>
replicas: 4 # 4 replicas to begin with and HPA may override it based on the metrics
autoscaling:
enabled: true
minReplicas: 2
maxReplicas: 10
metrics:
# Aim for high CPU utilization for higher throughput
- type: Resource
resource:
name: cpu
target:
type: Utilization
averageUtilization: 80
behavior:
scaleUp:
stabilizationWindowSeconds: 30
scaleDown:
stabilizationWindowSeconds: 60
```

You can use resource metrics (CPU or memory), custom metrics (Kubernetes Pod or Object), or external metrics as autoscaling inputs. For resource metrics, ensure that the [Kubernetes metrics server][9] is running in your cluster. For custom or external metrics, consider configuring the [Datadog Cluster Agent metrics provider][10].

### Deploying a multi-layer gateway

For advanced scenarios, you can deploy multiple gateway layers to create a processing chain. To do this, deploy each layer as a separate Helm release, starting from the final layer and working backward.
Expand Down Expand Up @@ -516,3 +555,5 @@
[6]: https://opentelemetry.io/docs/collector/deployment/gateway/
[7]: https://github.com/open-telemetry/opentelemetry-collector/tree/main/config/configtls
[8]: http://github.com/DataDog/helm-charts/blob/main/charts/datadog/README.md
[9]: http://github.com/kubernetes-sigs/metrics-server
[10]: /containers/guide/cluster_agent_autoscaling_metrics/?tab=helm
Loading