right now, similar events cannot be aggregated - as there is no key that binds them together. The only way to find out is by iterating and parsing to match the thread stack.
Because each event on a monitorEvent is on a lock, does it make sense to use the address of the monitor itself as the key? As per @mpirvu , the java object address is subjected to chhange across gc cycles, and are not trustworthy.
right now, similar events cannot be aggregated - as there is no key that binds them together. The only way to find out is by iterating and parsing to match the thread stack.
Because each event on a monitorEvent is on a lock, does it make sense to use the address of the monitor itself as the key? As per @mpirvu , the java object address is subjected to chhange across gc cycles, and are not trustworthy.
this can have some discussions.