Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

Asy AppDynamics > Troubleshooting Application Problems > Flashcards

Troubleshooting Application Problems Flashcards

1
Q

Diagnostic session

A
  1. directs AppDynamics to collect extra transaction snapshots for one or more BTs for a period of time
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

A full call graph

A

captures the entire call sequence for the business transaction invocation, and contains information on each monitored node involved in the processing of the business transaction.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Snapshots under normal circumstances:

A

many of these snapshots contain partial call graphs, or no call graphs at all.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Ways to trigger diagnostic session

A
  1. Manually
  2. Automatically in response to performance problems (partial call graph)
  3. In a responce to an event via policy
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Manual diagnostic session parameters

A
  1. duration: from 1 to 10 minutes
  2. frequency: from 1 to 10 snapshots
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Slow / Error transaction default threshold

A

Configuration. => Slow transaction threshold => diagnostic session settings

  1. More than 10% of calls per minute have errors
  2. More than 10% of calls are slow / very slow / stalled
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Automated Transaction Diagnostics

A
  1. uses statistical analysis to identify transaction snapshots for anomalies that could cause issues in the future.
  2. These snapshots may not have triggered a Health Alert.
  3. delivers a prioritized list of causal factor transactions that you can use to manage problematic business transactions before they become actual production issues or outages.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How AppDynamics Defines errors

A
  1. Any Unhandled exception
  2. HTTP return codes 400-505 that occur in BT
  3. An exception that is handled but logged with a severity of Error or Fatal using Log4j or java.util.logging NLog or Log4Net
  4. A handled exception that occurs during a call to an exit point

NB: There is not a one-to-one correspondence between the number of errors and the number of exceptions.

Configuration > Instrumentation > Error Detection.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

A stack trace is available for a given exception if

A

the exception was passed in the log call.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Stall transaction definition

A
  1. Disable detection
  2. Stall occurs when a transaction’s response time is <300> deviations above average for the last 2 hours
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Slow / Error transaction setting options

A

Select one of the options:

  1. More than X % slower than the average of the last Y hours
  2. Greater than X ms
  3. (Default) Greater than 3 (4) standard deviations for the last Y (2) hour
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Configure periodic snapshot collection

A
  1. Configuration => Slow transaction snapshots => Tab: diagnostic session settings: Configure periodic snapshot collection
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Periodic snapshot collection settings options

A

(can be both)

  1. Take one snapshot every X (100) execution of a BT (not recommended for PROD)
  2. Take one snapshot every X (10) min (Default)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Troubleshoot options

A
  1. Slow response times (BT, )
  2. Errors
  3. Health rules violations
  4. War room
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Error detection options

A
  1. Using logged exceptions or messages
  2. HTTP return code
  3. Redirect pages
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Errors using logged exception and messages

A
  1. java.util.logging
  2. Log4j
  3. SLF4j/Logback
  4. Mark a BT as error
17
Q

Call Graph settings

A

Configuration / Instrumentation / Call graph settings

Configure Call Graph Settings permission.

  1. Methods taking less than X (10 ms)
  2. Minimum SQL query time X (10) ms
  3. Packages to exclude from the call graph
  4. Specific sub-packages from eluded to be included
  5. Enable Aggressive slow snapshot collection ?
18
Q

Transaction snapshot

A

A collection of detailed diagnostic information captured during a single invocation of a business transaction.
Examples include call graphs and timing during a single user login, where login is the business transaction.

19
Q

Transaction snapshot UI

A
  1. Overview
  2. Slow calls and errors
  3. Waterfall view
  4. Segment list
  5. Data collectors
20
Q

Transaction snapshot drill down

A
  1. Overview
  2. Call graph
  3. Slow calls & errors
  4. DB & remote service calls
  5. Server
  6. Network
  7. More

Asy AppDynamics (12 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions