To monitor end-to-end latency performance metrics, a Performance Analyst must first define the end-to-end latency transaction. This involves configuring the business transactions to include the necessary entry and exit points that capture the complete flow of the transaction, thereby enabling the measurement of the total latency.
References:
AppDynamics documentation on Business Transactions:
https://docs.appdynamics.com/latest/en/application-monitoring/business-transactions

The Metric Browser provides the authoritative metric hierarchy and can generate the REST URL corresponding to a selected Service Endpoint metric. A Performance Analyst first navigates to a representative Service Endpoint and metric, then copies the generated REST URL. The metric path in that URL can be modified with supported wildcard expressions to return matching metrics for all captured Service Endpoints or services within the application.
This method avoids manually constructing an unfamiliar metric path and ensures that the application identifier, metric hierarchy, time-range parameters, and REST endpoint syntax are correct. Wildcards allow the analyst to query multiple Service Endpoint names, tiers, or metric branches in one request.
Direct access to the Controller's underlying database is unsupported and bypasses the Controller API model.
The Applications browser is useful for interactive analysis but does not itself provide the most direct REST- query construction workflow. "Consumed Endpoints" is not the required location for enumerating all Service Endpoint metrics through the REST interface.
Relevant CAAPA Study Guide topics include Metric Browser, Service Endpoint Metrics, Metric Data REST API, Metric Paths, Wildcard Queries, and REST URL Generation.

The Transaction Score view in the Application Dashboard categorizes transactions by load, response time, errors, slow transactions, and stalled transactions. It provides an aggregated value for a specific time range, giving an at-a-glance indication of the health and performance of business transactions.
References:
AppDynamics documentation on Transaction Score: https://docs.appdynamics.com/latest/en/application- monitoring/application-dashboard

A database-specific KPI is created through Databases > Configuration > Custom Metrics. This area allows the Performance Analyst to define additional database measurements that are not included among the standard metrics collected by Database Visibility. A custom metric is typically based on a database query that returns a numeric value, such as queue depth, replication lag, application-specific record counts, storage utilization, or another operational indicator important to the organization.
After configuration, the Database Agent executes the metric query according to the defined collection interval and reports the resulting value to the Controller. The KPI can then be reviewed with other database metrics and incorporated into dashboards, health rules, baselines, and alerting policies.
The Metric Browser is used to inspect and analyze metrics already being collected; it is not the primary location for defining a new database custom metric. Application Instrumentation configures Application Agent transaction detection and code-level monitoring, while Slow Transaction Thresholds controls Business Transaction performance classification rather than database KPI creation.
Relevant CAAPA Study Guide topics include Database Visibility, Database Agent Configuration, Custom Database Metrics, Metric Queries, KPI Monitoring, Health Rules, and Metric Browser Analysis.

The "Method Invocation Data Collector" is specifically designed to capture code-level data such as method arguments, variables, and return values. This type of data collector enables deep visibility into the execution of methods within transactions, providing valuable insights into the application's behavior and performance. This detailed level of monitoring is essential for diagnosing complex issues and understanding the inner workings of business transactions.
References:
AppDynamics documentation on Data Collectors: Details the types of data collectors available, including Method Invocation Data Collectors, and how they can be used to capture detailed code-level data.