Are Trace execution file names random?

[myndeswx]

Hello, I am very interested in how are trace execution files named, and if it's possible to choose the name for it?
Or maybe it's possible to make a similar log with some shared code?

Basically I need to monitor templates work externally and trace execution log file looks great!

Also, to the same question, how do you record trace execution when running template in template?

 

[VladZen]

Please check the info about tracing in help docs.

 

[myndeswx]

Please check the info about tracing in help docs.

Thank you, in the docs it says-
The files are located in the user directory: C:\Users\<USER NAME>\Documents\ZennoLab\Traces and are grouped by tasks.
But it says nothing about the file name itself? I don't know if you also have it like this, but mine seem random numbers..
And what I would like to have is threadID.txt (it would be perfect to generate the file name after starting the template)
because now how could I know which file is for which thread?

Thanks!

 

[myndeswx]

If anyone knows how to find out which file is for which thread I would appreciate it!
OR maybe someone has same solution as 'trace execution' made in shared code somehow? )

 

[VladZen]

File name in traces is thread id.
You can get thread ID in template by this C# code:

return Thread.CurrentThread.ManagedThreadId.ToString();

and add this to instance title:

instance.AddToTitle(Thread.CurrentThread.ManagedThreadId.ToString());

 

[myndeswx]

Thank you, understood, it is possible to work now!

However, I really think the naming ID is deceptive because taskID as expected is unique.
And ManagedThreadId is only a number.

So if we start a template with 3 threads there will be threadIDs - 1 ,2 3
after it completes, and we run the template again with different details, threadIDs will be 1,2,3 again

Hope that makes sense, what we really need is way to get unique running thread IDs. And traces should be also saved by that unique thread ID in my opinion.

 

[hesham]

Thank you, understood, it is possible to work now!

However, I really think the naming ID is deceptive because taskID as expected is unique.
And ManagedThreadId is only a number.

So if we start a template with 3 threads there will be threadIDs - 1 ,2 3
after it completes, and we run the template again with different details, threadIDs will be 1,2,3 again

Hope that makes sense, what we really need is way to get unique running thread IDs. And traces should be also saved by that unique thread ID in my opinion.

yes i agree with you