PDFs


This page applies to an earlier version of the AppDynamics App IQ Platform.
See the latest version of the documentation.


On this page:

Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
47 rates

Metrics appear throughout the Controller user interface, including in the Metric Browser, Business Transactions list, and flow maps. 

While most metrics are self-explanatory, a few warrant additional explanation. This topic describes some of the metrics that you see in the AppDynamics UI.  

Common Metrics

The following metrics can be found in more than one location, such as the Business Transactions list, Node Dashboard, and Metrics Browser.

Block Time (ms), Average Block Time (ms)

Where found

  • Business Transactions > Business Transactions list > View Options > Slow/Stalled Requests > Block Time (ms)  
  • Metric Browser > Business Transaction Performance > Business Transaction Groups > group > business transaction > Average Block Time (ms)
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Average Block Time (ms)
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Average Block Time (ms) 

Description: Average wait time to get a lock. A high block time means there is often contention for the lock required for a thread to work on an object. Use thread dumps to diagnose lock contention problems and optimize application and JVM performance.  

Calls, Number of Calls 

Where found:

  • Tiers & Nodes > tier > Dashboard > Grid View > Calls
  • Tiers & Nodes > tier  >  node > Dashboard > Grid View > Calls
  • Business Transactions >  Business Transactions list  > View Options >  Key Performance Indicators > Calls
  • Troubleshoot > Slow Response Times > Slowest DB & Remote Service Calls > Number of Calls 

Description: Call volume, the total number of invocations of the entry point for all instances of the business transaction during the specified time from the node to the destination displayed. The more calls in your system, the busier it is. You might analyze the number of calls for system sizing.

Calls/min, Calls per Minute

Where found

  • Tiers & Nodes > tier  > View Dashboard > Grid View > Calls/min
  • Tiers & Nodes > tier  > node > View Dashboard > Grid View > Calls/min
  • Business Transactions > Business Transactions list > View Options > Key Performance Indicators > Calls/min 
  • Metric Browser > Business Transaction Performance > Business Transaction Groups > group > business transaction > Calls per Minute
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Calls per Minute
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Calls per Minute
  • Metrics Browser > Backends > Discovered backend call > Calls per Minute 
  • Metric Browser > Overall Application Performance > Calls per Minute 
  • Metric Browser > Overall Application Performance  > tier > Calls per Minute 
  • Metric Browser > Overall Application Performance  > tier >  Individual Node > node > Calls per Minute      

DescriptionThe average number of incoming or outgoing calls per minute during the specified time from the node to their destination. A decreased number of calls per minute may indicate problems processing transactions because of code, network or hardware problems and should be investigated further. You might also analyze the number of calls for system sizing purposes. 

A call, as represented by the calls per minute metric, can represent a somewhat different type of event depending on whether it is counted in the context of the application or tier. At the application level (i.e., Overall Application Performance), a call corresponds to a business transaction invocation. At the tier level, a call corresponds to individual invocations of services on that tier. Thus the number of calls per minute at a particular tier can exceed the number of calls per minute that is shown for the same time period at the application level, since a single execution of a business transaction can involve multiple calls to a single tier.       

CPU Used (ms), JVM CPU Burnt (ms/min)

Where found:

  • Business Transactions > Business Transactions list > View Options > CPU Usage > CPU Used (ms)
  • Tiers & Nodes > Show Data (Java) > Memory > JVM CPU Burnt (ms/min)

Description: AppDynamics obtains JVM CPU Burnt metrics via the OperatingSystemMXBean internal API. This is the amount of time the JVM used the CPU to process transactions monitored by the Java Agent.  The agent converts this forever-increasing metric into minute chunks. For the selected time range, JVM CPU Burnt indicates the average number of milliseconds of CPU time the JVM used for its processes in a minute. High CPU usage can degrade performance and may occur when the JVM memory settings are too low. If the heap setting is undersized for the application load, it can be quickly exhausted, triggering the JVM Garbage Collection (GC). If the JVM GC can't free enough memory, the JVM would then run again for just a short time before running out of memory again, triggering another JVM GC session. If the JVM GC session is running over and over again, CPU usage increases.

Note: Transactions monitored by agents other than the Java Agent may not present a meaningful metric in the CPU Usage column of the Business Transaction List.  

