Debugging a multithreaded Ado.NET/EntityFramework application with DbMonitor is easier than without, but threads get mixed in the log and it's not possible to filter for a given thread (or I don't know how).

One of the (or probably both) following features would help to make this much easier:

1) Allow to Filter by StackTrace content: If I know which thread I am interested in I usually know the entrypoint method, which is a line in the stacktrace. As DbMonitor knows the stacktrace of any line t logs, filtering by stacktrace content would help to support this and probably additional usecases as well.
2) It might be worth to enable filtering by Thread. In a multithreaded application this makes it easier to follow along one thread as the log filtered to a single thread isn't interleaved any more.