Skip to content
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.

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

Adjusted Metric Types Titles for Reading Improvement #3

Merged
merged 1 commit into from
Jun 17, 2024
Merged
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions docs/dynamic-scaling-policy-e6927e5.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ Scale your application instances based on memory or CPU usage, response time, th

<a name="loioe6927e5af85e45f4a8a056c8662fa784__section_dtl_yfb_n4b"/>

## Metric Types **memory consumed** and **memory utilized**
## Metric Types: **memory consumed** and **memory utilized**

These scaling rules define that if the memory consumption either exceeds or falls below the set threshold, the application is respectively scaled up or down by an instance. If an array of scaling rules is defined, the Application Autoscaler runs periodic checks of the scaling policy to verify if any of the specified conditions matches. New instances are generated based on specified rules.

Expand Down Expand Up @@ -105,7 +105,7 @@ Metric Type **memory utilized**



## Metric Types **throughput** and **responsetime**
## Metric Types: **throughput** and **responsetime**

The following samples are simple scaling policies for the metric types **throughput** and **responsetime**. The scaling rule determines if the throughput or response time exceeds or falls below the set threshold.

Expand Down
Loading