Service Endpoint Limits
A service endpoint adds a small amount of system overhead. Agents capture approximately three metrics per service endpoint, so monitoring each service endpoint results in additional metric traffic.
To prevent the possibility of a boundless expansion of service endpoints, the Controller and agent configurations apply these limits:
| Element | Limit | For more information |
|---|---|---|
| Application Agent | 25 service endpoints per entry point type | See max-service-end-points-per-entry-point-type
on App Agent Node Properties Reference. |
| Java Agent | 40 asynchronous worker thread service endpoints |
See |
| Node | 100 service endpoints | See max-service-end-points-per-node on App Agent Node Properties Reference. |
| Controller account | 4000 service endpoints | For an on-premises Controller, the limit is configurable using
the sep.ADD.registration.limit configuration
property accessible in the Administration Console. |
| Execution thread | 1 endpoint | See max-service-end-points-per-thread on App Agent Node Properties Reference. |
Custom Event for Service Endpoint Limits
ServiceEndpointEventManager, which dispatches a custom event
named appdynamics.sep.limit.breached when the specified percentage
of the total service endpoint limit for the account is reached. This property can be
configured at either the controller level or the account level. Ensure that you
create a policy on a long running application with this event to get alert. For more
information on how to create a policy, see Configure Policies.Account or Controller Property:
sep.account.limit.event.trigger.percentage
Type: Integer
Possible Values: Between 1 and 99
Priority: Account level property takes precedence over the Controller level property
Event Type: CUSTOM
Event Name: appdynamics.sep.limit.breached