Autoscaling in APM Insight

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. 

    • Related Articles

    • How to identify and resolve conflicts between other APM products and the APM Insight .NET agent

      Problem statement: You are experiencing either of the below issues and suspect that another APM product is interfering with the Site24x7 .NET agent. 1. The .NET monitor is not created under APM > APM Insight > Applications, even after the .NET agent ...

    • APM Insight integration for Next.js in Kubernetes

      To integrate the Site24x7 APM Insight Next.js agent into your Kubernetes application using initContainers with the prebuilt agent image, follow the steps below: Prerequisites A Next.js application container image The Site24x7 APM Insight license key ...

    • Bundled .NET and .NET Core agents in a single MSI

      In APM Insight .NET agent version 6.8.0, the .NET and .NET Core agents have been bundled into a single MSI, enabling unified monitoring of both application types. Upgrade requirements for .NET Core agent 6.7 and below If you're using .NET Core agent ...

    • Steps to troubleshoot if you see "NO Data" in the Node VM tab

      Problem statement: You are getting No Data under the garbage collection and event loop graphs such as GC Pause Time, GC Pause Frequency, and Event Loop Ticks Per Minute. Prerequisite: The Node.js agent version should be 3.0.0 or higher. Solution: The ...

    • Prerequisites for Node.js agent installation

      For a smooth Node.js agent installation, ensure that you've fulfilled the following prerequisites. The environment should have node version 16.20.2 or above installed. The application user should have full permission to access the agent directory. ...