How is auto scaling handled by the APM Insight agent?
When applications are scaling up, a request for creating a new instance comes from the agent. Depending upon the license availability, the new instance may be scaled up for monitoring.
Let's say your license limit allows you to monitor 3 advanced monitors. The following table illustrates the various scenarios w.r.t autoscaling in APM Insight:
Case
| Active instance
| Auto-suspended instance
| Autoscale scenario
|
1.
| All three instances are active.
| None
| In this case, a new instance will not be spawned for autoscaling since your license limit is already consumed completely.
|
2.
| Two instances are active
| One instance is auto-suspended because of scaling down
| Here, the auto-suspended instance will be reactivated.
|
3.
| One instance is active
| One instance is auto-suspended because of scaling down | The auto-suspended instance will be reactivated. After autoscaling, you can accommodate one more active instance in this scenario.
|
Note: When the instance is in down state for more than 5 minutes, it is automatically marked as Suspended. In case, if you had manually suspended your application, even when a new instance spans, it will still be in suspended state, unless changed manually.