Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
on 10-24-2018 12:35 PM - edited on 07-19-2024 02:09 PM by Ryan.Paredez
The licensing module is set up to run every five minutes to:
If an agent is up and connected to the Controller, it will try to consume a license. Agents will consume licenses on a first come, first served basis. For example, you may have five total Java Agent licenses available and all five are already being consumed, but you have two more agents trying to acquire the licenses. If one of the reporting agents stops reporting, a license will free up after five minutes and you will have one spot available. However, we cannot predict which of the two pending agents will consume that free license. To view your recent and historical license consumption, follow the instructions outlined here.
To read the complete details about the license management process, see the two resources linked below:
Starting with Controller v4.3+ (Still valid as of 24.x), disabled agents do not release licenses. Even if the agents have been disabled, some agents report data.
Example :
Java Agents will still report JVM and Garbage Collection-related metrics. .NET agents will report machine and hardware-related metrics, which consumes licenses.
On top of this, Agents always ping controller for health check. Any ping to controller will consume licenses.
To avoid this, you need to log into the host machine and take down the agent. For more complete instructions on disabling app agents, please see our official documentation.
We have detailed articles on two of our most commonly used APM licenses. For other agents, please refer to License Entitlements and Restrictions.
Last Updated: 2/25/19
How can a Windows service (Machine Agent or .NET Agent) continue communicating with a controller when it is successfully stopped? If that's the case, it seems like a design flaw that needs to be addressed by AppD APM development.
@Robert.Bratton it is likely that the agent is not stopped successfully. Please check
If you still have issues, please raise a support ticket along with tasks manager screenshots and agent logs.
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form