Errors/min, Errors per Minute

Where found

  • Business Transactions > Business Transactions list > View Options > Key Performance Indicators > Errors/min
  • Tiers & Nodes > tier > View Dashboard > Grid View > Errors/min
  • Tiers & Nodes > tier > node > View Dashboard > Grid View > Errors/min
  • Metric Browser > Business Transaction Performance > Business Transaction Groups > group > business transaction > Errors per Minute
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Errors per Minute
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Errors per Minute
  • Metric Browser > Overall Application Performance > Errors per Minute 
  • Metric Browser > Overall Application Performance  > tier > Errors per Minute
  • Metric Browser > Overall Application Performance  > tier >  Individual Node > node > Errors per Minute      

Description: Unhandled exceptions and any exception that prevents a business transaction from completing successfully are counted as errors. You can configure error detection to define the types of errors that the agent reports, so you see just those that are most useful for monitoring and troubleshooting your application environment. 

Response Time (ms), Average Response Time (ms), Avg. Time per Call

Where found

  • Business Transactions > Business Transactions list > View Options > Key Performance Indicators > Response Time (ms)
  • Tiers & Nodes > tier > node > View Dashboard > Response Time (ms)
  • Troubleshoot > Slow Response Times > Slowest DB & Remote Service Calls > Call Type > any > Avg. Time per Call 
  • Metric Browser > Business Transaction Performance > Business Transaction Groups > groupbusiness transaction > Average Response Time (ms)
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Average Response Time (ms)
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Average Response Time (ms)
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > External Calls > Average Response Time (ms)
  • Metric Browser > Backends > discovered backend call > Average Response Time (ms)   
  • Metric Browser > Overall Application Performance > Average Response Time (ms)
  • Metric Browser > Overall Application Performance  > tier > Average Response Time (ms)
  • Metric Browser > Overall Application Performance  > tier >  Individual Node > node > Average Response Time (ms)             

Description: Average response time (ART) spent processing all business transaction or call instances from start to finish. A high response time may indicate slow or stalled transactions, slow database or remote service calls, or problems with backends. Also examine the value for Normal Average Response Time (ms) in the Overall Application Performance and Business Transaction Performance sections of the Metric Browser

Slow Transactions, Number of Slow Calls

Where found

  • Business Transactions > Business Transactions list > View Options > Slow/Stalled Requests > Slow Transactions
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Number of Slow Calls
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Number of Slow Calls
  • Metric Browser > Business Transaction Performance > Business Transactions > tier > business transaction > External Calls > Number of Slow Calls

Description: The number of instances that meet the criteria defined for a slow transaction

Stalled Transactions, Stall Count 

Where found

  • Business Transactions > Business Transactions list > View Options > Slow/Stalled Requests > Stalled Transactions
  • Metric Browser >  Business Transaction Performance > Business Transaction Groups > group > business transaction > Stall Count 
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction >  Stall Count
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Stall Count

Description: Number of instances of this business transaction that meet the criteria defined for a slow transaction. If a transaction hits the stall threshold (takes more than 45 seconds or the set stall threshold to finish), a stall transaction event notification appears on the Events  because the transaction might take a very long time to eventually finish or time out.  Criteria for slow, very slow, and stalled transaction performance is determined by thresholds you define.  A high stall count impacts application performance and results in slow transactions. See Troubleshoot Slow Response Times. 

Very Slow Transactions, Number of Very Slow Calls 

Where found

  • Business Transactions > Business Transactions list > View Options > Slow/Stalled Requests > Very Slow Transactions
  • Metric Browser >  Business Transaction Performance > Business Transaction Groups > group > business transaction > Number of Very Slow Calls 
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction >  Number of Very Slow Calls
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Number of Very Slow Calls 

Description: Number of instances of this business transaction that meet the criteria defined for a slow transaction.

Wait Time (ms), Average Wait time (ms)

Where found

  • Business Transactions > Business Transactions list > View Options > Slow/Stalled Requests > Wait Time (ms)
  • Metric Browser >  Business Transaction Performance > Business Transaction Groups > group > business transaction > Average Wait time (ms)
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction > Average Wait time (ms)
  • Metric Browser >  Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node > Average Wait time (ms) 

