> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Fix Auto-Scaling Issues

You can configure [Atlas auto-scaling alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-autoscaling) and alert conditions in the project [alert settings](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) modal. You can also view auto-scaling events in the [project's Activity Feed.](https://www.mongodb.com/docs/atlas/tutorial/activity-feed.md#std-label-view-activity-feed)

**Important:**

Auto-scaling alerts apply to all clusters in a project. You cannot scope alerts to specific clusters. Alert notifications identify which cluster triggered the event by cluster name and ID.

## Alert Conditions

To trigger alerts, you can configure the following alert conditions in the project-level [alert settings](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-alerts) page.

- [`Auto-scaling: Compute auto-scaling initiated for base tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-initiated-for-base-tier) occurs if Atlas starts compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster. Atlas can scale disk capacity as part of this event.

- [`Auto-scaling: Compute auto-scaling initiated for analytics tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-initiated-for-analytics-tier) occurs if Atlas starts compute auto-scaling for any of the [analytics nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) in your dedicated cluster. Atlas can scale disk capacity as part of this event.

- [`Auto-scaling: Compute auto-scaling down didn't initiate for base tier due to storage requirements`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-down-didn-t-initiate-for-base-tier-due-to-storage-requirements) occurs if Atlas couldn't start compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster as the configured storage size isn't supported by the target cluster tier.

- [`Auto-scaling: Compute auto-scaling down didn't initiate for analytics tier due to storage requirements`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-down-didn-t-initiate-for-analytics-tier-due-to-storage-requirements) occurs if Atlas couldn't start compute auto-scaling for any of the [analytics nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) in your dedicated cluster as the configured storage size isn't supported by the target cluster tier.

- [`Auto-scaling: Compute auto-scaling didn't initiate for base tier due to maximum configured cluster tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-base-tier-due-to-maximum-configured-cluster-tier) occurs if Atlas couldn't scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) because your cluster reached a maximum cluster tier configured for auto-scaling.

- [`Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to maximum configured cluster tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-analytics-tier-due-to-maximum-configured-cluster-tier) occurs if Atlas couldn't scale up an [analytics node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) because your cluster reached a maximum cluster tier configured for auto-scaling.

- [`Auto-scaling: Compute auto-scaling didn't initiate for base tier due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-base-tier-due-to-insufficient-oplog-size) occurs if Atlas couldn't scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window)

- [`Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-analytics-tier-due-to-insufficient-oplog-size) occurs if Atlas couldn't scale up an [analytics node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-analytics-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window)

- [`Auto-scaling: Predictive compute auto-scaling initiated for base tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Predictive-compute-auto-scaling-initiated-for-base-tier) occurs if Atlas starts predictive compute auto-scaling for any of the [operational nodes](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) in your dedicated cluster.

- [`Auto-scaling: Predictive compute auto-scaling did not initiate for base tier due to maximum configured cluster tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Predictive-compute-auto-scaling-did-not-initiate-for-base-tier-due-to-maximum-configured-cluster-tier) occurs if Atlas couldn't predictively scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) because your cluster reached a maximum cluster tier configured for auto-scaling.

- [`Auto-scaling: Predictive auto-scaling did not initiate for base tier due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Predictive-auto-scaling-did-not-initiate-for-base-tier-due-to-insufficient-oplog-size) occurs if Atlas couldn't predictively scale up an [operational node](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-operational-node) due to insufficient [oplog](https://www.mongodb.com/docs/manual/reference/glossary.md#std-term-oplog) size. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window)

- [`Auto-scaling: Disk auto-scaling initiated`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-initiated) occurs when Atlas starts auto-scaling disk capacity.

- [`Auto-scaling: Disk auto-scaling didn't initiate due to the cluster reaching maximum available disk size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-didn-t-initiate-due-to-the-cluster-reaching-maximum-available-disk-size) occurs if Atlas couldn't scale up the disk size because the cluster has reached maximum available disk size.

- [`Auto-scaling: Disk auto-scaling didn't initiate due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-didn-t-initiate-due-to-insufficient-oplog-size) occurs if Atlas couldn't scale up the disk size because the cluster's oplog size isn't sufficient. To learn more, see [Set Minimum Oplog Window.](https://www.mongodb.com/docs/atlas/cluster-additional-settings.md#std-label-set-oplog-min-window)

## Common Triggers

Auto-scaling alerts occur by default for your cluster when Atlas triggers them. You can change who receives these alerts and their distribution. To learn more about how auto-scaling behaves, see [Auto-Scaling for Atlas Clusters.](https://www.mongodb.com/docs/atlas/cluster-autoscaling.md#std-label-cluster-autoscaling)

Automatic scaling might not occur when a cluster receives a burst of activity, such as a bulk insert. To reduce the risk of running out of resources during automatic scaling up events, monitor your cluster during bulk inserts and other workload spikes.

## Fix the Immediate Problem

If your cluster nodes run out of memory or disk space, you can [upgrade your cluster](https://www.mongodb.com/docs/atlas/scale-cluster.md#std-label-scale-cluster-instance) to fix the immediate problem. You can select a cluster tier with more memory, storage, and IOPS (Input/Output Operations per Second).

## Monitor Your Progress

See [Monitor cluster metrics.](https://www.mongodb.com/docs/atlas/monitor-cluster-metrics.md#std-label-monitor-cluster-metrics)