Transaction Snapshot Limits

Within the guidelines, snapshot retention is also subject to snapshot retention limits. AppDynamics captures transaction snapshots subject to specific limits and conditions to manage resource consumption and performance impact. It is important to note that not all errors, slow calls, or stalled response times will generate snapshots due to these limits:

• Originating transaction snapshots are limited to a maximum of 20 snapshots per node per minute (controlled by the max-originating-snapshots-per-minute property), with a concurrency limit of 5 concurrent snapshots per node (controlled by the max-originating-concurrent-snapshots property)

• Continuing transaction snapshots are limited to a maximum of 200 snapshots per node per minute (controlled by the max-continuing-snapshots-per-minute property), with a concurrency limit of 100 concurrent snapshots per node (controlled by the max-continuing-concurrent-snapshots property).

For error transactions:

• For a single transaction, there is a maximum of two snapshots per minute.
• Across transactions, the maximum is limited to five snapshots per minute (specified by the node property max-error-snapshots-per-minute).

Snapshots are triggered under these conditions:

• When the agent starts a diagnostic session on the originating tier due to detected performance problems or manual initiation.
• When the agent identifies slow, very slow, stalled response times, or errors on the originating tier. These snapshots might contain partial call graph information as they start at the time the transaction slowed or experienced an error.
• Based on the periodic collection schedule, which by default captures one snapshot per BT every 10 minutes.