Click the Start a free trial link to start a 15-day SaaS trial of our product and join our community as a trial user. If you are an existing customer do not start a free trial.
AppDynamics customers and established members should click the sign in button to authenticate.
We are often hitting a bytecode limit in AppDynamics. There are examples of this in the production logs (officially undocumented that this is an issue):
[TimeseriesDispatcher] Method excluded because Cannot instrument class com/..../oet/server/services/instrument/history/TimeseriesServiceImpl$TimeseriesUpdater for interceptor class com.singularity.ee.agent.appagent.services.transactionmonitor.c because maximum 50 transformations exceeded for package prefix com....
So what should be done to avoid this limit
kindly help me in this
Sorry to hear that you are experiencing bytecode issue on the AppDynamics Controller. To dig into the issue, would you mind sharing some insights, such as the version of Controller you are using, type of deployment (upgrade or fresh install), version of the Agents, and any other info which is not confidential.
thanks for your reply,
controller version - 184.108.40.206, build 220.127.116.1177
Agent version - 18.104.22.168
FYI, Its not a fresh install
And as per my knowledege
to avoid those limit we can add below mentioned agent property :
The above mentioned property lets the bytecode instrumentation engine detect more remote services or service endpoints automatically.
Is my finding correct???
The package qualifiers limit increase should resolve the issue.
We will need agent logs to investiagte why this has not happened in your case; the best way to share these would be via a support ticket.