Advanced

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 different transaction names in a given minute that each have their own aggregates. If this is exceeded in any given minute, then transactions with other transactions names will still be aggregated into the overall bucket, but will not have their own buckets for that minute time period.
The maximum number of different aggregated queries that are stored per query type across transactions of a given transaction name (for display on the Queries tab). This is used to limit storage and memory when there are lots of dynamically created queries. More than this number of aggregated queries are stored in memory and then this number of the top queries by time are stored. Specifically, 10 times this number are stored in memory for overall aggregates and 2 times this number are stored in memory for aggregates by transaction name.
The maximum number of different aggregated service calls that are stored per service call type across transactions of a given transaction name (for display on the Service calls tab). This is used to limit storage and memory when there are lots of dynamically created service calls. More than this number of aggregated service calls are stored in memory and then this number of the top service calls by time are stored. Specifically, 10 times this number are stored in memory for overall aggregates and 2 times this number are stored in memory for aggregates by transaction name.
Maximum number of trace entries collected for a 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 stack trace samples collected for a given transaction. This is used to limit the memory of very long transactions that would capture potentially hundreds of thousands of stack traces (e.g. large batch or background operations).