Step 4: Drill into SQL or Remote Service Calls to determine the root cause.

  1. Slow database call – click the database call to gain information about the call.
    1. If you have Correlated snapshots between Java applications and Oracle databases – drill down into the Oracle database on the Transaction Snapshot to view database details captured during the snapshot.
    2. If you have Splunk AppDynamics for Databases – right-click the database on the Application, Tier, Node or Backend Flow Map, and choose Link to Splunk AppDynamics for Databases. You can use Splunk AppDynamics for Databases to diagnose database issues.
    3. If you have Database Monitoringri ght-click the database on the Application, Tier, Node or Backend Flow Map, and chooseViewto review database problems.On the SQL Calls tab of the transaction snapshot, sort the SQL Calls by Avg. Time (ms).
  2. On the Remote Service Calls tab, sort the queries by Avg. Time (ms).
  3. Select the slow call.
  4. Click Drill Down intoDownstream Callto gain further insight into the methods of the service call.
  5. Sort the methods by theTime (ms)column.
  6. Select a slow method.
  7. ClickDetails.