Description: This metric displays the average time spent when invocations are in a thread sleep or wait state. Average wait time for a thread to process an object such as TIMED_Wait (sleeping while waiting for disk or network I/O, on object monitor), WAITING (parking) for a thread lock, and TIMED_WAITING (on object monitor). A high average wait time may be indicative of problems such as disk lock or network contention. Examine thread dumps to determine what the threads are waiting for. 

Business Transactions Metrics

AppDynamics displays all business transactions for a single business application on the Business Transactions list. Use these performance metrics to troubleshoot your business transactions

 

% Slow Transactions

Where foundBusiness Transactions > Business Transactions list > View Options > Slow/Stalled Requests

Description: Percentage of instances that are slow over the selected time frame.

% Stalled Transactions

Where foundBusiness Transactions > Business Transactions list > View Options > Slow/Stalled Requests

Description: Percentage of instances that stalled over the selected time frame.

% Very Slow Transactions

Where foundBusiness Transactions > Business Transactions list > View Options > Slow/Stalled Requests

Description: Percentage of instances that are very slow over the selected time frame.

Error %

Where found: Business Transactions > Business Transactions list > View Options >  Key Performance Indicators

Description: Percentage of instances of this business transaction that are errors.

Health

Where found: Business Transactions > Business Transactions list > View Options > Key Performance Indicators

Description: The health column shows red, yellow, or green icons for the health status of the business transaction. Click the icon to get more information. 

Max Response Time (ms)

Where found: Business Transactions > Business Transactions list > View Options > Performance Indicators

Description: Longest time spent processing an instance.

Min Response Time (ms)

Where found: Business Transactions > Business Transactions list > View Options > Performance Indicators

Description: Shortest time spent processing an instance.

Original Name

Where found: Business Transactions > Business Transactions list > View Options > Other

Description: Default name applied by AppDynamics. Business transaction identifier. If you renamed the business transaction, viewing the original name can be useful for debugging.

Spark charts

Where foundBusiness Transactions > Business Transactions list > View Options > Key Performance Indicators > Show Spark Charts

Description: Used to show the response time, calls per minute, and errors per minute as a graph over the selected time range.

Tier

Where foundBusiness Transactions > Business Transactions list > View Options > Other

Description: Display name of the originating tier for the business transaction. Business transaction identifier.

Type

Where foundBusiness Transactions > Business Transactions list > View Options > Other

Description: The types that are listed depends on the app agent (Java, .NET, PHP, and so on).  Business transaction identifier.

See Also

Errors/min, Errors per MinuteSlow TransactionsStalled TransactionsVery Slow TransactionsWait Time (ms)

Business Transaction Dashboard

AppDynamics displays summary statistics for a specific business transaction on the Grid View of the Business Transaction Dashboard.

Times Spent (ms)

Where found: Business Transactions > Business Transaction

DescriptionAverage time spent by the specific activity and any spawned asynchronous activities. Percentage metrics represent the fraction of time spent on a specific activity. Asynchronous activities do not have a percentage breakdown because each asynchronous activity is linked to the originating business transaction, but represents a separate logical entity throughout the execution of the business transaction.

Flow Map Metrics

Flow maps appear in several of the built-in dashboards in the UI, and show different information depending upon the context in which they appear. 

The Application Flow Map displays overall performance statistics for all Business Transactions. These metrics are based on all business transactions from a specific tier to another tier, and from tiers to backend systems such as database or remote service.

See Also

Response TimeCallsCalls/minErrors/min

Metric Browser Metrics

You use the metric browser to view, analyze and export metric data. For information on using the metric browser, see Metric Browser

AppDynamics metrics are organized into the following categories: 

Backends 

Backend monitoring provides key performance metrics for calls to databases and remote services. 

See Also

Calls per Minute

End User Monitoring 

End user monitoring (EUM) provides key performance metrics about your end users' experience starting from the users' Web browsers instead of at the application server. See Browser RUM Metrics. 

EUM metrics in the metric browser appear only if EUM is enabled for your application.

Mobile

See Mobile RUM Metrics.

Service End Points

See Service Endpoints.

Overall Application Performance 

Overall application performance metrics are displayed at application, tier, and node levels. Node-level metrics appear under individual nodes for each tier. Overall performance metrics include metrics for the external calls between two tiers, or between a tier and a database or remote service.

