Tracking Background Transaction
Apart from web transactions, most applications run background tasks to perform various tasks like maintenance, schedulers, messaging, etc. APM Insight also captures these transactions and list them under Background tab in APM Insight dashboard.
For the agent to track background transactions, it has to be enabled in background_transaction.conf file. To configure settings for background transaction, refer below:
| Configuration |
Description |
Default Value |
| bgtransaction.tracking.enabled |
- Enabling this option, APM Insight agent starts tracking background transactions
- All transactions other than HTTP are considered as background transactions
|
True |
| bgtransaction.trace.enabled |
- Enabling this option, the agent collects traces for slow background transactions, provided bgtransaction.tracking.enabled is set to true
|
True |
| bgtransaction.trace.threshold |
- Traces will be collected for background transactions whose response time have crossed the specified threshold value, provided bgtransaction.trace.enabled is set to true
|
5 (seconds) |
| bgtransaction.record.cputime.enabled |
- Record CPU time for every background transaction, if enabled.
|
False |
bgtransaction.trace.external.
components.count.threshold |
- Trace snapshot will be taken for background transactions which has total external components (like MYSQL, MEMCACHED, etc) call count equal or higher than the configured number.
|
40 (Count) |
| bgtransaction.tracking.request.interval |
- Sampling factor for background transactions
- If value is set to 1, agent tracks every transaction. If value is set to n, agent tracks 1 in n transactions of same kind
|
1 (Request) |
