AppDynamics CAAA flashcards
AppDynamics CAAA · Build recall with a focused review session.
32 cards. Read the term and the definition here. The deck at the top of this page is optional.
- Business Transaction
- A named unit of monitoring defined by entry-point match rules; it groups similar requests so response time, errors, and call graphs are measured together.
- Baseline deviation
- The number of standard deviations a live metric is from its learned baseline; alerts fire when deviation crosses a configured threshold.
- Automatic baseline
- A dynamic baseline that learns normal behavior over time and adapts to recurring patterns such as daily or weekly traffic cycles.
- Call graph
- A tree of the exit calls made while processing a transaction, showing downstream tiers and backends with their time and error contribution.
- Transaction snapshot
- A captured record of one slow or errored transaction, including its call graph, timing, and request data for diagnosis.
- Node health states
- A node is healthy, alerting, or unmonitored based on agent reporting and health rule evaluation; stopped nodes retain historical metrics.
- Percentile response time
- The response time below which a given percentage of transactions fall; the 95th percentile captures tail latency that averages hide.
- Exit call
- An outbound call from a monitored tier to a backend such as a database, HTTP service, or message queue; it appears in call graphs.
- Attack detection rule
- A pattern or signature matched against request data to identify injection, traversal, or scripting attacks on monitored transactions.
- Threat score
- An aggregate severity value computed from correlated attacks, weighing rule severity, confidence, and the business risk of affected transactions.
- Data exfiltration detection
- Detection that flags transactions sending unusually large or unusually destined outbound data compared with learned baselines.
- Security policy scope
- The set of applications, BTs, IP ranges, or environments to which a security policy applies; scoping reduces false positives.
- Blocking mode
- A security mode in which the agent actively denies matching requests; monitoring-only mode records and scores attacks without blocking.
- Sensitive data detection
- Pattern matching for PII such as credit card or social security numbers in request and response payloads, separate from injection rules.
- ABAP agent
- An SAP agent that instruments SAP GUI, RFC, and web entry points and reports dialog response time, work process use, and dumps.
- HANA monitoring
- Collection of SAP HANA database metrics such as CPU, memory, disk, and expensive SQL through the HANA SQL interface.
- SAP T-code naming
- Using SAP transaction codes and RFC destinations in match rules to map SAP workloads to meaningful business transactions.
- SAP short dump event
- An ABAP runtime error surfaced as an event in the controller, distinct from a business transaction error, indicating program failure.
- SAP agent connectivity
- The link between SAP agents and the controller; a lost connection creates a metric gap and triggers an agent-health alert.
- Browser RUM
- Real-user monitoring via a JavaScript agent that measures page render, AJAX, JavaScript errors, and end-user response time by segment.
- Synthetic monitoring
- Scheduled scripted browser or API checks run from selected locations to measure availability and response time without real users.
- Apdex formula
- Apdex = (satisfied + tolerating/2) / total, where satisfied is at or below target T and tolerating is between T and 4T.
- Page waterfall
- A breakdown of page load into DNS, connect, TLS, download, and render phases, separating front-end from back-end time.
- JavaScript agent injection
- Insertion of the EUM beacon script into monitored pages, which sends page and AJAX metrics to the controller.
- EUM to BT correlation
- Linking a browser page or AJAX request to the back-end business transaction snapshot so user slowness maps to server calls.
- Synthetic script step
- One action in a recorded browser journey, such as click or type; failures are reported per step with screenshots and timing.
- Machine agent
- A host-level agent collecting CPU, memory, disk, and network metrics, extensible with extensions for servers and middleware.
- Cluster agent
- An agent deployed to a Kubernetes cluster that collects pod, container, and node metrics and maps them to monitored applications.
- ADQL
- Analytics Query Language used to search transaction, log, and metric events; only fields defined in the schema are queryable.
- Data collector
- A configuration that extracts business data from request or method payloads and attaches it to transactions for analytics.
- Business journey
- A funnel built from analytics events that measures conversion and drop-off across defined stages of a user or order flow.
- Infrastructure health rule
- A rule that evaluates host, container, or analytics metrics and triggers actions such as email, SMS, or webhook when violated.