You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/api-management-capacity.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -170,7 +170,8 @@ Use capacity metrics for making decisions whether to scale an API Management ins
170
170
+ Ignore sudden spikes that are most likely not related to an increase in load (see [Capacity metric behavior](#capacity-metric-behavior) section for explanation).
171
171
+ As a general rule, upgrade or scale your instance when a capacity metric value exceeds **60% - 70%** for a long period of time (for example, 30 minutes). Different values may work better for your service or scenario.
172
172
+ If your instance or workspace gateway is configured with only 1 unit, upgrade or scale it when a capacity metric value exceeds **40%** for a long period. This recommendation is based on the need to reserve capacity for guest OS updates in the underlying service platform.
173
-
+ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric.
173
+
+ Use [available diagnostics](monitor-api-management.md) to monitor the response times of API calls. Consider adjusting scaling thresholds if you notice degraded response times with increasing value of capacity metric.
174
+
+ For classic tiers, discard the most recent 1‑minute data point when reading raw Azure API Management capacity metrics because the derived value can be invalid if source data isn’t available at aggregation time; do not base operational or scaling decisions on 1‑minute values — for autoscaling use average aggregation windows of 30 minutes or longer, evaluate sustained conditions before scaling, and annotate dashboards to exclude the final 1‑minute point so trends reflect reliable data.
174
175
175
176
> [!TIP]
176
177
> If you are able to estimate your traffic beforehand, test your API Management instance or workspace gateway on workloads you expect. You can increase the request load gradually and monitor the value of the capacity metric that corresponds to your peak load. Follow the steps from the previous section to use Azure portal to understand how much capacity is used at any given time.
Copy file name to clipboardExpand all lines: articles/automation/automation-services.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -155,7 +155,7 @@ Provides a serverless, event-driven compute platform for automation that allows
155
155
156
156
- You can use a variety of languages to write functions in a language of your choice, such as C#, Java, JavaScript, PowerShell, or Python, and focus on specific pieces of code. Functions runtime is an open source.
157
157
- You can choose the hosting plan according to your function app scaling requirements, functionality, and resources required.
158
-
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable/durable-functions-overview.md?tabs=csharp).
158
+
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable-functions/durable-functions-overview.md?tabs=csharp).
159
159
- You should avoid large and long-running functions that can cause unexpected timeout issues. [Learn more](../azure-functions/functions-best-practices.md?tabs=csharp#write-robust-functions).
160
160
- When you write PowerShell scripts within the Function Apps, you must tweak the scripts to define how the function behaves, such as how it's triggered and its input and output parameters. [Learn more](../azure-functions/functions-reference-powershell.md?tabs=portal).
161
161
@@ -197,7 +197,7 @@ Provides a serverless, event-driven compute platform for automation that allows
197
197
198
198
- You can use a variety of languages to write functions in a language of your choice, such as C#, Java, JavaScript, PowerShell, or Python, and focus on specific pieces of code. Functions runtime is an open source.
199
199
- You can choose the hosting plan according to your function app scaling requirements, functionality, and resources required.
200
-
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable/durable-functions-overview.md?tabs=csharp).
200
+
- You can orchestrate complex workflows through [durable functions](../azure-functions/durable-functions/durable-functions-overview.md?tabs=csharp).
201
201
- You should avoid large and long-running functions that can cause unexpected timeout issues. [Learn more](../azure-functions/functions-best-practices.md?tabs=csharp#write-robust-functions).
202
202
- When you write PowerShell scripts within Function Apps, you must tweak the scripts to define how the function behaves, such as how it's triggered and its input and output parameters. [Learn more](../azure-functions/functions-reference-powershell.md?tabs=portal).
0 commit comments