Any transaction that exceeds this amount of time will have its partial trace stored to
disk immediately (prior to its completion).
This is to guard against transactions which never complete (or at least run long
enough and do enough harm to hang the jvm).
In the case where some transactions have been configured with a very long slow threshold, the immediate
partial trace store threshold does not take effect on those transactions until they have exceeded their slow
threshold.
The maximum number of transaction aggregates (aggregated by transaction name) that are stored per
transaction type for any given minute.
This is used to limit memory and storage when there are lots of distinct transaction names.
Any transactions that do not make the cut are still aggregated and stored in the "Overall" transaction
aggregate.
The maximum number of query aggregates (aggregated by query text) that are stored per transaction aggregate
for any given minute.
This is used to limit memory and storage when there are lots of distinct queries.
During any given minute, up to ten times this number of query aggregates are stored in memory for the
overall transaction aggregate and up to two times this number are stored in memory for named transaction
aggregates.
At the end of each minute, up to this number of query aggregates are stored to disk per transaction
aggregate.
Any queries / query aggregates that do not make the cut are aggregated and stored under the query text
"LIMIT EXCEEDED BUCKET" (for their respective query type).
In addition to this limit being applied during initial collection, it is also applied during rollups and
when displaying query aggregates in the UI (over still larger time spans).
The maximum number of service call aggregates (aggregated by service call text) that are stored per
transaction aggregate for any given minute.
This is used to limit memory and storage when there are lots of distinct service calls.
During any given minute, up to ten times this number of service call aggregates are stored in memory for the
overall transaction aggregate and up to two times this number are stored in memory for named transaction
aggregates.
At the end of each minute, up to this number of service call aggregates are stored to disk per transaction
aggregate.
Any service calls / service call aggregates that do not make the cut are aggregated and stored under the
service call text "LIMIT EXCEEDED BUCKET" (for their respective service call type).
In addition to this limit being applied during initial collection, it is also applied during rollups and
when displaying service call aggregates in the UI (over still larger time spans).
Maximum number of trace entries collected for any given transaction.
This is used to limit the memory of very long transactions that would capture
potentially hundreds of thousands of trace entries (e.g. large batch or background
operations).
Also, the UI is not really optimized for viewing super large numbers of trace entries.
Maximum number of profile samples collected for any given transaction.
This is used to limit the memory of very long transactions that would capture
potentially hundreds of thousands of profile samples (e.g. large batch or background
operations).
Profile samples are merged where possible so this can generally be quite large.