Plumbr is capable of monitoring for a large number of specific root causes explicitly. Unfortunately, the different technologies used in real world means that the number of ways a particular code can perform poorly is effectively unlimited. Thus a fallback was needed to cover the cases where the specific root cause can not be determined. In such situations, Plumbr Agent captures a snapshot from the suspicious transaction.
This snapshot is captured at the moment when 50% of the transaction threshold is exceeded. The snapshot will be linked to the transaction if the duration of the transaction will eventually be flagged as slow. When the transaction does not exceed the slow threshold, the captured snapshot is discarded.
To expose this information in a useful way, Plumbr aggregates those call stacks into a tree-like structure. Call stacks occurring most frequently are ranked higher in a tree. To reduce noise, non-repetitive occurrences are hidden, enabling you to focus on the most frequently captured snapshots first.