Discussion Feed

Hi Pavan, These are different measures. One URL will often trigger multiple calls on the server side. One would expect the number of HTML page hits to be proportional to the total number of application requests on the back end, but these numbers will rarely be equal.   Regards, ... View more

Hi Wesley, Please keep in mind that the Analytic Events have a short shelf life. They are normally purged after two weeks, so I would expect your Analytics Query to return the same result whether 2 weeks, or 2 months, or one year is queried. Rather than use an Analytics Query, your best bet is to use the metrics visible in the Metric Browser to do this calculation. These metrics are calculated from the Events every minute, and are aggregated and persisted for a year by default. An example Metric Path is: End User Experience|Geo|United Kingdom|Page Requests per Minute Use the REST API to fetch the "Sum" of this metric over the one year period for your calculation.   Regards, ... View more

The AppDynamics Controller manages a pool of licenses. When a new JVM is started with the -javaagent and -D agent terms, the agent will connect to the Controller and request a license. If a license is available, the JVM will come up instrumented and continue to report to the Controller until the JVM is shut down. The license will be released back into the pool within five minutes of the JVM shutdown. If a license is not available, the JVM will startup instrumented, but the agent will not collect or publish any data, but will continue to ping the Controller every minute to determine if a license is available. If a license becomes available, the agent will turn itself back on and start reporting metrics to the Controller.   License Management Scope configuration allows you to assign licenses to specific applications and machines. Using scopes to configure licenses allows you to express and scale the configuration modules as required. https://docs.appdynamics.com/display/PRO45/License+Management has details.     Another customer set up a Web Service that's called from the app server startup script with App Name, Tier Name, Node Name. The Web Service determines if the target JVM should be instrumented based on a local lookup, If the JVM should be instrumented, the Web Service will return the agent terms, -javaagent and -D's, and the JVM will start up instrumented. If the JVM doesn't match the criteria for instrumentation, the Web Service returns nothing and the JVM starts up without instrumentation.   Hope these two possible approaches help you, ... View more

Do you have an "All Other Traffic" bucket where the target BT may be grouped? If it was there, you would see it in the "View Traffic Details" dialog from the "All Other Traffic" BT dashboard.   Regards, ... View more

If you configured the transaction match exactly as you have described, it would fail because your match string has a space after "Web" that shouldn't be there. Regards, ... View more