Assign unique task/process id for emby logging

[rbjtech 4270]

Just an observation that would make tracking 'tasks' in emby that much easier.

The tasks in emby probably already have some form of 'task/process' id - could this be written to the log ?

This way, you could filter on the 'process id' and see all elements of an individual task from start to finish.

I know you log a 'Class' but these are obviously used for multiple processes so details get all mixed up and a 'task' may consist of multiple elements.

So as an example -

If you do a library scan - that consists of ffmpeg, ProviderId, QuickImage etc - it would be good if all that could be tied together with a single 'process id' for that manual or scheduled library scan.

Thanks.

[Luke 37071]

Hi, yes it’s not a bad idea. Thanks.