All developers read Plugin trace log quite often when developing and investigating plugin issues. So if you add tracing in a meaningful manner it can pin point the erroneous point of the code.
Anyway, one issue we face in this regards is its not easy to identify the exact trace log we are interested in. Suppose we analyze an issue in PROD environment where a lot of operations occur is same time. My personal opinion is its not even helpful with applying multiple filters to track the exact record.
In such situations, I find Plugin Trace Viewer (of Xrm Tool Box) helpful.
That's because, it allows you to apply many filters effectively by date, Plugin etc. which definitely help you fetch the exact trace you are searching for, evening with in lots of lots of traces.
(Note: Please press Ctrl + F for text search of the trace log which is a most important feature)
I am very thankful to Jonas Rapp who is the author of the tool.
You too will like it!
