The EUM Server (on-premises/SaaS) can process a maximum of 2000 network request types per mobile app group and 500 network requests per mobile application.
If the number of network requests for an application exceeds one of these limits, AppDynamics continues to monitor network requests that have already been discovered, but new network requests will not be discovered. Should a limit be exceeded, a warning appears on the network request list.
You can use these techniques to keep your usage under the two network request limits.
Remove Network Requests Without Load
Removing network request types that have been discovered but are not receiving any load is a good place to start to reduce the number of your registered requests.
Deleting network requests does not prevent them from being re-discovered in the future if the request once again comes under load. To prevent specific network requests from ever being discovered, you must create exclude rules. See the section "Creating Mobile Exclude Rules" in Configure Mobile Network Request Naming.
Delete network requests with no load
- In the Network Requests list, uncheck the With Load checkbox.
- Refresh the list.
- Find the requests that have no load. They are candidates for removal.
- Select the requests that you want to delete.
- In the More Actions dropdown, click Delete Request(s).
Exclude Requests That Do Not Need to Be Monitored
The Mobile Agent may be detecting network requests types that are not interesting for you to monitor. You have two methods to exclude these types of network requests.
The first method is to add custom exclude rules from Configuration > Mobile Request Naming, Thresholds, & Percentiles. See Creating Mobile Exclude in Rules for explicit instructions.
Using custom exclude rules, network requests for new data that match the exclude rules will not be registered. The load on the existing network requests that match the exclude rule will drop to zero. To delete any network requests of the excluded type that have already been registered from the network request list, follow the procedure described in Delete network requests with no load.
The second method is to select an existing network request from the Network Requests list and then exclude it. This will change the app's exclude rules so that incoming data matching that request will not be tracked. In addition, the historical data for that request will be deleted.
To use the second method for the exclude rules that prevent a network request from being tracked and remove historical data for that network request:
- From Network Requests, select the network request you want to exclude.
- Click Actions > Exclude Requests to open the Exclude Requests dialog.
- Click Exclude.
Group Network Requests of Similar Type
Review the default network request naming rule described in Configure Mobile Network Request Naming. It is possible that the default rule is generating many more network requests types than are desirable.
For example, perhaps your application loads images dynamically and stores them on your server with URLs like
. This would cause a separate network request to be generated for each image, which is probably not what you want. You could create a custom naming rule to group all the image URLs as a single network request. See Configure Mobile Network Request Naming.
After you have created custom rules to reduce the number of network requests detected, unregister the network requests for those are now covered by the custom rule, following the procedure described in Delete network requests with no load.