Monitoring Application Performance

Question 1

Baseline time period options

Answer 1

1. Dynamic: use a rolling window
2. Fixed - use specific time range (min 0, max 31)

Question 2

Baseline trend

Answer 2

1. None: average over all time period
2. Daily
3. Weekly
4. Monthly

Question 3

Create Baseline

Answer 3

1. Name
2. Trend
3. Time period

Question 4

Dashboard templates

Answer 4

Configuration => Tier / Node Dashboard

Can associate a dashboard with a tier!

Question 5

Development level monitoring

Answer 5

Configuration => Development level monitoring => Can select transaction

Question 6

Tiers & Nodes Show Data options

Answer 6

1. Health
2. Hardware
3. Memory (Java)
4. Network

Question 7

Configure flow maps

Answer 7

1. Persist zoom and pan?

Filtering criteria:
1. Response times
2. Calls/min
3. Errors/min

Question 8

Metric data display

Answer 8

1. 1 min resolution: 4 hours
2. 10 min resolution: 4 hours - 48 hours
3. 1 hour resolution: 48 hours - 365 days

After 365 days - deleted

Question 9

Development Level Monitoring

Answer 9

1. a mode in which certain default limits on the data that AppDynamics collects are turned off
2. apply development monitoring to a specific business transaction and originating node combination

Question 10

Effects of development level monitoring

Answer 10

1. increases the retention of call graphs and SQL statement capture
2. Exit Calls—AppDynamics increases information collected for exit calls to backend systems. For database backends, the agent collects all SQL statements without per-transaction limits. The agent also collects all JDBC and ADO.NET calls attached to methods, even when the call duration is less than 10 ms.
3. Snapshots—The agent attempts to take a snapshot for every transaction, ignoring the values for these agent node properties:

Question 11

Limit on the number of snapshots

Answer 11

Max 20 snapshots per node per minute