I like Diagnostic Data Collection, and am using it, but the events that it traps are not event in my top 10 of working out problem solving

One event I would use a few times a month is adding -diagEvent lockwaittimeout

Knowing what is running/stack traces/lock table when that event occurs in the db/apserver logs would go a long way to trace back bad code that causes unusual pauses in the system.

The manual option fro promon to collect the current diagnostic data is good, but for the locwaittimeouts, I'm never near the DB at the time of the event, and have not been able to catch one in the act either