Node Drill Down

The node drill down organizes diagnostic data among these tabs:

• The Overview tab includes a problem summary, execution times, CPU time stamp, tier, node, process ID, thread name, etc.
• The Call Graphs tab lists call graphs showing the execution flow for the transaction on a given tier. For details, see Call Graphs.
• The Slow Calls and Errors tab lists all the slow method calls and calls that resulted in an error. You can use the Hot Spots slider to sort calls by execution time with the most expensive calls in the snapshot at the top.
• The Error Details tab exposes exception stack traces and HTTP error codes.
• The DB & Remote Service Calls tab shows all SQL query exit calls to databases and exit calls to other remote services such as web services, message queues, or caching servers. See Database queries and batching for more information about how Splunk AppDynamics handles SQL exit calls.
• The Server tab displays graphs for hardware—CPU Memory, Disk IO, Network IO— Memory—Heap, Garbage Collection, Memory Pools—JMX, and more. If you have Server Visibility, you will have access to full performance details for the server hardware and operating system
• The complete detail is unavailable when you continue with transaction snapshots on the transactions such as, Java POJO business transaction. For example, it may not display example URL, session ID, thread name, and so on.
• For customers using Network Visibility, the Network tab shows charts related to the impact of the network on the transaction and other pertinent data. For information on network KPIs and troubleshooting see KPI Metrics in Network Dashboard and Application Flow Map and KPI Metrics in Right-Click Dashboards.
• The Data Collectors tab shows pertinent application data for the transaction snapshot. For configuration options, see Data Collectors.

  HTTP Data

  HTTP payloads contain basic data such as the URL and session ID, and additional data for Servlet entry points, Struts, JSF, Web Services, etc. You can use HTTP data collectors to specify which query parameter or cookie values should be captured in the transaction snapshot.

  Cookies

  The snapshot can use cookie values to help identify the user who initiated the slow or error transaction.

  User Data

  User data from any method executed during a transaction, including parameter values and return values, to add context to the transaction. You can use method invocation data collectors to specify the method and parameter index.In cases where an exit call is made just before a business transaction starts, exit call information can show up in this field, particularly if the transaction is marked as slow or having errors. Please note that sensitive information on the exit call may be shown in this situation.

• The More tab shows how metrics for the node that deviate the most from the established baselines as Node Problems. It also shows all the Service Endpoints invoked during the snapshot and the Servlet URI and Process ID of the transaction.

Database Queries and Batches

Splunk AppDynamics normalizes SQL queries and by default does not display raw/bind values. You can configure SQL capture settings to monitor raw SQL data in the queries. Individual calls that take less than 1 second are not reported.

When returning data to a JDBC client, database management systems often return the results as a batched response. Each batch contains a subset of the total result set, with typically 10 records in each batch. The JDBC client retrieves a batch and iterates through the results. If the query is not satisfied, the JDBC client gets the next batch, and so on.

In the SQL query panel, a number followed by an X in the Query column means that the query ran the number of times indicated within a batch. The value in the Count column indicates the number of times that the batch job executed.

Database Drill down

Database drill downs provide this transaction information:

Queries

Lists the queries consuming the most time in the database as top SQL statements and Stored Procedures. Comparing the query weights to other metrics such as SQL wait times may point you to SQL that requires tuning.

Clients

Displays the hostname or IP addresses of the Top N clients using the database. A database client is any host that accesses the database instance.

Sessions

Displays the Session ID of the Top N sessions using the database sorted by time spent.

Schemas

Shows the names of the Top N busiest schemas on the database server.