Overall Application Performance metrics are available at three different levels in the Metric Tree:

  • Overall Application Performance
  • Overall Application Performance  > tier
  • Overall Application Performance  > tier >  Individual Node > node

Note: Since the "Where found" information is the same for each Overall Application Performance metric, this information isn't repeated in the following descriptions.

Exceptions per Minute

Where found: Overall Application Performance

Description: An exception is a code-based anomalous or exceptional event, usually requiring special processing. Unhandled exceptions are errors and are not included in this count. Exceptions usually indicate underlying code problems and should be resolved as soon as possible.  

HTTP Error Codes per Minute 

Where found: Overall Application Performance

DescriptionHTTP errors include all HTTP calls done outside of a web service call that produced an error. HTTP errors usually indicate underlying code problems and should be resolved as soon as possible. 

Infrastructure Errors per Minute 

Where found: Overall Application Performance

Description:  Infrastructure errors include errors that occur outside the context of a business transaction.

For example, you create an information point on a method that generates an error but the information point point isn't part of a business transaction. The agent collects metrics related to the errors as infrastructure errors.

See Also

Average Response Time (ms)Calls per MinuteErrors per Minute  

Business Transaction Performance 

Business transaction performance metrics are available for the business transactions and groups of business transactions. The Metric Browser lists metrics for a business transaction under the tier where the business transaction is invoked. 

Most Business Transaction Performance metrics are available at three different levels in the Metric Tree: 

  • Business Transaction Performance > Business Transaction Groups > group > business transaction

  • Business Transaction Performance > Business Transactions > tier > business transaction

  • Business Transaction Performance > Business Transactions > tier > business transaction > Individual Nodes > node 

Note: Since the Where found information is the same for all Business Transaction Performance metrics, except those for the external calls, this information isn't repeated in the following descriptions.

The Metric Browser also displays metrics for external calls from the tiers.

  • Business Transaction Performance > Business Transactions > tier > business transaction > External Calls > call  

95th Percentile Response Time (ms)

Where foundBusiness Transaction Performance 

Descriptionpercentile is a value below which a given percentage of measurements in a set falls. For example, the Observed (Average) for a 95th percentile metric value of 150 ms means that 95% of all values are 150 ms or less. Using percentile metrics, you can discover outlying values for the response times for business transactions to answer questions such as, "What is the 95th percentile latency of transactions for the website during the last hour?" Depending on the nature of the business transaction and the value of the 95th percentile metric, the indication that the response times for 5% of the transactions exceed this value may be a cause of concern for the performance of your application. In addition to the default 95th percentile metric, you can configure other percentile metrics to display here.

Average CPU Used (ms)

Where found: Business Transaction Performance

Description: Displays the average time the business transaction spent using the CPU. An invocation of the business transaction might be in a wait state or be blocked when not using the CPU.

Average Request Size 

Where found: Business Transaction Performance

Description: HTTP request content length for each business transaction.

Normal Average Response Time (ms)  

Where found: Business Transaction Performance

Description: Average response time per minute of all instances except slow, very slow and stalled transactions.

See Also

Average Block Time (ms)Average Wait time (ms)Calls per MinuteErrors per MinuteNumber of Slow CallsAverage Response Time (ms)Stall CountNumber of Very Slow Calls

Application Infrastructure Performance

Application Infrastructure Performance metrics are displayed for the tier and for individual nodes:

  • Application Infrastructure Performance > tier 

  • Application Infrastructure Performance > tier > Individual Nodes > node 

Note: Since the Metric Browser hierarchy is the same for all Application Infrastructure Performance metrics, this information isn't repeated in the following descriptions.

Availability - App

Where found: Agent > App > Availability

Description: Application server (such as JVM) availability. The application server is available if it is reporting to the Controller. The application server may be running on more than one node and this metric reflects how many nodes the application server was running on. When the application server is shutdown or crashes, then its availability metric decreases. Be aware of how often and for how long your application server was down. Availability is a good indicator of server health. 

Availability - Machine

Where found: Agent > Machine > Availability

Description: The Controller reports the machine as available as long as the Standalone Machine Agent is reporting metrics. When the machine is not available, no metrics for your server are available. The machine may need to be restarted or there may be a networking problem preventing connection with the Controller. 

