DevOps / AppDynamics Interview questions
1. Explain AppDynamics.
AppDynamics is an Application Performance Monitoring (APM) and observability platform that watches how software behaves in production — tracking response times, error rates, and resource usage down to the individual method call. It was acquired by Cisco in 2017, and following Cisco's acquis...
2. What is Appdynamics?
The AppDynamics Business iQ tool assists in the creation of dashboards that automatically link application performance to business outcomes. AppDynamics provides a streamlined, integrated solution for visualizing, monitoring, and managing all of your application's components.
3. What is Application Performance Monitoring (APM)?
Application Performance Monitoring is the practice of measuring and analyzing how well software performs while it's actually running, so teams can detect slowdowns, errors, and capacity problems before — or as soon as — they affect users. A typical APM tool like AppDynamics tracks a c...
4. What are agents and the controller in AppDynamics?
AppDynamics agents are plug-ins or extensions that monitor the performance of your application code, runtime, and behavior. Theyre deployed to every corner of your application environment, from devices to containers and hosts, to applications. The AppDynamics controller receives metrics from age...
5. What are the core components of the AppDynamics platform?
AppDynamics is built from a small set of cooperating pieces: agents that collect data, a Controller that stores and analyzes it, and a UI/API layer teams use to act on it. Component Role App Agent Instruments application code (Java, .NET, Node.js, PHP, Python) to capture transactions Machine Agen...
6. Why is AppDynamics used?
AppDynamics provides a great amount of detail and insight to solve performance problems by using APM Tools and an analytics-driven approach. AppDynamics, the Application Performance Management (APM) solution baselines, monitors, and reports on the performance of all transactions that flow through...
7. What is the Controller in AppDynamics?
The Controller is the central server that every AppDynamics agent reports to. It receives incoming metrics and transaction data, stores it, evaluates health rules against it in near real time, and serves the web UI and REST API that teams use to view dashboards, flow maps, and alerts. It can run ...
8. What is OpenTelemetry in Appdynamics?
OpenTelemetry is a new framework for improved observability that allows you to standardize how telemetry data, such as logs, metrics, events, and traces, are gathered and delivered to your preferred backend platform. OpenTelemetry, as an emerging standard for cloud-native monitoring, will extend ...
9. What is an App Agent in AppDynamics?
An App Agent is the piece of AppDynamics that runs inside the actual application process — the JVM for Java, the CLR for .NET, the Node.js runtime, and so on — and instruments the code without requiring source code changes. For managed runtimes like Java and .NET, it works by injectin...
10. What is Unified Monitoring in AppDynamics?
AppDynamics Unified Monitoring is the industry's first application-centric, integrated monitoring platform that traces every transaction, both synchronous and asynchronous, from end user through the entire application environment. It's built to work as one solution, with one UI, one data platform...
11. What is a flow map in Appdynamics?
Flow maps present a dynamic visual representation of the components and activities of your monitored application environment. Flow maps show the tiers, nodes, message queues, and databases in the environment, and the business transactions that flow through them.
12. What are the types of agents available in AppDynamics?
AppDynamics ships several agent families, each targeting a different layer of the stack, and most production deployments run more than one type side by side on the same host or application. Agent Type Monitors App Agents (Java, .NET, Node.js, PHP, Python, C/C++ SDK) In-process application code an...
13. What is a Business Transaction in AppDynamics?
A Business Transaction (BT) is a named, trackable unit of work — typically a specific request type like /checkout or /login — that AppDynamics follows from its entry point through every tier it touches, until the response is returned. Rather than showing raw, undifferentiated traffic,...
14. What is Appdynamics node?
A node is the basic unit of processing that AppDynamics monitors. An app agent or machine agent or both instrument a node. Nodes belong to tiers. Service endpoint. Service endpoints provide a subset of the metrics for a tier, focused on a specific application service.
15. What is a Tier in AppDynamics?
A Tier is a logical grouping of one or more Nodes that perform the same role within an application — for example, every instance of your checkout service, regardless of how many servers it's running on, forms a single "Checkout Service" tier. AppDynamics automatically groups nodes into the ...
16. What is Galileo suite?
The Galileo Suite is the ultimate enterprise-level monitoring solution with interactive 3D visualizations and controls that help to quickly understand and assess your environment/infrastructure and analyze its health. Automatic discovery and correlation of monitored assets allow you to immediatel...
17. What is a Node in AppDynamics?
A Node is the smallest unit AppDynamics monitors: a single instance of an application process with an agent attached to it, such as one JVM, one .NET worker process, or one Node.js process. Each node gets a unique name in the Controller, often following an
18. What is a Business Application in AppDynamics?
A Business Application is the top-level container in AppDynamics' monitoring hierarchy — it represents an entire application end to end, made up of all the tiers (and their nodes) that participate in serving it, such as a web tier, an API tier, and a payments tier grouped under one e-commer...
19. What is the Application Flow Map?
The Application Flow Map is a live, auto-generated diagram showing how traffic actually moves through a business application — every tier drawn as a node, with arrows for calls between tiers and out to backends like databases, caches, or third-party services. Each connection is annotated wi...
20. What is a Health Rule?
A Health Rule is a condition AppDynamics continuously evaluates against live metrics — for example, "average response time exceeds 3 standard deviations above baseline for 5 minutes" — that puts a Business Transaction, tier, or node into a Warning or Critical health state when it's vi...
21. What is a Policy in AppDynamics?
A Policy connects a triggering condition — most commonly a health rule violation, but also events like a deployment or a specific error — to one or more Actions that should run automatically when that condition occurs. Actions can include sending an email, posting to a chat tool like ...
22. What is a Transaction Snapshot?
A Transaction Snapshot is a detailed, point-in-time capture of one specific execution of a Business Transaction — not an aggregate metric, but the actual call graph for that single request: every method call, database query, and remote call it made, each with its own timing. Snapshots are t...
23. Define baseline in AppDynamics?
A baseline is AppDynamics' learned model of "normal" performance for a specific metric — typically a Business Transaction's response time — built from historical data rather than a single fixed number a person has to guess and set. Baselines are calculated per time window (for example...
24. What is the Machine Agent used for?
The Machine Agent runs on the host operating system, separately from any application process, and reports hardware and OS-level metrics: CPU utilization, memory usage, disk I/O, and network throughput for the server it's installed on. It's available for most common operating systems (Windows, Lin...
25. What is End User Monitoring (EUM)?
End User Monitoring captures how an application actually performs from the perspective of the person using it — in the browser or on a mobile device — rather than only measuring server-side response time. It has two real-traffic modes and one simulated mode: Browser RUM injects a Java...
26. What is Database Visibility in AppDynamics?
Database Visibility, delivered through the Database Agent, monitors the performance of the database servers your application depends on — separate from, but correlated with, the application-side view of how long a query took from the app's perspective. It tracks database-level metrics like ...
27. What are Backends in AppDynamics?
A Backend is any downstream dependency a Business Transaction calls that AppDynamics doesn't have an agent installed on — a database, a cache like Redis, a message queue, a third-party REST API, or another internal service without its own App Agent. AppDynamics detects these automatically a...
28. Describe the Metric Browser in AppDynamics?
The Metric Browser is the Controller UI screen for browsing and plotting the raw metrics AppDynamics collects, organized in a tree structure by application, tier, node, and metric category, rather than pre-packaged into a fixed dashboard. It's useful when a default dashboard doesn't show the exac...
29. What is the difference between a Tier and a Node in AppDynamics?
These two terms describe different levels of AppDynamics' monitoring hierarchy, and mixing them up is a common source of confusion for people new to the platform. Tier Node A logical group representing one application role (e.g. "Order Service"). A single running instance of that application, e.g...
30. How does AppDynamics automatically discover Business Transactions?
AppDynamics ships with built-in automatic discovery rules per supported framework and entry point type — servlets, EJBs, web services, message listeners, and similar — that watch incoming traffic and name a new Business Transaction the first time they see a distinct entry point patter...
31. What is the difference between automatic and custom Business Transaction match rules?
Both approaches decide how incoming requests get grouped into named Business Transactions, but they trade off setup effort against precision. Automatic Discovery Custom Match Rules Built in, requires no configuration to start. Explicitly authored by a team member. Can over-generate BTs on high-ca...
32. How does AppDynamics correlate a transaction across multiple tiers?
When a request enters the originating tier, the App Agent generates a unique identifier for that transaction instance and carries it forward as the request calls into downstream tiers, so every tier's activity for that one request can later be reassembled into a single, cross-tier view. sequenceD...
33. Why is the singularityheader important in transaction correlation?
The singularityheader is the HTTP header AppDynamics uses to carry a transaction's correlation identifier from one tier to the next, and it's the specific mechanism that makes cross-tier distributed tracing possible instead of each tier only ever reporting isolated, disconnected metrics. When the...
34. How does AppDynamics decide when to capture a transaction snapshot?
Rather than recording every single execution of every Business Transaction — which would be far too much data — AppDynamics captures snapshots selectively, triggered by specific conditions on either the originating or a continuing tier. Trigger What it Means Slow Response time exceeds...
35. What is dynamic baselining and how does it work?
Dynamic baselining is the statistical process AppDynamics uses to continuously learn what "normal" looks like for a metric — most often a Business Transaction's response time — instead of relying on a static threshold someone has to guess and maintain by hand. It works by collecting h...
36. Why does the Java Agent use byte-code instrumentation?
Byte-code instrumentation lets the Java Agent add monitoring logic — timing a method, capturing a database call, injecting a correlation header — into a running application without ever touching or recompiling the application's actual source code. The alternative approaches are both w...
37. Explain the internal working of AppDynamics' byte-code instrumentation?
When the Java Agent starts, it registers a Java agent premain hook (the standard JVM instrumentation API) that gets control before the application's own classes finish loading, giving it the chance to modify bytecode on the fly rather than after the fact. sequenceDiagram participant JVM participa...
38. What is a Service Endpoint in AppDynamics?
A Service Endpoint lets you track a specific method call inside a Business Transaction as its own separately-measured unit — for example, one particular internal service call buried deep inside a larger transaction — without having to make it a whole new Business Transaction of its ow...
39. What is an Information Point?
An Information Point lets you turn the return value or a parameter of any method call into a custom metric, even if that method has nothing to do with entry points, exit points, or Business Transactions at all. You configure it by pointing at a class and method (similar to a Service Endpoint's ma...
40. What is a Data Collector in AppDynamics?
A Data Collector captures extra context alongside a transaction snapshot — an HTTP header value, a request parameter, a piece of business data passed as a method argument, or a JMX attribute — so that when you're looking at a slow or errored snapshot, you can see not just the timing b...
41. When should you use custom match rules instead of automatic discovery?
Custom match rules earn their configuration cost specifically when automatic discovery's default behavior produces a Business Transaction list that's either too noisy, too coarse, or misaligned with how the business actually thinks about its own critical flows. High-cardinality URLs: paths like /...
42. What is the difference between Slow, Very Slow, and Stalled transactions?
These three categories describe increasingly severe response-time problems AppDynamics detects for a Business Transaction, and each maps to a different snapshot trigger and typically a different severity of health rule violation. Category Meaning Slow Response time exceeds baseline by a configure...
43. How does AppDynamics calculate Average Response Time (ART)?
Average Response Time is the mean elapsed time, in milliseconds, from when a Business Transaction's entry point begins executing to when it returns a response, averaged across all the calls to that Business Transaction within the selected time window. Every individual execution the agent observes...
44. What is the difference between the Machine Agent and the Network Agent?
Both agents run at the host level rather than inside an application process, but they observe different layers of what's happening on that host. Machine Agent Network Agent Reports OS/hardware metrics: CPU, memory, disk, uptime. Reports TCP-level network metrics between tiers. Extensible via shel...
45. What is an Adaptive Session in AppDynamics?
An Adaptive Session (sometimes called a Diagnostic Session) is a temporary, more aggressive data-collection mode AppDynamics switches a Business Transaction into when it detects a recurring or worsening performance pattern, rather than relying on the normal, lighter sampling used during healthy o...
46. What is a thread dump and when does AppDynamics capture one automatically?
A thread dump is a snapshot of every thread running inside a JVM (or similar runtime) at a specific moment, showing each thread's current state and full stack trace — which is exactly the data needed to see what a stalled or deadlocked application is actually stuck doing. AppDynamics can tr...
47. How would you troubleshoot a suspected memory leak using AppDynamics?
AppDynamics won't point at the exact leaking object automatically, but it gives you the signal that narrows where to look and the tooling to confirm it, rather than guessing blind. Spot the trend: in the Metric Browser, watch heap usage (or a specific memory pool) over hours or days — a lea...
48. What are custom extensions for the Machine Agent?
Custom extensions let the Machine Agent collect and report metrics beyond its built-in hardware set — anything a shell script, Java program, or other executable can measure and print in the expected format, the Machine Agent can pick up and forward to the Controller as a regular metric. Mec...
49. How does the Cluster Agent monitor Kubernetes environments?
The Cluster Agent runs as its own pod inside a Kubernetes cluster and talks to the Kubernetes API server to collect cluster-level state and events — pod status, deployments, node conditions, and resource utilization — giving visibility into the orchestration layer itself, on top of wh...
50. What is the difference between SaaS and On-Premises Controller deployments?
Both deployment modes run the same core Controller software, but they differ in who operates the infrastructure and what that implies for maintenance, scaling, and data residency. SaaS Controller On-Premises Controller Hosted and operated by Cisco/Splunk. Installed and operated inside the custome...
51. How can you reduce AppDynamics agent overhead in a production environment?
Agent overhead in AppDynamics is generally low by design, but on very high-throughput or latency-sensitive services, a few concrete levers exist to trim it further without losing the visibility that matters most. Tune snapshot thresholds: if the slow/very-slow thresholds are too aggressive, the a...
52. What is Business iQ / Analytics in AppDynamics?
Business iQ (delivered through the Analytics Agent and Analytics UI) lets teams query and visualize transaction and log data using business-relevant dimensions — things like promo code, customer segment, or product SKU — rather than only the technical dimensions (tier, node, response ...
53. How does AppDynamics integrate with ITSM tools like ServiceNow or PagerDuty?
AppDynamics integrates with ITSM and incident-management tools primarily through Policy Actions: when a health rule violation (or another triggering event) fires a policy, one of its configured actions can be to automatically create a ticket in ServiceNow, page an on-call engineer through PagerDu...
54. What is the AppDynamics REST API used for?
The AppDynamics Controller exposes a REST API that lets teams programmatically read and configure most of what's available in the UI — metrics, health rule status, business transaction lists, and configuration objects — instead of clicking through screens manually. Use Case Example Me...
55. Explain the lifecycle of an alert from health rule violation to notification?
An AppDynamics alert isn't a single event; it's a short pipeline where a metric condition is evaluated, a status change is recorded, and only then — if configured — does an external action actually fire. flowchart TD A[Live metric arrives] --> B{Health Rule condition evaluated} B -- W...
56. What is the difference between Warning and Critical health rule severities?
Warning and Critical are the two severity levels a health rule violation can reach, and they exist so that not every deviation from normal gets treated with the same urgency — a mild slowdown and a full outage shouldn't page the same person the same way. Warning Critical A moderate, less se...
57. What are Instrumentation exclude rules and why would you use them?
Instrumentation exclude rules tell an App Agent to skip applying byte-code instrumentation to specific classes, packages, or methods that would otherwise match its normal detection logic — effectively an opt-out list layered on top of automatic and configured instrumentation.
58. Explain the execution flow of a distributed transaction across microservices in AppDynamics?
In a microservices architecture, a single user-facing request often fans out across many independently deployed services, and AppDynamics reconstructs that entire path as one logical Business Transaction rather than a set of disconnected per-service metrics. sequenceDiagram participant User parti...
