AppDynamics CAAA key terms

A logical unit of work in an application, such as a login or checkout, defined by matching rules on entry points so that performance can be measured and compared consistently over time.

The tier and method or URI where a business transaction begins, such as a servlet, web service, or message consumer. Traffic is matched against entry points to decide which transaction it belongs to.

A captured record of one business transaction execution showing the call graph across tiers, with timing, exit calls, and errors, used for diagnosing where time was spent.

The hierarchical view inside a snapshot that shows methods, remote service calls, and asynchronous work as nested nodes with their own durations and percentages of total time.

An outbound dependency invocation made by a monitored tier, such as a database query, HTTP call, or message publish, that is timed and correlated to the downstream component.

A statistical model of normal performance for a metric, learned over a rolling time window and compared against current values to trigger anomaly-based health rule violations.

A baseline that adjusts for recurring patterns such as time of day and day of week, so that thresholds reflect expected load rather than a single flat number.

A configured condition, evaluated against metrics or baselines, that determines when an entity is warning or critical; violations drive events, policies, and alerts.

A rule that links a triggering event, such as a health rule violation, to actions like sending notifications, creating tickets, or running remediation scripts.

A record of something noteworthy that occurred in the monitored environment, including health rule violations, configuration changes, deployments, and custom events, shown on timelines.

Software installed on or attached to a monitored component, such as an application server, machine, or database, that collects metrics and transaction data and reports to the controller.

The central management server that receives data from agents, stores metrics and snapshots, applies configuration such as business transactions and health rules, and serves the web UI and APIs.

A group of identical application server instances that run the same code and are monitored together, forming one layer in the application topology.

A single monitored runtime instance, such as one JVM or one machine, that belongs to a tier and reports its own metrics and snapshots.

The hierarchy of business applications, tiers, and nodes that represents the monitored system and determines how metrics roll up for viewing and alerting.

Automatic discovery of downstream systems reached by exit calls, such as databases and remote services, so their performance can be tracked and correlated with callers.

A monitored or unmonitored downstream endpoint identified by exit calls, used to measure dependency latency and to detect problems originating outside the instrumented tier.

A named capture of method arguments, return values, or other runtime data at a specific method, used to enrich snapshots and support data collection for analytics.

A configuration that extracts specific values from requests, such as URLs, parameters, or headers, and publishes them as metrics or transaction properties for analysis.

The UI area for exploring the metric tree of an application or infrastructure entity, charting time ranges, and comparing values against baselines.

A numeric time series reported by agents or derived by the controller, such as average response time, calls per minute, or CPU usage, used for charts and health rules.

The runtime instrumentation component, typically a language-specific agent, that intercepts method calls to measure transactions, detect exit calls, and report snapshots and metrics.

The technique of modifying loaded classes at runtime to insert measurement hooks around methods, enabling transaction timing without changing application source code.

A standalone agent installed on a host that collects server-level metrics such as CPU, memory, disk, and network, and can run extensions for additional monitoring.

The infrastructure monitoring capability that tracks hardware and operating system health per machine and correlates it with application performance and tier behavior.

A collector that connects to database servers to gather performance and wait-state metrics, helping identify database-side causes of slow application transactions.

A query interface over stored transaction and log records that lets users filter, aggregate, and chart individual events rather than pre-aggregated metrics.

Collection and analysis of per-transaction records, including custom data, to support ad hoc queries, funnel analysis, and segmentation beyond standard metrics.

Ingestion and indexing of application log events so they can be searched, correlated with transactions, and used to build dashboards and alerts.

A defined sequence of business transaction steps that models a user flow end to end, enabling measurement of conversion, drop-off, and cumulative performance across steps.

A technique that counts how many users or sessions reach each successive step of a defined journey, revealing where drop-off occurs and which step performs worst.

Collection of performance and error data from actual end users' browsers via an injected JavaScript agent, measuring page load phases, AJAX calls, and client-side errors.

A small script injected into monitored web pages that measures browser-side timing, captures errors and AJAX activity, and reports beacons back to the controller.

Scheduled scripted browser or HTTP checks executed from locations worldwide to test availability and response time independently of real user traffic.

The measured duration for a browser page to render, often broken into phases such as network, server, and DOM processing, used to judge end-user experience.

Instrumentation of native mobile apps with an SDK that reports crashes, network requests, and screen-level performance from real devices to the controller.

The capability that observes runtime traffic to detect attacks and vulnerabilities, correlating security findings with the business transactions and tiers they affect.

Identification of malicious request patterns, such as injection or cross-site scripting attempts, in live traffic, producing security events tied to the affected application.

A weakness discovered in application code or libraries, such as unsafe input handling, that could be exploited and is tracked with severity and remediation status.

Configuration that determines which security detections are active, how traffic is evaluated, and what actions or alerts are produced when a threat is found.

Monitoring of SAP landscapes, including ABAP and Java stacks, to track dialog response times, background jobs, and system health alongside business processes.

The time an SAP system takes to respond to an interactive user request, a key indicator of user experience and system load in SAP monitoring.

A short identifier used in SAP systems to launch a specific function or program, often used to categorize and monitor business activity performance.