From 6a6b9a75d5cfccdfe667992b1b9fa98250f4bbef Mon Sep 17 00:00:00 2001 From: Danny-Driscoll Date: Fri, 6 Jun 2025 14:02:25 -0400 Subject: [PATCH] Update autoscaling.md --- content/en/containers/monitoring/autoscaling.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/containers/monitoring/autoscaling.md b/content/en/containers/monitoring/autoscaling.md index 5c5f920757aee..076700810bb4b 100644 --- a/content/en/containers/monitoring/autoscaling.md +++ b/content/en/containers/monitoring/autoscaling.md @@ -175,7 +175,7 @@ The [Autoscaling Summary page][11] provides a starting point for platform teams Click **Optimize** on any workload to see its scaling recommendation. -### Deploy recommendations with Autoscaling +### Deploy Autoscaling After you identify a workload to optimize, Datadog recommends inspecting its **Scaling Recommendation**. You can also click **Configure Recommendation** to add constraints or adjust target utilization levels. @@ -209,4 +209,4 @@ As an alternative to Autoscaling, you can also deploy Datadog's scaling recommen [10]: https://app.datadoghq.com/orchestration/scaling/ [11]: https://app.datadoghq.com/orchestration/scaling/summary [12]: https://app.datadoghq.com/orchestration/scaling/cluster -[13]: https://app.datadoghq.com/orchestration/scaling/workload \ No newline at end of file +[13]: https://app.datadoghq.com/orchestration/scaling/workload