Discussion Feed

Added these images as attachments. ... View more

Hi Amritesh,   Two things to check: 1. There are a number of different types of Business Transactions. Some of these, like servlets and web services, have associated URLs. Others, like message driven requests, do not. Since the screenshot shows the BTs being bucketed in "CR_CatchAll", it's not clear that there should be URLs for these requests. The last snapshot in the screenshot does show the URL, so we know the URL is being collected in some cases. 2. The configuration to collect the URL is in the HTTP Data Collector section of the Configure/Instrumentation/Data Collectors page. The default HTTP Data Collector has the "URL" collection enabled, but this can be customized. Make sure that the HTTP Data Collector for this BT has URL collection enabled.   Regards, Brian Wheeldon ... View more

The Java agent runs inside the application server JVM, so there is inevitably some overhead. The AppDynamics Dev team has spent years minimizing this overhead and allowing customers to dynamically adjust the balance between collecting enough information to diagnose issues vs. collecting too much information and adding excessive overhead. For example, you mentioned the call graph providing method-level performance metrics across many major packages. The agent does this without instrumenting every method. In fact, typcially fewer than 1% of all application methods are instrumented.  You're also correct that collecting diagnostic snapshots is the highest overhead activity. This is why, by default, diagnostic snapshots are collected only for Error, Slow, Very Slow, and Stalled requests, plus a sample of one snapshot per Business Transaction every 10 minutes. This means that the vast majority of transaction executions are monitored, but no diagnostic snapshot is collected. Yes you can tune the number of snapshots collected by configuring Thresholds: https://docs.appdynamics.com/display/PRO43/Transaction+Thresholds It's common for performance teams to configure the Thresholds to minimize overhead in Production environment, while enabling more frequent snapshot collection in Pre-Prod environments.  ... View more

Hi Matt, You can configure which HTTP codes should/shouldn't be treated as an error in any AppDynamics application.  By default, AppDynamics captures HTTP error codes from 400 to 505. HTTP response codes may convey errors that occur at the business level of an application. For example, in an ecommerce application, a 522 error might indicate that an item is out of stock. For this case, you may want to exclude the error as a default transaction error indicator. To exclude a return code, add them to the error detection list by creating a custom error code range and then disabling that error code by clearing its   Enabled   checkbox. This in effect excludes the error code as an error indicator.   https://docs.appdynamics.com/display/PRO43/Error+Detection#ErrorDetection-DetectHTTPResponsesorRedirectPagesasErrors   ... View more

Hi Slavcho, You can choose a specific time range for each visualization with  "Use Widget Specific Time Range". It will be necessary to make this configuration for each widget (on the right side of your screenshot). Regards, Brian ... View more

I believe the .NET agent collects the Windows performance counter "System: %Total Processor Time" and reports it to the Controller as Application Infrastructure Performance|<Tier>|Individual Nodes|<Node>|Hardware Resources|CPU|%Busy   See https://docs.microsoft.com/en-us/sql/relational-databases/performance-monitor/monitor-cpu-usage for details. ... View more