Events Exceeding Limits 

Where found: Agent > Event Upload 

Description: The number of events dropped due to the maximum number of events uploaded per minute for the agent was exceeded. No additional events are tracked for the rest of the minute at which time the event count starts over. You can see event details on the Events tab of the UI. Events are dropped based on the limits imposed by the events.buffer.size value and events.uploaded.per.min Controller settings. To ensure you are not missing event notifications, ensure that these Controller settings are set appropriately

Events Uploaded 

Where found: Agent > Event Upload

Description: Number of agent events that were uploaded. You can see event details on the Events tab of the UI. 

Invalid Metrics 

Where found: Agent > Metric Upload

Description: The number of metrics which were invalid and not accepted by the Controller. Each metric sent from the agent is validated by the Controller. An invalid metric is one for which the value for current, min, max, sum, or count is less than zero.  

Number of Application Infrastructure Changes Sent

Where found: Agent > ConfigChannel

Registration Failed

Where found: Agent > Business Transactions

Description: For the selected time range, indicates the number of unsuccessful registrations for the business transaction. New business transactions are posted to the Controller for registration every 10 seconds.  Registration failure may be because the registration limit for the Controller was reached. In this case, you may want to review the business transactions that you are currently monitoring and refine business transaction discovery for your agents. 

Registration Successful 

Where found: Agent > Business Transactions

Description: For the selected time range, indicates the number of successful registrations of new business transactions. New business transactions are posted to the Controller for registration every 10 seconds.  

Request License Errors 

Where found: Agent > Metric Upload

Description: The number of errors caused by a mismatch between the number of licenses and the maximum number of requests. The Controller setting, rsds.upload.limit.per.min controls the maximum number of requests that can be uploaded per minute per number of license units in the account. Ensure that this Controller setting is configured appropriately for your account. 

Time skews Errors 

Where found: Agent > Event Upload

Description: Number of event errors that occurred because of a difference between agent and controller timestamp and subsequently the events couldn't be uploaded or were not accepted by the Controller.  If the Controller receives metrics that are time-stamped ahead of its own time, the Controller reject the metrics. To avoid this possibility, maintain clock-time consistency throughout your monitored environment. 

Unmonitored Calls per Minute 

Where found: Agent > Business Transactions

Description: Number of business transactions which were not monitored by agent. Number of business transactions detected in excess of the business transaction limit. Instead of tracking all business transactions, by default AppDynamics tracks a max of 50 business transactions per node. When that limit is reached, AppDynamics tracks additional business transactions with this counter and reports them in the All Other Traffic category in the Application > Business Transactions list and in the Metric Browser as Unmonitored calls per minute.

Errors 

Error metrics for the specific errors are shown by tier and by individual node. The error names are the signatures AppDynamics generates for each exception, HTTP error, or internal agent error that is linked to a metric. 

Information Points 

Node Dashboard Metrics

AppDynamics displays summary statistics for calls on the Node Dashboard.

Errors 

Where found: Tiers & Nodes > tier > View Dashboard
                        Tiers & Nodes > tier > node > View Dashboard

Description: The number of errors experienced by the calls or business transactions during the specified time from the node to the destination displayed. Error configurations let you define the types of errors that the agent reports, so you see just those that are most useful for monitoring and troubleshooting your application environment. 

See Also

CallsCalls/min, Calls per Minute

Node Dashboard - Memory Metrics

Click the Memory tab of the Node Dashboard to see e memory metrics. 

GC Time Spent (ms/min)

Where found: Tiers & Nodes > tier > View Dashboard > Memory (Java)
                        Tiers & Nodes > tier > node > Show Data > Memory (Java)

Description: For the selected time range, indicates the average number of milliseconds used by the JVM during the JVM CPU Burnt time to compete Garbage Collection (GC). JVM GC time can negatively impact applications and services.  Tune GC management for each application or service.  If the GC Time Spent is high, it could indicate that the heap setting for the JVM is undersized for the application load and can be can be quickly exhausted, triggering the JVM GC. If the JVM GC can't free enough memory, the JVM would likely run again for just a short time before running out of memory again, triggering another JVM GC session. 

See also

CPU Used (ms), JVM CPU Burnt (ms/min)

 

  • No labels